The TYPE control statement specifies the types of audit records to print. This control statement is required. The format for the TYPE control statement is:
1 6
TYPE=n[,...,n]
Control Statement Definition
Is the control statement identifier and must start in position 1.
Is the type of Audit record. A maximum of six types can be requested. The allowable values for this type are:
Definition
TMC records which have been updated manually or through CA 1 batch programs.
Tapes which have been opened/closed for input.
Tapes which have been opened/closed for output.
Exception records. These records are flagged with exception codes. The exception codes and their meaning are explained in the following section:
002— Image before updates if the AUDB4 option is set to ALL or BATCH.
003— Nonresident multifile record for output.
004— Nonresident input volume.
005— Nonresident output volume.
006— Nonresident multivolume.
007— Nonresident tape initialized.
008— Control Record manually updated.
013— A mixed expiration date was encountered and the system set the option MIXEXP to WARNING or LOG.
014— A mixed expiration date was encountered and the system set the option MIXEXP to DISALLOW.
CLA— TMSSMF83 creates this record. The operating system cataloged this data set, which was already indicated as being cataloged within the TMC. The bit TMISCAT of TMFLAG4 for the volume record or the bit DSNBISCA of DSNBFLG1 for the DSNB record indicate the state. The data set is probably cataloged on more than one system. As soon as it is uncataloged on one of the MVS catalogs, the flag is turned off.
CLB— TMSSMF83 creates this record. A volume of this multivolume set, which has been cataloged, does not have the proper volume sequence number as indicated in the TMC. The volume was probably cataloged out of sequence or the volume sequence number in the TMC is incorrect. Verify the volume chaining of the volume set. Run TMSPTRS, if needed.
CLC— TMSSMF83 created this record. The previous volume of this multivolume data set that is cataloged was not chained to this volume in the TMC. The current volume is not the last of the volume set. Check the volume chaining of the volume set. Run TMSPTRS, if needed.
CLD— TMSSMF83 created this record. The current volume that is cataloged is not a part of the multivolume data set that is defined to the TMC. The volume is not in scratch status. If the catalog operation including this volume should add this volume to the volume chain, chain it manually.
CLE— TMSSMF83 created this record. A volume of this multivolume data set that is cataloged is not a part of this multivolume data set that is defined to the TMC. The volume is in scratch status but the TMERASE bit of TMFLAG3 in the TMC volume record is on. If the catalog operation including this volume should add this volume to the volume chain, erase the volume and chain the volume manually.
CLF— TMSSMF83 created this record. A volume of this multivolume data set that is cataloged is not a part of this multivolume data set that is defined to the TMC. The volume is in scratch status but it is also in delete status. If the catalog operation including this volume should add this volume to the volume chain, chain the volume manually.
CLG— TMSSMF83 created this record. A volume of this multivolume data set that is cataloged is not a part of this multivolume data set that is defined to the TMC. The volume is not being chained following the last volume of the volume set. If the catalog operation including this volume should add this volume to the volume chain, chain the volume manually.
CLH— TMSSMF83 created this record. A volume of this multivolume data set that is cataloged is not a part of this multivolume data set that is defined to the TMC. The volume is in scratch status but it is not in delete status. The volume should be in delete status because the previous volume in the volume chain has the TMACTVOLI flag of TMFLAG4 turned on. If the catalog operation including this volume should add this volume to the volume chain, chain the volume manually.
CLI— TMSSMF83 created this record. A catalog or recatalog request was being processed for the first file of a volume. The volume sequence number, on the TMC, was not equal to one. A recatalog request specifying multiple volumes for the first file in the wrong order causes this state.
CLJ— TMSSMF83 created this record. A catalog operation for a tape GDG caused more than 50 generations of the GDG data set to be uncataloged. CA 1 updates only the TMC records of the 50 oldest generations and turns off the OSC flag bits. The Audit record shows the last generation that was processed successfully. If any newer versions of the GDG data set that are no longer cataloged are required, update them manually.
EDA—This record was created when an External Data Manager called TMSTMSTV to release a tape volume. Either the volume is not flagged as externally managed, or it does not match any active EDM rule.
Verify the status of the volume and the EDM rules defined in PPOPTION member TMOEDMnn. If necessary, use TMSUPDTE to clear the EDM information and to expire the tape manually.
EDB—This record was created when an External Data Manager called TMSTMSTV to release a tape volume. The TMC volume was part of a multifile or multivolume chain, which is not valid for an EDM tape.
Verify the status of the volume and the EDM rules defined in PPOPTION member TMOEDMnn. If necessary, use TMSUPDTE to clear the EDM information and to expire the tape manually.
SCR— Invalid multivolume chain found.
BYP— A user exit bypassed or modified an update of a record. Original record with CA 1 modifications is written using BYP.
Tapes which have been rejected for output.
CA 1 internal processing records. Type 5 Audit records contain control statement or message input, the name of the function, and the CPU ID that wrote the record. The audit record contains the date and time when the processing record was written. The Type 5 Audit record codes are:
001— Extension (TMSFORMT) or purge (TMSREMOV) job reformatted the TMC.
002— CA 1 initialization control statement input or messages.
003— Detects whether CA 1 is at the proper level to support the TMSXTEND process.
009— The Blockset Audit feature uses this record to fill out an audit block.
010— The Blockset Audit feature uses this record to record that a dormant system has been detected and the block has been marked full.
011— Volume pool monitor record that updates volume status counters.
012— Volume pool monitor record that updates product variables that various CA 1 utilities created.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|