LXX (Log File) Automated Processing for Jobtrac AMR

Products

Datacom Jobtrac Datacom/AD Datacom/DB

Issue/Introduction

Datacom/AD uses a log file called the LXX to capture database maintenance transactions (add, update and delete) as part of the process for maintaining data integrity. As updates are made to the database, the LXX is updated with each change that is made.

Is there a way to use Jobtrac AMR functionality to help manage the LXX?

Environment

z/OS

Datacom/AD Version 15.1

Datacom/DB Version 15.1

Resolution

First, it is important to note that if the LXX is allowed to fill up, all update processing in the MUF will stop until the committed update transactions are spilled from the LXX to the Recovery File (called the RXX) and removed from the LXX. Once the LXX has reached the pre-defined threshold as noted on the MUF Startup Option LOGSPILL (first parameter), messages will be produced in the MUF log to indicate how full the LXX is at that point. You can use the Jobtrac AMR functionality to monitor and respond to these messages.

One caution is that since Jobtrac uses Datacom processing for its data, if there is a problem and the LXX for the Jobtrac MUF reaches 100% full, this AMR process will not be able to submit the LXX Spill job. Be sure that you have an alternative process to identify this critical error.

Below is the configuration of the AMR table to capture the DB00308I message that is issued when the LXX reaches the threshold noted above. Here is a sample of that message:

DB00308I - LOG AREA IS  nn% FULL, nnnnnn BLOCKS SPILLABLE

Here is the AMR table setup used to capture the Datacom/AD message above.

CA-Jobtrac                     AMR Table                 Row 1 to 2 of 2
COMMAND ===>                                             SCROLL ===> PAGE
                                                         07/02/24   10:38
Table: DAILY                                                                
--------------------------------------------------------------------------
  Msg Text   : '//DB00308I'                                   Offset= 000
Command/Reply:                                                            
Altered Text :                                                Offset= 000
Process Pe   :        Create Event: MUFJOBNM     Trigger Event: DBSPILL       
TOD Range    :        SYS:               Trg Act: ( RUN  )

Once this is set up, you will need to identify the DBUTLTY Spill JCL member that is moved to the location 000 library for AMR to submit when this message is processed.

Additional Information

For more information on using OPS/MVS or other automation tools to manage the Datacom LXX messages, please review Knowledge Base article 26465, titled "Managing Datacom Log file (LXX) spills with automation (Automated Operations) routines".