Warning messages are built into the RXX Analysis Report to alert you to unexpected data. The warnings do not necessarily represent a problem but could. The input is expected to be a series of log records in the order they were created. If this is found to not be true, a warning message is produced. For example:
WARNING: TIMESTAMP STEP DOWN: FROM B229FA165F111C00 TO B229EC970BCCFB04 LXX BLOCK xxxxxxxx VS yyyyyyyy WARNING: DATE/TIME STEP DOWN: FROM mm/dd/ccyy hh.mm.ss TO mm/dd/ccyy hh.mm.ss LXX BLOCK xxxxxxxx VS yyyyyyyy WARNING: TSN STEP DOWN: FROM DBDB2706 TO DBDB2701 LXX BLOCK xxxxxxxx VS yyyyyyyy WARNING: LOG RECORD SEQUENCE NUMBER NOT +1: FROM 0000000F TO 0000005F LXX BLOCK xxxxxxxx VS yyyyyyyy
For the LXX BLOCK info in the previously shown example:
Shows (for debugging purposes) the hex value for the log block prior to the current one.
Shows (for debugging purposes) the hex value for the current log block.
Each of the four kinds of warning messages shown previously is independent of the others and occurs as often as its condition applies. For example, if the volumes of a multivolume file are provided in an order other than that in which they were built, one of each message would be expected.
Because an RXX Analysis Report can be lengthy and the warning message(s) can be embedded with the output (making it easy for them to be overlooked), at the bottom of the report (if any of the warning messages were generated) is a warning that alerts you to the embedded warning(s). The messages that warn you about the warnings are:
WARNING: TIMESTAMP STEP DOWN(S) ENCOUNTERED. WARNING: DATE/TIME STEP DOWN(S) ENCOUNTERED. WARNING: TSN STEP DOWN(S) ENCOUNTERED. WARNING: LOG RECORD SEQ. NUMBER NOT +1(S) ENCOUNTERED.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|