Previous Topic: TMSSPLIT Utility—Select Data from the TMC for Use by TMSMERGENext Topic: Report Description

Utilities › TMSSPLIT Utility—Select Data from the TMC for Use by TMSMERGE › Considerations

Considerations

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 along with the export tape. If not, you may wish to consider providing 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, 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, 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 you should run TMSPTRS to insure that there are no problems in the DSNB chains of the ranges to be processed.