Re: Identifing IBM commands that return control before process completes

On 16-Jun-2015 12:08 -0600, Steinmetz, Paul wrote:

My original issue is within an AJS job, no way of waiting for the
END* or STR* to complete before going to the next sequence.
<<SNIP>>

FWiW, I would probably code a request that encapsulates separately the various END* and STR* rather than directly coding the specific OS commands; e.g. ENDJOBWAIT JOB() instead of ENDJOB JOB(), ENDSBSWAIT SBS() instead of ENDSBS SBS(), etc. Or perhaps code a Delay For Request (DLYFORRQS) command that invokes the respective polled-delay capability required for whatever was coded as the preceding request; e.g. instead of coding the two comma-separated requests ENDJOB TEST2, DLYJOB 5 for which one can only /hope/ that the 5-second delay is enough and suffer the unnecessary stalling when the 5-second delay is excessive, I would code the two comma-separated requests ENDJOB JOB(*N/*N/TEST2), DLYFORRQS RQS(*ENDJOB) JOB(*N/*N/TEST2). The latter is a somewhat problematic implementation, because the coded requests must be maintained as paired.

Other features have taken into account the probable desire to effect waits and\or synchronous behavior vs only operating asynchronously, so again, I do not know why few seem willing to submit DCRs to IBM asking for certain commands to add the capability to operate synchronously; e.g. Vary Configuration (VRYCFG) has:
Vary on wait (VRYWAIT)
Asynchronous vary off (ASCVRYOFF)