This document covers the following topics:
ADAREP can be specified alone to retrieve a database status report. You can optionally customize the report by added parameter values.
These parameters are used to print the checkpoint list in normal (CPLIST) or extended (CPEXLIST) format. Either CPEXLIST or CPLIST must be specified to display checkpoint information. CPEXLIST adds the following information to the normal CPLIST information, depending on the checkpoint origin:
(Utility or Adabas Online System/Basic Services) function name;
Checkpoint-specific data.
If the CPEXLIST report is to be displayed, OFFSET can also be specified for a more readable display.
The FROMDATE, TODATE, FROMSESSION, and TOSESSION parameters may be used to indicate the range of checkpoints to be printed.
FILE defines the list of files for which status information is to be printed or displayed. If this parameter is omitted, status information for all files will be included.
If NOFILE is specified, the printing of all file and field description information is suppressed.
When CPLIST or CPEXLIST is specified, specific start and/or end dates for checkpoint information can be specified. Examples of valid yyyymmdd date specification are:
ADAREP FROMDATE=19960101,TODATE=19960228 January 1-February 28, 1996
ADAREP FROMDATE=19951111 November 11, 1995 to checkpoint file end
ADAREP TODATE=19951223 From checkpoint file begin to (and including)
December 23, 1995
If FROMDATE is not specified, the report begins with the earliest checkpoint information in the system (or with the first on the FROMSESSION session, if later); if TODATE is not specified, the report continues up to the most recent checkpoint (or ends with the last on the TOSESSION session, if earlier).
Specify a start and/or end session number. Sessions before FROMSESSION and/or after TOSESSION session numbers are not included in the report information. If FROMSESSION is not specified, the report begins with the earliest checkpoint information in the system (or with the first on the FROMDATE date, if later); if TOSESSION is not specified, the report continues up to the last checkpoint (or ends with the last on the TODATE date, if earlier).
LAYOUT=1 specifies that the "Contents of Database" table should be printed in a single 120- character column format. Normally, the Contents of Database report table is divided into two 80-column subtables suitable for terminal display.
The following is an example of how the Contents of Database section of the report would appear if LAYOUT=1 is specified. You compare this sample to the one provided in Contents of the Database: General File Status.
*************************************************
* Contents of Database 68 (EXAMP68 ) * yyyy-mm-dd hh:mm:ss
*************************************************
File Name Loaded TOP-ISN MAX-ISN EXT. PADD Blocks Allocated (Blocks Unused)
NUA D A% D% NI UI AC DATA/CYL
1 EMPLOYEES 2001-12-28 1107 1695 111 1 10 10 200 15 2 150/1
1 138 2 104/0
2 MISCELLANEOUS 2001-12-28 1779 2543 111 1 10 10 200 15 3 150/1
2 174 10 97/0
3 VEHICLES 2001-12-28 773 1695 111 1 10 10 200 15 2 150/1
3 183 8 138/0 |
ADAREP reads the address converter to determine the value for RECORDS LOADED for a file. For very large files, this can result in a large amount of I/O activity. If LIMCOUNT is specified, ADAREP checks the value for TOPISN for the file. If TOPISN is greater than 1000, "NOT COUNTED" appears under RECORDS LOADED.
If NOCOUNT is specified, no value is printed for RECORDS LOADED for any file. If neither LIMCOUNT nor NOCOUNT are specified, ADAREP compiles the exact value for RECORDS LOADED for each file.
The printing of the field definition table (FDT) information for each file is to be omitted. The FDT of the Adabas checkpoint and security files are not printed by ADAREP.
If NOLGLIST is specified, the logical database layout information is to be omitted. If NOPHLIST is specified, physical database layout information is omitted. Specifying NOSTD suppresses all database layout information, and is equivalent to specifying NOLGLIST and NOPHLIST.
When an error is encountered while the function is running, the utility prints an error message and terminates with user abend 34 (with a dump) or user abend 35 (without a dump).
If NOUSERABEND is specified, the utility will not abend after printing the error message. Instead, the message "utility TERMINATED DUE TO ERROR CONDITION" is displayed and the utility terminates with condition code 20.
The OFFSET parameter aligns the beginning of the extended information with the end of the normal checkpoint information for printing on a single line. The default is 63. To display extended information, OFFSET must be reduced or the extended portion may not be displayable within 80 columns.
PLOGNUM specifies the number of the nucleus protection log used during the ADASAV save operation. The parameter is required if the supplied save tape was created by an Adabas version 5.1 online save operation. For tapes created using Adabas version 5.2 or above, the PLOGNUM is supplied on the tape. Specifying PLOGNUM for such tapes overrides the information on the tape.
If SAVETAPE is specified, the report is printed from a save tape. The purpose of the save tape report is to determine what the save tape contains. For more information, see the section Processing Save Tape Input.
CPLIST/ CPEXLIST cannot be specified with SAVETAPE. NOCOUNT must be specified with SAVETAPE because ADAREP does not count the number of records in a file on a save tape. If CPLIST/ CPEXLIST is specified or NOCOUNT is not, ADAREP prints a warning message, changes these options internally, and continues processing.
SYN1/SYN4 specifies the block number containing the SYN1/SYN4 checkpoint at which the corresponding save operation began. The parameter is required if the supplied save tape was created by an Adabas version 5.1 online save operation. For tapes created using ADASAV version 5.2 or above, the SYN1/SYN4 checkpoint information is supplied on the tape. Specifying SYN1/SYN4 for such tapes overrides the information on the tape.
ADAREP REPORT
All database, file, and field information is to be printed. Checkpoint data is not to be printed.
ADAREP REPORT NOFDT
Database and file information is to be printed. Checkpoint data and field definitions for each file are not to be printed.
ADAREP CPEXLIST,FROMDATE=19980701,TODATE=19980715 ADAREP NOSTD,NOFILE
A checkpoint list (extended format) is to be printed for all checkpoints taken between July 1, 1998 and July 15, 1998. No other information is to be printed.
ADAREP REPORT SAVETAPE,NOCOUNT
All database, file, and field information is to be printed from a save tape. NOCOUNT is required because ADAREP does not count the number of records in a file on a save tape.
