Example 1: ALERT-initiated CLIST EXEC without optional parameters
This example shows an IMFEXEC ALERT statement that schedules an EXEC named SETJOB without any optional parameters:
The ALERT generated by this statement looks like this example:
_____ 10:15 e SYSB SETUP BAB031 . . . JOB 00395
You enter OUT (or any maximum five-character string) in the RSP column. The positional parameters passed to the ALERT-initiated EXEC in this example are defined in the following table:
Positional parameter | Variable name | Value passed | Description of value passed |
|---|---|---|---|
1 | EXECNAME | SETJOB | is the name of the EXEC |
2 | RSP | OUT (contents of the 5-character RSP column) | is the (up to) five-character string the user enters in the RSP column of the ALERT DETAIL DISPLAY panel to actually invoke the ALERT |
3 | ATEXT1 | SETUP | is the first word of ALERT text |
4 | ATEXT2 | BAB031 | is the second word |
5 | ATEXT3 | . | is the third word |
6 | ATEXT4 | . | is the fourth word |
7 | ATEXT5 | . | is the fifth word |
8 | ATEXT6 | JOB | is the sixth word |
9 | ATEXT7 | 00395 | is the last word of the ALERT text |
Figure 1. ALERT-Initiated CLIST (Example 1)
/*********************************************************************/
/* DOC GROUP(MVS) FUNC(JES2) CODE(J2) DOC DISP(YES) */
/* AUTHOR(B&B) DOC DESC(WRITE MESSAGE FOR SETUP) */
/*-------------------------------------------------------------------*/
IMFEXEC MSG 'ALERT &EXECNAME IS REQUESTING SETUP FOR JOB &ATEXT7'
EXIT
Describing the example
This EXEC issues the IMFEXEC MSG command to write a message to the BBI-SS PAS Journal that, when all the values from the input are substituted for, translates into the following example: