Date: mm/dd/ccyy ******************************************************************************** Page: 1 * CA Datacom/DB * Time: hh.mm.ss * General Utility * Release: 12 * Copyright © 2009 CA. All rights reserved. * SPnn ******************************************************************************** CONTROL CARD(S) .........1.........2.........3.........4.........5.........6.........7.........8 Œ REPORT AREA=LXX FUNCTION=REPORT AREA=LXX Ž
The command exactly as entered.
An analysis of keywords encountered and expected. Any errors found are flagged with a note in the left margin.
Any messages related to syntax processing are presented in this area.
Date: mm/dd/ccyy ******************************************************************************** Page: 2 * CA Datacom/DB * Time: hh.mm.ss * Multi-User Facility * Release: 12 * Copyright © 2009 CA. All rights reserved. * SPnn ******************************************************************************** LOG FILE (LXX) OUTPUT LOG FILE OPEN - NO LOG FILE SPILLING - NO LOG FILE SPILL PENDING - NO MASTER LIST RCV OPTION - YES LOG FILE HIGHEST TRANSACTION SEQUENCE NUMBER - DBDC2C2A CYCLE START DATE - 5/06/2009 CYCLE START TIME - 7.14.33 FIRST BLOCK USED THIS CYCLE - 0001C800 CURRENT LOG BLOCK - 0001C8FF PHYSICAL BLOCKS USED THIS CYCLE - 0 RESTART FORWARD SCAN BLOCK - 0001C800 LOG PENDING PARAMETER - 100 LOG FILE BLOCK SIZE - 32,760 PHYSICAL BLOCK SIZE - 32,760 LOG VARIABLE - YES PHYSICAL BLOCKS PER LOGICAL BLOCK - 1
This section of the report provides messages that indicate the status of the Log Area.
LOG FILE HIGHEST TRANSACTION SEQUENCE NUMBER indicates the last transaction sequence number in the Log Area.
VARIABLE indicates if the LXX is initialized as variable (YES) or not (NO), specified by the DBUTLTY INIT AREA=LXX VARIABLE= option.
The date and time (ccyymmddhhmmss) of the LXX INIT, FXX INIT, and LAST LOG RECORD indicates when each was last initialized, as follows:
The date and time of the INITs is that which DBUTLTY was using when executed. Prior to Version 12.0, this date and time was adjusted relating to current daylight saving time. It is printed as binary zeros if the LXX or FXX was not subject to INIT in Version 11.0 (also known as r11) SP2 or later. Following the date and time is the store clock value (in hex, cccccccccccccccc, for example C23D3418E97E5B82) at the time of the INIT.
LXX RESET - NO indicates that the LXX in this example has not been reset since it was last initialized. If the LXX had been RESET, the NO would be replaced with the date and time (ccyymmddhhmmss) of the RESET, followed by the store clock value (cccccccccccccccc) at the time of the RESET.
The FXX TOTAL TASKS line shows the Force Area total tasks that are allowed to execute. This is the number that restricts whether MUF can enable the line (below the line) by specifying the number of total tasks that are allowed, the most that have been used since the last INIT, and the current number of system tasks. The number of user tasks allowed are reduced by the number of system tasks.
The FXX USER TASKS line is the number of user tasks that are allowed, based upon the current total tasks.
The next line gives information about the meaning of user tasks. When a user does an INIT of the FXX with TASKS=, this number is the user tasks, to which CA Datacom/DB adds the current number of system tasks to arrive at a number of total tasks. Because, as already mentioned, the number of user tasks allowed are reduced by the number of system tasks, if the number of system tasks changes, the number of user tasks can decrease.
The LAST LOG RECORD line provides the date and time (ccyymmddhhmmss) and store clock value (cccccccccccccccc) of the last record logged in the prior MUF. It is zeros for the first MUF after an INIT. This line is provided for information only. If the MUF did a full restart, the scan process looked for a step-down condition to stop. If a step-down is found, the date and time and store clock value of the step-down is provided, preceded by an * as shown in the sample report. If the step-down occurred not to a valid log record but to a binary zero block (it is zeros for the first MUF after an INIT), the message would instead be STEP DOWN - BINARY ZERO BLOCK. If the step-down occurred to an invalid record, the message would instead be STEP DOWN - INCOMPLETE RECORD (this condition could occur if the block data was being sent down the channel when a sever machine condition interrupted the flow and what was written to DASD was incomplete, which might or might not be possible with current hardware).
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|