Sharing the CA 1 TMC › Setting Up a Shared TMC

Setting Up a Shared TMC

The CA VM:Tape interface to CA 1 allows you to share a single TMC between VM and z/OS systems.

Before you can use the CA VM:Tape interface to CA 1, you need to set up a shared TMC using the CA VM:Tape OSTMC, OSAUDIT, SMFID, and USEREDIT configuration file records.

To set up the CA 1 interface to CA VM:Tape, follow these steps:

1. Edit the VMTAPE CONFIG file and add an OSTMC and an OSAUDIT record to identify the virtual address and data set names of the OS format TMC and Audit files.

   The OSTMC record identifies the virtual address and data set name of the OS format CA 1 TMC data set. If the OSTMC is used, the SMFID must also be set. For more information, see OSTMC record.

   The OSAUDIT record identifies the virtual address and data set name of the OS format CA 1 Audit data set. For more information, see OSAUDIT record.

2. Verify that the TMC data set and Audit data set reside on separate, real DASD volumes.

   Note: Step 3 does not apply if have you run TMSXTEND. It only applies if you use an old version CA 1 and have not run TMSXTEND.

3. Prepare the CA VM:Tape USEREDIT user exit to provide the identical translation for CA VM:Tape that the TMMVOLDF MACRO provides for CA 1 assemblies.

   The USEREDIT user exit identifies the name of an assembler language user exit that translates installation standard volsers into relative record pointers to volume records in the TMC. This exit is required.

   Note: For more information about the USEREDIT user exit, see Utility Reference.

   1. Examine the TMSVOLDF ASSEMBLE prototype file that is provided with CA VM:Tape. You will need to customize this file to provide the correct translations for TMC volume record access at your site.

      The TMSVOLDF ASSEMBLE file must be changed to contain the TMMVOLDF macro statements that are identical in format and sequence to those used with CA 1. You can use the CA 1 utility TMSBLDUE to produce the correct list of TMMVOLDF macro statements that must be included to correctly customize your TMSVOLDF ASSEMBLE file.

   2. Obtain a copy of the TMMVOLDF MACRO from the CA 1 program product libraries. This macro is required to assemble your customized copy of TMSVOLDF ASSEMBLE.

      After you have the macro on the CA VM:Tape 191 minidisk, you must generate a CMS MACLIB which contains the TMMVOLDF MACRO. For example, use the following instructions to create the CMS MACLIB named TMMVOLDF that includes the TMMVOLDF MACRO:

      maclib gen tmmvoldf tmmvoldf
      

   3. Assemble your customized copy of TMSVOLDF to produce the TMSVOLDF TEXT file needed to provide correct translations for TMC volume record access at your site. For example, issue the following commands to perform the assembly:

      global maclib tmmvoldf dmsgpi dmsom osmacro
      assemble tmsvoldf
      

   4. Examine the LISTING file produced for errors. Ensure that the TMSVOLDF TEXT file was created as part of the assembly.

      Note: The USEREDIT exit is only used if the TMC has not been extended using the CA 1 TMSXTEND utility.

   5. The USEREDIT user exit requires two text files. The "static" portion, TMSEXITU TEXT provided with CA VM:Tape; and the "customized" portion, TMSVOLDF TEXT that you created as instructed above. Both text files must reside on a minidisk accessed by CA VM:Tape, usually the 191 minidisk. The static portion (TMSEXITU) dynamically loads the customized portion (TMSVOLDF). Therefore, your USEREXIT USEREDIT record in the VMTAPE CONFIG file should be entered as:

      USEREXIT USEREDIT TMSEXITU