|
|
|
|
|
As soon as validity checks have been completed and the job is allowed access to the data set on the volume, Control-M/Tape records relevant information in the volume and data set records in the Media Database.
When a new data set is created, Control-M/Tape records the data set attributes such as block size, record length, record format, and so on in the data set record of the Media Database. The open count, number of active data sets on the volume, and so on are also recorded in the volume record of the Media Database.
Whenever a volume’s data set is opened, Control-M/Tape updates "last access" information in the data set record. This information includes: Date, time, job name, step name, DD name, program name, CPU ID, device address, and step completion code. These fields are tracked and stored as separate fields for the following events: Last read access, last write access and creation time. The volume record also contains last access date, time, and job name.
When a data set is opened, Control-M/Tape updates the data set information in the Media Database with its abend retention period. If the data set is closed normally, the data set is updated with its normal retention period. This ensures that, in case of system crash before the data set is closed normally, the abend retention period for the data set is established.
When "end of volume" is encountered, Control-M/Tape chains together the volumes of a multi-volume data set. "End of volume" processing is actually a combination of "close" processing for the old volume and "open" processing for the new volume.
When a data set is closed, Control-M/Tape updates the following:
Retention and vaulting information are updated for new data sets and for data sets created dynamically by Control-M/Tape. The vault pattern is updated only if the volume contains no previous vault pattern. The retention and vaulting information are obtained from the rule table currently in memory, as described in Rule Search.
Parent Topic |