Space announcements

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Log Master termination processing

The following table summarizes how Log Master attempts to respond when it encounters a return code 8 (error) or greater.

Log Master produces output data sets and updates the Repository differently in response to these return codes depending on whether the return code is 8 (error), or 12 (severe), and whether a work ID contains at least one ongoing log scan.

Note

This section provides general information about Log Master termination processing in response to error conditions. Depending on the circumstances in your environment, or the circumstances of a particular error condition, the product might respond differently or might not be able to respond as described here.

Log Master output handling at termination

Return code

Work ID includes at least one ongoing log scan

Actions during termination processing

8

No

  • Write and catalog all output data sets. 1

  • Update the Repository with history information about the work ID.

If the work ID includes multiple log scans, the product takes these actions for all log scans (including log scans that did not encounter an error).

8

Yes

  • Purge and uncatalog logical log, load, SQL, and DDL output data sets, and command files.

  • Write and catalog all reports. 1

  • Update the Repository with history information about the work ID.

  • Discard updates to the ALPURID table of the Repository. 2

If the work ID includes multiple log scans, the product takes these actions for all log scans (including log scans that did not encounter an error and log scans that are not ongoing).

12

No

  • Purge and uncatalog logical log, load, SQL, and DDL output data sets, and command files.

  • Write and catalog all reports. 1

  • Update the Repository with history information about the work ID.

If the work ID includes multiple log scans, the product takes these actions for all log scans (including log scans that did not encounter an error).

12

Yes

  • Purge and uncatalog logical log, load, SQL, and DDL output data sets, and command files.

  • Write and catalog all reports. 1

  • Update the Repository with history information about the work ID.

  • Discard updates to the ALPURID table of the Repository. 2

If the work ID includes multiple log scans, the product takes these actions for all log scans (including log scans that did not encounter an error and log scans that are not ongoing).

1 Log Master processes different forms of output simultaneously (in parallel). Because of this behavior, the output data sets that Log Master writes and catalogs after an error can contain complete or partial output. If processing for a form of output encounters return code 8 or greater, that data set might contain only output that was generated before the product encountered the error condition.

2 Log Master tracks each run of an ongoing log scan by using the ALPURID table in the Repository. When an ongoing log scan encounters return code 8 or greater, the product assumes that the log scan must be run again so that all output files include the same set of transactions. Because of this assumption, the product does not update the ALPURID table with information from the log scan that encountered the error. This action ensures that the next run of the ongoing log scan uses the same start point as the run that encountered the error.


Was this page helpful? Yes No Submitting... Thank you

Comments