TAPEAUDIT - Audit Catalog-Tape Database
Advanced Catalog Management provides the TAPEAUDIT command to analyze and suggest catalog fixes or tape system queries for a variety of error conditions in your ICF catalog environment as compared to your RMM, TLMS, or CA1 TMS tape management system. The catalog fixes are written to one DD statement for IDCAMS processing and the tape system queries are written to a second DD statement for subsequent processing your tape management systems query command.
- Detection of cataloged tape data sets not defined in tape database.
- Detection of cataloged tape data sets not accessible via catalog aliases.
- Detection of cataloged tape data sets that are not cataloged in the catalog appropriate for the data set's alias.
- Detection of tape volumes in your tape database that are not in the catalog as data sets.
- Detection of tape data sets where the catalog and tape management system have different volumes, file sequence numbers, or volume sequence numbers.
- Detection of a tape data set that defined on a scratch volume.
Syntax
TAPEAUDIT Command Syntax
Keywords
- RMM
- Specifies the RMM tape management system.
- TMC
- Specifies the TMC tape management system.
- TLMS
- Specifies the TLMS tape management system.
- INCLUDE-BCS
- Specifies one or more fully qualified catalogs or catalogs masks
to process.Important: If neither INCLUDE-BCS or EXCLUDE-BCS is used, the current master catalog and all connected user catalogs will be included.
- EXCLUDE-BCS
- Optionally specifies one or more fully qualified catalogs or catalog
masks to exclude from processing.Important: If neither INCLUDE-BCS or EXCLUDE-BCS is used, the current master catalog and all connected user catalogs will be included.
- INCLUDE-ALIAS
- Specifies one or more fully qualified catalog aliases or alias masks to process.
- EXCLUDE-ALIAS
- Optionally specifies one or more fully qualified alias or alias masks to exclude from processing.
- IDCAMS-FIXFILE
- Optionally specifies the DD name to be used to output the file
containing catalog fixes using IDCAMS.
If not specified, TAPEAUDIT will not generate IDCAMS fixes.
- TAPESYS-FIXFILE
- Optionally specifies the DD name to be used to output the file
containing queries for your tape management system.
If not specified, TAPEAUDIT will not generate tape system fixes.
- EXTRACT-FILE
- Optionally specifies the DD name to be used to output the file
containing data used to create fixes.
The extract file is intended for use by those users who find that the form of the fixes provided by TAPEAUDIT, does not meet their needs. The extract file can be processed by MQFL using CKMPTAMQ data definition.
- MESSAGE-TEXT
- Optionally controls the volume of messages printed during the
operation of TAPEAUDIT. The valid values are:
- ABBREVIATED - (the default) indicates that a minimal set of progress messages are displayed.
- FULL - indicates that more progress messages are displayed.
- DEFAULT-USERCATALOG
- The IDCAMS fixes written by TAPEAUDIT use a value for the CATALOG
keyword when the user catalog is not known. If specified, the data
set name must specify an existing catalog.
When a data set is found in the tape system which has no matching catalog alias and no catalog entries, TAPEAUDIT will create IDCAMS fixes for defining the alias to the specified catalog and defining the data set in the specified catalog. If DEFAULT-USERCATALOG is not specified, the first user catalog discovered by TAPEAUDIT will be used.
- DEVICETYPE
- The IDCAMS DEFINE NONVSAM fixes written by TAPEAUDIT require a value for the DEVICETYPES keyword
for cataloging either an un-cataloged data set found in the tape database or an incorrectly
cataloged data set. DEVTYPE value consists of one to eight characters. Important: The DEVTYPE value will be used in the IDCAMS fix if specified. If DEVTYPE is not specified, the value “3490” will be used in the IDCAMS fix.
- LIMIT
- By default TAPEAUDIT will limit the number of fixes to 32. You can specify a value of 0 to 999999. Specifying 0 will disable all limits.
- FOREIGN
- Foreign tapes are tapes that are not managed by the tape management system. Use the FOREIGN keyword to list those volume names that are not managed by the tape management system but have cataloged data sets. TAPEAUDIT will not generate mismatch errors for these foreign tapes; however, TAPEAUDIT requires that the volume names are not in the tape management system.
- POLICY
- (TLMS only) TAPEAUDIT TLMS uses this keyword's
four policy keywords (ALLCATALOGED, CATALOGED, UNCATALOGED, and IGNORE)
to specify how it manages data sets. Each of these policy keywords
can name one or more retention codes in any order. If specified,
each individual retention code can appear at most one time in the
policy keywords.
Valid
Table 1. POLICY keyword retention codes Code Control Default Policy 1 Catalog ALLCATALOGED 2 Keep date ALLCATALOGED 3 Catalog/date ALLCATALOGED 4 Cycle ALLCATALOGED 5 Elapsed days ALLCATALOGED 6 Move immediate ALLCATALOGED 7 Manual ALLCATALOGED 8 Days since used ALLCATALOGED 9 Expiration data keyword ALLCATALOGED A Catalog for all data sets on the tape ALLCATALOGED B Keep date ALLCATALOGED C Catalog/date for all data sets on the tape ALLCATALOGED Unless specified by ALLCATALOGED, CATALOGED, UNCATALOGED, or IGNORE, the retention codes default is to manage them as if specified as ALLCATALOGED(123456789ABC).
- ALLCATALOGED(codes)
- TAPEAUDIT enforces this policy by allowing but not requiring these
retention codes to have entries in the z/OS catalog. This supports
tapes that are to be retained until all of the data sets on the tape
are un-cataloged.
Data sets on TLMS tape volumes with one of the specified retention codes are used for a match with entries from the z/OS catalogs if the data set is cataloged. A mismatch causes a TAPEAUDIT message.
Specifying ALLCATALOGED retention codes has no affect because all of the retention codes default to this policy.
- CATALOGED(codes)
- TAPEAUDIT enforces this policy by requiring retention codes to have entries in the z/OS catalog.
A data set with one of the specified retention codes is extracted for a match with entries from the z/OS catalogs. A mismatch causes a TAPEAUDIT message.
For example: CATALOGED(57) Specifying “5” and “7” removes these codes from the default ALLCATALOGED policy and adds them to the CATALOGED policy.
- UNCATALOGED(codes)
- TAPEAUDIT enforces this policy by requiring retention codes to have no entries in the z/OS
catalog.
A data set with one of the specified retention codes is not extracted for TLMS versus catalog matching. If the data set is cataloged, a mismatch message is written indicating the data set should not have been cataloged.
For example: UNCATALOGED(57) Specifying “5” and “7” removes these codes from the default ALLCATALOGED policy and adds them to the UNCATALOGED policy.
- IGNORE(codes)
- TAPEAUDIT allows you to name those retention codes that you want TAPEAUDIT to ignore and not use
when checking for errors. Use IGNORE for data sets with a retention code that are
inconsistently cataloged for processing or historical reasons.
No retention codes are suppressed unless this keyword is specified.
For example: IGNORE(57) Specifying “5” and “7” removes these codes from the default ALLCATALOGED policy and adds them to the IGNORE policy.
- SUPPRESS
- Optionally stops TAPEAUDIT from performing a specific function.
The values for specific fix types are:
- MATCHBADUCAT
- A data set name was found in both the catalogs and in the tape system. This matching data set name was found in a catalog other than the catalog indicated by its catalog alias in the master catalog.
- MATCHNOALIAS
- A data set name was found in both the catalogs and in the tape system. This matching data set name has no catalog alias.
- MATCHINCORRECT
- A data set name was found in both the catalogs and in the tape system. This matching data set name does not have matching volser, volume sequence number, or file sequence number.
- MATCHCATALOG
- A data set name was found in both the catalogs and in the tape system. This data set is not defined in the catalog that matches its catalog alias.
- NOROLLEDOFF
- Stops TAPEAUDIT from commenting any DEFINE NONVSAM statements generated for ONLYTAPEGDS. These statements are normally commented to prevent GDG LIMIT from being exceeded.
- ONLYCATALOGED
- The data set name is only found in the catalogs.
- ONLYTAPE
- The data set name is only found in the tape database.
- ONLYTAPENOALIAS
- The data set name is only found in the tape database and there is no catalog alias for the data set name.
- TAPEDUPERROR
- The tape database has multiple copies of the data set name.
- TAPESEQERROR
- A multi-volume data set in the tape database does not have a sequentially increasing volume sequence number starting with 1.
- TAPEMAXERROR
- The tape database has multiple copies of the data set name that exceed an internal limit of the TAPEAUDIT command.
- RECHECK
- Suppressing RECHECK stops TAPEAUDIT from validating the problems found by re-reading the catalog and tape database.
- ENQTEST
- Suppressing ENQTEST stops TAPEAUDIT from performing a test ENQ during re-checking. This test is normally done to ensure that the data set is not currently being written to and that the catalog and tape systems are not being changed for this data set.
Usage notes
- TAPEAUDIT prints messages for each problem that is encountered as they are discovered. At the end of processing, these problems are analyzed so that the best fix is created.
- During the time that TAPEAUDIT is extracting the catalog and the tape database records, data sets can be created or deleted. These changes may appear as problems that TAPEAUDIT will attempt to revalidate before creating fixes. Problems related to missing aliases and cataloged data sets in the wrong catalog will not be revalidated.
- TAPEAUDIT should not be scheduled to run during the time the your tape managements daily expiration-date processing occurs.