The CONTINUE keyword allows you to continue processing TYPE=LOGR requests even if some earlier requests fail. This keyword applies only to the job step in which it appears as it does not span job steps. This keyword can be useful when you want to process many requests in a single job step and you want system logger to try to execute all the requests. Even if some fail.

The placement of the CONTINUE request is significant. If an error occurs in requests before the CONTINUE request is specified, system logger will not execute the remaining requests, including the CONTINUE request. However, system logger will perform syntax checking on the remaining statements as usual. If an error occurs after CONTINUE is specified, system logger will record the error and attempt to execute the remaining requests in the job step.

You only need to specify CONTINUE once. Subsequent CONTINUE requests are allowed, but will not produce a different effect than if CONTINUE was only specified once.

System logger displays message IXG004I for successful requests that follow the CONTINUE keyword. It displays messages IXG447I and IXG003I for failing requests that follow the CONTINUE keyword. The failure message IXG447I is similar to IXG002E, but does not mean system logger will stop trying to execute requests. At the end of the report, system logger displays message IXG446E if any request failed. This message presents the number of errors system logger found.

If your requests are contingent on a previous request, use a separate job steps and avoid the use of the CONTINUE request. The result of a job step with CONTINUE that has an error is an overall failure return code of 12.

In the event of a syntax error, the IXCMIAPU utility stops processing and will not execute the remaining requests, even if CONTINUE is specified.

For examples of the CONTINUE keyword, see Administrative data utility for the LOGR policy. Also see the section titled Utility Error Messages in z/OS MVS Diagnosis: Reference for examples of message output.