Using the MAXDELAY keyword parameter to synchronize submitted Processes
You can synchronize submitted Processes by coding the MAXDELAY keyword parameter in either the SUBMIT command or the PROCESS statement.
To suspend the execution of the DGADBATC job step until the submitted Process either completes or a specified interval of time elapses, use the MAXDELAY keyword.
For a detailed description of the MAXDELAY parameter, see the Submit command in SUBMIT Command.
Important: Because of the following restrictions, you might want to code MAXDELAY in the
SUBMIT command instead of the PROCESS statement:
- If you code MAXDELAY in a PROCESS and submit it through the IUI, the submit will fail with the message SCBI220I MAXDELAY not supported feature for IUI.
- If you use the MAXDELAY PROCESS statement keyword, the message
SCBI221I MAXDELAY not supported for ESF submits
is displayed when the DTF is down and the Process does not submit.
The following example shows the MAXDELAY keyword that is coded in the SUBMIT
command.
//SYSIN DD *
SIGNON USERID=(USER01,PASSWRD)ESF=NO
SUBMIT PROC=PROCAAA MAXDELAY=UNLIMITED
SIGNOFF
/*
You can also place the MAXDELAY keyword in the PROCESS statement for PROCAAA, as in the following
example.
PROCAAA PROC SNODE=REMOTE.NODE.B MAXDELAY=UNLIMITED
STEP01 COPY TO (DSN=USER01.TESTDATA.OUTPUT -
DISP=RPL -
SNODE) -
FROM (DSN=USER01.TESTDATA.INPUT -
DISP=SHR -
PNODE)