CA1 - how split the current TMC file

Products

• CA 1 Flexible Storage
• CA 1 Tape Management - Copycat Utility
• CA 1 Tape Management - Add-On Options

Issue/Introduction

What it is procedure to split the TMC file which is shared between several partitions, to get own one TMC file per partition ? 

Environment

Release:
Component: 1

Resolution

Once the n systems are isolated to seperate ranges we can then use TMSGRW  to get a list of the volsers for each system.  Use this as input to TMSSPLIT
 to get the information from the TMC.  The output from TMSSPLIT will be used as input to TMSMERGE.

The TMSSPLIT and TMSMERGE can be found on the Utilities and Reports Guide.

<Please see attached file for image>

Considerations for TMSSPLIT

Review the following considerations before beginning the Split procedure.

1. CA 1 Catalog Control and Catalog Days Control of tape data sets (CATALOG, CATLG, CATLG/ddd in control statements and online interfaces, or LABEL=EXPDT=90ddd and LABEL=EXPDT=99000 in JCL) requires that CA 1 keep tapes out of scratch status as long as the data set has an entry in the system catalog. If possible, the system catalog information for these volumes should be made available to the receiving site with the export tape. If not, you may want to provide a different EXPDT value to the affected records prior to TMSSPLIT execution.
2. If any tapes going to the receiving site are under Vault Management System control, adjustments must be made if the receiving site is using identical vault names (OUTCODEs) as the sending site. Through redefinition of the vault pattern control statements, these tapes can be assigned a new vault name or removed from VMS control entirely. Have a copy of the sending site's pattern ready for the receiving site so the patterns can be integrated.
3. If the sending or receiving site uses the Scratch Pool Management feature, integrate or built the hlq.CTAPOPTN members defining the tape pool options. Console operators and users should be informed of any visible changes this may cause. The same holds true for the CA 1 options that are defined in the TMOOPTxx and TMOEDMxx members of hlq.CTAPOPTN, and the Pull data set used by TMSPULL. A Retention Data Set (used by TMSEXPDT) in use at either location also requires similar accommodation.
4. A split/merge operation should not be performed when the sending site's ranges are identical to ranges currently reflecting nonscratch data sets in the receiving site's TMC. The merge operation requires that the Volume records for the import data set be properly formatted in the receiving TMC. They should be in either scratch or inactive (DELETE) status.
5. Before running TMSSPLIT, run TMSPTRS to verify that there are no problems in the DSNB chains of the ranges to be processed.

 

Considerations for TMSMERGE

The receiving site should take the following into consideration:

• The use of Catalog Control and Catalog Days Control of tape data sets (CATALOG, CATLG, or CATLG/ddd in control statements and online interfaces, or LABEL=EXPDT=99000 and LABEL=EXPDT=90ddd in JCL) indicates that CA 1 keeps tapes out of scratch status as long as the CATLG-protected data set has an entry in the system catalog. If the system catalog information from the sending site is not immediately available to the receiving site, the batch utility TMSCTLG should not be executed until the system catalog is updated or the merged TMC records are updated with some other EXPDT value.
• If OCTLG=NO in hlq.CTAPOPTN member TMOOPTxx, run TMSOSCAT PARM=SYNC again if the receiving data is from a Version 5.2 system or below that has not had TMSOSCAT PARM=SYNC run against the data.
• If Volume records from the sending site are under Vault Management System control, the Vault Pattern entries from the sending site should be integrated into the receiving site's pattern prior to running any VMS utilities. If the sending site uses vault names (OUTCODEs) equal to vault names used in the receiving site, the sending site's vault pattern entries need to have the REDEFINED keyword option specified for each data set name affected to prevent duplicate slot errors.

• If the sending or receiving site uses the Scratch Pool Management feature, the hlq.CTAPOPTN members defining the tape pool options need to be built/integrated. Console operators and users should be informed of any visible changes this may cause. The same holds true for the CA 1 options defined in the TMOOPTxx and TMOEDMxx members of hlq.CTAPOPTN. The Retention Data Set used by TMSEXPDT, and the PDS used by TMSPULL, will require similar accommodation if either data set is in use at either location. 

  Note: When using PARM=DEFAULT with TMSMERGE, the FLAG1 =x’01’ ('eligible for RDS override') bit will be turned on in ALL the new merged TMC records. If there is a matching RDS entry, this allows that the EXPDT of the tape is overridden. To ensure that the proper expiration date is assigned to your datasets: review your RDS entries or incorporate your sending RDS entries into the receiving site’s Retention Dataset (RDS) before running TMSEXPDT. Otherwise, premature retention expiration may occur.

• A split/merge operation should not be performed when the sending site's ranges are identical to ranges in the receiving site's TMC that currently reflect nonscratch data sets unless new external VOLSERs are assigned. The merge operation requires that the Volume records for the import data set be properly formatted in the receiving TMC, and they should be in either scratch or inactive (DELETE) status. If TMSMERGE determines that you are overlaying an active record, it will free the DSNBs and break the volume chains and then do the overlay.
• The number of Audit records required to support the merge is specified on the TMSSPLIT output. This number is to be combined with the value of the number of Audit and DSNB records reported. The number is also relative to the Audit data set threshold level; should the level be reached TMSMERGE will terminate with a U0008 abend. Another consideration is that more than the number specified by TMSSPLIT is required if the merge overlays records that are active; that is, records not in scratch or delete status, especially if the volume records being overlayed are multifile volumes and the DSNBs associated with them have to be cleared and returned to the free chain by the merge process. Since the number of audit records needed if AIVS or foreign control statements are used is increased, plan for an additional audit record for each secondary volume and secondary VOLSER. A good practice would be to triple the number of AUDIT records based on the output from TMSSPLIT.
  Because RESTART cannot be used if AIVS or foreign control statements are used, the only way to recover from an abend situation is to restore the TMC. For this reason, CA 1 should be in batch active mode. It is recommended that a TEST parameter be used for the initial run to ensure there are no problems prior to the production run.