VMTBUILD Utility (CMS TMCs Only)

Use the VMTBUILD utility to build TMC and Audit files from TMC input files and the specified configuration file. Use the VMTBUILD utility to do the following:
vmtzvm
Use the VMTBUILD utility to build TMC and Audit files from TMC input files and the specified configuration file. Use the VMTBUILD utility to do the following:
  • Create a TMC or Audit file
  • Add or delete SERIES records from the TMC
  • Split a TMC
  • Recreate a TMC from a backup TMC and Audit file
 For more information about the processing messages generated during VMTBUILD, see 
Message Reference.
 
 
Contents
 
 
 
Utility Syntax
This utility has the following syntax:
VMTBUILD {TMC [
ddname1
...[
ddname10
]] [("Options"] | AUDIT [(PRINT]} Options: [CONFIG
filename
] [DELETE] [PRINT]
Parameter Descriptions
A description of each parameter follows:
  •  
    TMC
    Specifies that a TMC file is to be created. Use this parameter to create the initial TMC. You can also use this parameter to add SERIES records to an existing TMC, remove SERIES records from a TMC, split a TMC, or recreate a TMC from a backup TMC and Audit file if the TMC is lost. CA VM:Tape obtains the TMC fileid from the CMSTMC record in the VMTAPE CONFIG file; the TMC fileid must not already exist. Also, CA VM:Tape obtains SERIES records from the VMTAPE CONFIG file to determine the tape volsers to be included in the new TMC.
  •  
    ddname1 ...[
    ddname
    10]
    Specifies up to 10 input file ddnames that contain TMC or Audit file record images. CA VM:Tape applies the records to the new TMC in the order specified.
    Before issuing the VMTBUILD command, you must issue a CMS FILEDEF command for each 
    ddname
     specified on the command line. The input files you specify on the FILEDEF commands can be on tape or disk.
  •  
    AUDIT
    Specifies that an Audit file is to be created. CA VM:Tape obtains the Audit fileid from the CMSAUDIT record in the VMTAPE CONFIG file; the Audit fileid must not already exist.
  •  
    CONFIG
     filename
     
    Specifies the name of the configuration file containing the SERIES, CMSTMC, and CMSAUDIT records that define the output files. The filetype is CONFIG. The file can reside on any accessed disk. If not specified, filename defaults to VMTAPE.
  •  
    DELETE
    Specifies that all TMC records are to be marked as deleted volumes instead of scratched volumes when there is no input volume record that matches a new TMC record. (SCRATCH is the default status.) Volume records marked as being deleted in the TMC are placeholders for future expansion; that is, there is no corresponding real tape in the library, although there is expected to be one in the future.
    Tapes with a deleted status can be made available for scratch use with the TAPEINIT command. For more information, see TAPEINIT Command in the 
    Command Reference
    .
    Note:
     If you have specified one or more 
    ddnames
     on the command line, the input file that has a matching record in the TMC will be applied, thereby overlaying the deleted record. The only records that remain deleted when a new TMC is built are those not overlaid by any of the records in the input files.
  •  
    [PRINT]
    Specifies that informational messages about the formatting of the new files should be printed on the virtual machine printer and on the console.
How VMTBUILD Works
VMTBUILD reads the SERIES records in the specified CA VM:Tape configuration file, then builds a TMC with default scratch or deleted volume records and the volser and media type fields obtained from the SERIES record.
Next, VMTBUILD reads, in turn, each input file pointed to by the 
ddnames
 you specified on the command line. For each volume record, VMTBUILD overwrites the corresponding record in the new TMC. Thus, record by record, the new TMC inherits the information from the input files. For example, if the volser ABC123 is found in both 
ddname1 
and 
ddname10
, the record is overlaid twice, and ultimately, the information from 
ddname10
 remains in the new TMC.
Volser information in an old TMC used as an input file overwrites the corresponding volser information in the new TMC. Thus, you cannot change the SERIES record in the VMTAPE CONFIG file to indicate that the media is a cartridge tape (when before it was a reel), and use VMTBUILD to perform the necessary conversation of the TRTCH and DEN values for you. The new TMC will ultimately be rewritten with the TRTCH and DEN values from the old TMC.
Never try to merge two TMCs that have (or have ever had) identical volsers without first rebuilding each TMC individually to delete all the overlapping volsers. This initial step also removes any references in each TMC to volsers that are now obsolete. When you run VMTBUILD for a second time to merge the two TMCs, no volume in one TMC refers to a volume from the other TMC.
The optional input files are applied to the new TMC one at a time in the order specified (left to right). The input files are presumed to be specified in chronological order, with the first or leftmost containing the oldest data and the last or rightmost containing the newest data. Duplicate volser data in the newer files replaces the older data in the new TMC.
For input file FILEDEFs, you 
must
 specify the LRECL option if the input file is on a non-CMS minidisk:
  • The value must be 340 for the TMC or 370 for the Audit file.
    You can use the following data files (TMC-
    like
     files, except for Audit files) as input from various sources:
  • Current CMS TMC and Audit file
  • CA VM:Tape backup of a TMC or Audit file
  • Output from the VMTCON utility
Before Running VMTBUILD
If you are using VMTBUILD to build the TMC and the Audit files, protect against data loss from DASD failures by putting the TMC and Audit files on separate real DASD volumes.
Be sure that CA VM:Tape is not running before you run VMTBUILD from the CA VM:Tape user ID.
If the TMC you are building is shared, shut down all CA VM:Tape systems that share the TMC before you run VMTBUILD. The system from which you run VMTBUILD should be shut down last or you will need to reaccess the TMC minidisk before you run VMTBUILD.
If input to VMTBUILD is a CA VM:Tape backup of a TMC or Audit file, FILEDEF commands must use the same label type that was used when the file was backed up.
 For more information about example of using the utility, see "Recovering the TMC" in Backing Up CA VM:Tape (CMS Only).
Be sure the specified or default configuration file resides on an accessed minidisk because VMTBUILD uses it to obtain the SERIES records and filenames and filetypes of the output files.
Be sure the TMC and Audit output files specified in the configuration file do not exist or have been renamed before executing VMTBUILD. Make a backup copy of the current TMC and Audit files before running VMTBUILD.
If you do not provide the current TMC as input to the VMTBUILD utility, all current TMC information will be lost. This could result in data loss, because saved tapes will no longer be protected; they will be in scratch or deleted status and available to be used again.
Examples
 
Adding or Removing Volser Series
 
You must perform this operation whenever the configuration file SERIES records are in any way modified or reordered to:
  • Add a new series
  • Extend an existing series
  • Delete a series
  • Reorder the series in the TMC
For example, to add a new series of 100 reels (SYS001 through SYS100) to your TMC, follow these steps:
  1. End CA VM:Tape.
  2. Edit the VMTAPE CONFIG file and add the following record:
    SERIES SYS001 100 REEL
  3. Rename the current TMC (as specified on the CMSTMC record) to OLDTMC TMC B:
    rename vmtape tmc b oldtmc tmc b
  4. Issue a FILEDEF command to define input data from the old TMC to the current TMC:
    filedef currtmc disk oldtmc tmc b
  5. Run VMTBUILD:
    vmtbuild tmc currtmc
    CA VM:Tape responds as follows:
    INITIALIZING THE NEW VOLUME LIBRARY FILE ‘VMTAPE TMC B’ ... INITIALIZATION COMPLETE -- 239 RECORDS PROCESSING INPUT FILE 1 DDNAME=CURRTMC 241 RECORDS READ -- 3 RECORDS IGNORED VOLUME RECORDS: 236 APPLIED AND 0 REJECTED DATASET RECORDS: 4 PASSED 0 REJECTED 0 IGNORED PROCESSING MULTI-VOLUME AND MULTI-DATASET TAPESETS 0 VOLUMES DROPPED FROM MULTI-VOLUME TAPESETS 3 MULTI-VOLUME TAPESETS 2 MULTI-DATASET TAPESETS FINAL NUMBER OF DATASET RECORDS IS 4
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
 
  • If CA VM:Tape is running, end it.
  • Rename the current TMC (as specified on the CMSTMC record) to OLD TMCTMC B:
    rename vmtape tmc b oldtmc tmc b
  • Issue a FILEDEF command to define input data from the old TMC to the current TMC:
    filedef oldtmc disk oldtmc tmc b1
  • 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
  • Rename the current TMC (as specified on the CMSTMC record) to SYSA TMC B:
    rename vmtape tmc b sysa tmc b
  • Run the second execution of VMTBUILD to rebuild the production TMC without the extracted volumes:
    vmtbuild tmc oldtmc (config sysb
  • Move SYSA CONFIG and SYSA TMC to the appropriate system.
  • Erase VMTAPE CONFIG and rename the SYSB CONFIG file to VMTAPE CONFIG before initialization.
    rename sysb config b vmtape config b