Previous Topic: ExamplesNext Topic: VMTCON Utility (CMS TMCs Only)


Splitting a TMC

Your site has been sharing one TMC between two CA VM:Tape systems, System A and System B. Due to a departmental reorganization in your company, it no longer makes sense to share the TMC. Because each system needs existing records in the TMC, you decide to split it. To split a TMC, follow steps similar to these:

  1. Create two new configuration files, SYSA CONFIG, containing the SERIES records used by System A, and SYSB CONFIG, containing the records used by System B, using the current production system configuration file. The resulting configuration files contain the following SERIES records:

VMTAPE CONFIG

SYSA CONFIG

SYSB CONFIG

SERIES AB0100 100

SERIES 1000 100

SERIES AB0100 100

SERIES 300000 4000

SERIES 300000 4000

SERIES 000 100

  1. If CA VM:Tape is running, end it.
  2. Rename the current TMC (as specified on the CMSTMC record) to OLD TMCTMC B:
    rename vmtape tmc b oldtmc tmc b
    
  3. Issue a FILEDEF command to define input data from the old TMC to the current TMC:
    filedef oldtmc disk oldtmc tmc b1
    
  4. Use the current TMC along with the SYSA CONFIG file to create a new TMC containing a subset of the records in the current production TMC.

    Two executions of VMTBUILD are necessary. Run the first execution of VMTBUILD to extract the volsers needed by System A from the old TMC:

    vmtbuild tmc oldtmc (config sysa
    
  5. Rename the current TMC (as specified on the CMSTMC record) to SYSA TMC B:
    rename vmtape tmc b sysa tmc b
    
  6. Run the second execution of VMTBUILD to rebuild the production TMC without the extracted volumes:
    vmtbuild tmc oldtmc (config sysb
    
  7. Move SYSA CONFIG and SYSA TMC to the appropriate system.
  8. Erase VMTAPE CONFIG and rename the SYSB CONFIG file to VMTAPE CONFIG before initialization.
    rename sysb config b vmtape config b