A Recovery File (RXX) Analysis Report reads a RXX and produces a summary report of the contents.
The many options provided by this report allow you to use information about the contents of a Recovery File to analyze logging and recovery operations and correct any problems that could occur.
This utility always reads one input file of one or more volumes. In z/OS, this can be multiple concatenated files which appear to CA Datacom/DB as one file. In all environments, if the input is not log data, unexpected results occur. z/OS users can run the report against the Log Area (LXX) directly. This is not recommended, but can be requested by CA Support. If this is done, one or more of the various warnings is to be expected. This is because:
The REPORT function, like all DBUTLTY functions, is designed and expected to run authorized in z/OS. If the RXX was built from an LXX that was ever used with the MUF option LOG_RECORD_ENCRYPT set to YES since the LXX was last initialized or reset, the REPORT function is required to run authorized. It does not matter if the RXX being read has encrypted data. Potentially authorized data is not intended to be in an unauthorized address space.
Following is the syntax for the RXX Analysis Report:
Note: The Recovery File Analysis Report program can detect the type of input file. If the input is a CA Datacom Fast Recovery file (split), the Report control statements are as shown in the Split File Analysis Report syntax on page Split File Analysis Report.
┌─ , ─────────────┐ ►►─ REPORT AREA=RXX ─┬─────────────────────┬─▼─┬─────────────┬─┴──────────────► └─ BLOCK=blocknumber ─┘ └─ DBID=nnnn ─┘ ►─┬───────────────────┬─┬───────────────────────────┬────────────────────────► └─ JOBNAME=jobname ─┘ └─ LOGPRINT=log-print-type ─┘ ►─┬────────────────┬─┬───────────────────────────┬───────────────────────────► └─ OPTION2=name ─┘ └─ RANGEDT=date/time-range ─┘ ►─┬────────────────────────┬─┬─────────────────────────────┬─────────────────► └─ RANGETSN=tsn-numbers ─┘ └─ RECORDS=log-recs-accepted ─┘ ►─┬────────────────────────────┬─┬──────────────────────────────┬────────────► └─ RUNUNIT=run-unit-numbers ─┘ └─ STARTAFT=log-recs-to-count ─┘ ►─┬────────────────────┬─┬───────────────────────────┬───────────────────────► └─ TABLE=table-name ─┘ └─ TSNPRINT=tsn-print-type ─┘ ►─┬─────────────────────┬────────────────────────────────────────────────────►◄ └─ URINUM=uri-number ─┘
The syntax just shown defines the provided and optional reports. Each was described as though the entire input was considered selected data (the default), but be aware that numerous data selection options are available. Remember, too, that a log record, to be selected, must pass all of the specified options (a single option can be specified or any combination, including all of them).
Each of the following options can only be specified once, except for the DBID= option, that you can repeat.
Command
Invokes the function to produce a report.
Required Keywords
Requests the Recovery File Analysis Report.
This is specified as an eight-character hexadecimal number representing a data block within a data area. This option would normally be included when requested by CA Support.
Use to specify a database ID. You can repeat this option. Each occurrence may specify one or more valid database IDs or a range of DBIDs nnnn-mmmm (a range, for example, such as 100-250).
Specify a job name.
Choose either DETAIL or DETAILX for log-print-type.
The DETAIL option prints an INPUT RECORD that can be useful, if one execution selects all records for a transaction. This information can be used to dump the records around the selected records in another execution. If the same input file(s) are provided, this input record number is the same for each execution.
The DETAILX option prints an INPUT RECORD and formats a hex dump of the log record. As either of these options may produce large quantities, the standard DBUTLTY report headings are reduced to an abbreviated one line.
Specify a data area name or the Full Parent name of a partitioned table.
Specify two date/times to provide a range (low to high). The date/times are specified as a 28 character number with the lower date/time immediately followed by the higher date/time. Each date/time is 14 characters in the format 'ccyymmddhhmmss'. For example: '2002121400000020020228235959'. Note that the input is not read beyond one record higher than this ending value.
Specify two TSN numbers to provide a range (low to high). The TSN numbers are specified as a 16-character hexadecimal number comprising 8 characters for the low TSN followed by the high TSN.
Provides a count of log records that are acceptable after processing the number of log records specified in the STARTAFT= parameter. If STARTAFT= is not specified, the count is presumed to be zero. The combination of RECORDS= and STARTAFT= provides the ability to print/dump portions of a Recovery File (RXX). Valid entries for RECORDS= is a number from 0 through 99999999. The default is all remaining records.
Note: The input is not read beyond the number of records that are to be selected.
Specify a run unit number to restrict record selection. Valid entries for RUNUNIT= is a number from 0 through 99999. The default is all run units.
Specify a count of log records before which all are rejected. Valid entries for STARTAFT= is a number from 0 through 99999999. The default is 0.
Specify a table name. This is the table name in the Request Area when the log record was built.
Specify a transaction report that prints one line of output for every transaction selected in the input.
Choose either SUMMARY, DETAIL, or DETAILX for tsn-print-type. DETAIL and DETAILX are described in the LOGPRINT= section on Recovery File (RXX) Analysis Report. Specifying SUMMARY produces the basic transaction report. For more information and examples see TSNPRINT=DETAIL Sample.
Provides an eight-character URI number.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|