Processing for a BULK MODIFY request occurs for each data set matching the application thread's selection criteria. It is important to understand job boundaries can be crossed.

There is NO posting of the ECB after a BULK MODIFY request has been processed by JES.

In certain situations the BULK MODIFY request may not be successful. This is normal, and can occur if the output being released/returned is BUSY .There is no ECB posted and no error code returned; JES2 will always return to the caller, but the actual request may be partially or completely bypassed.

To assure that the desired changes are processed, it may be necessary to query the status of a job or specific job output, and if it appears that a request did not complete, then the BULK MODIFY request can be reissued.

You must provide at least SAF UPDATE authority for the JESSPOOL resource class to the application thread in order to correctly issue the SAPI BULK MODIFY call.

If the application does not provide for multi-tasking, it must follow the protocol shown in Figure 1. If the application does provide for multi-tasking, each thread in the application address space must follow the protocol shown in Figure 1.

Figure 1. Protocol for the SAPI BULK MODIFY Call