Externally initiated REXX EXECs
Externally initiated EXECs are scheduled by
- A job step that executes the IMFSUBEX program
- A user-written program
- A TSO user
The EXEC that IMFSUBEX schedules is called an externally initiated EXEC.
Example
The following EXEC is scheduled:
Externally initiated REXX EXEC example
ARG BACKDONE V1 .
/*----------------------------------------------------------------*/
/* DOC GROUP(MVS) FUNC(BKUP) CODE(BK) */
/* DOC DISP(YES) AUTHOR(B&B) */
/* DOC DESC(SEND NOTIFY/LOG FOR A SUCCESSFUL BACKUP) */
/*----------------------------------------------------------------*/
"IMFEXEC CMD #SE 'VOLUME 'V1' SUCCESSFULLY DUMPED',LOGON,USER=(SYSP1,SYSP2)"
"IMFEXEC MSG 'VOLUME 'V1' SUCCESSFULLY DUMPED'"
EXIT
The positional parameters that are passed to the EXEC-initiated EXEC are shown in the following table:
Positional parameter | Variable name | Value passed | Description of value passed |
|---|---|---|---|
1 | BACKDONE | BACKDONE | Name of the EXEC scheduled |
2 | V1 | SYST1 | Name of the volume serial number of a DASD |
3 | . | . | Period pads the positional parameters |
Example description
The EXEC named BACKDONE is scheduled in a target subsystem called SSA1.
A single parameter is passed (SYST1), which is a DASD volume serial number. The BACKDONE EXEC receives a volume serial number of a DASD from the second positional parameter to IMFSUBEX.
The BACKDONE EXEC first sends a message to two TSO users, SYSP1 and SYSP2, informing them that the volume backup has been successful and then places a message in the BBI-SS PAS Journal recording a successful operation.