Previous Topic: SUTMYN Automated Tape LibraryNext Topic: Recommendations and Considerations


Setting Up an Automated Tape Environment With the ATL

To set up the ATL interface to CA VM:Tape, add a PRODUCT LMS record to the VMTAPE CONFIG file to identify the LMS service virtual machine. Then add or modify the DEVICE record in the VMTAPE CONFIG file to include tape drives that are inside or outside the ATLs:

  1. End CA VM:Tape.
  2. Edit the VMTAPE CONFIG file:
    1. Add a PRODUCT LMS record to identify the user ID of the LMS service virtual machine running the LMS code:
      PRODUCT LMS userid
      

      For more information, see PRODUCT record.

    2. Add or modify a DEVICE record to include tape drives that are inside or outside the ATL. The DEVICE record identifies tape drives CA VM:Tape will manage, including those inside or outside the ATL.

      To identify any ATL devices, add or modify the DEVICE record in the VMTAPE CONFIG file as follows, replacing devices with the list of ATL devices:

      DEVICE devices
      

      You can use the NAME parameter on the DEVICE record to group tape drives. You can then direct tape mounts to a specific set of drives by specifying the group name using the NAME parameter on the MOUNT command. You can also use the LOCATION option on the MOUNT command to direct mounts to specific ATL locations.

      For more information, see DEVICE record.

    3. You can optionally add one or more LMSRANGE records to indicate specific ranges of tapes for CA VM:Tape to consider belonging to a specific LMS location:
      LMSRANGE start_vol-end_vol location
      

      Note: If you implement LMSRANGE config file records, synchronization with the SUTMYN robot is bypassed during CA VM:Tape REFRESH processing.

      For more information, see LMSRANGE record.

  3. Save and exit the VMTAPE CONFIG file.
  4. Define scratch pools in CA VM:Tape. For information about setting up CA VM:Tape scratch pools, see Scratch Pool Definition File. For information about using CA VM:Tape scratch pools with the LMS interface, see Scratch Pools.
  5. Before you initialize CA VM:Tape, ensure that the volsers that are already inside the ATL are defined in the CA VM:Tape TMC. For instructions on adding the volsers and adding or removing volser series in the VMTBUILD utility, see VMTBUILD Utility.

    If volsers inside the ATL are already defined in the CA VM:Tape TMC, you can continue to the next step.

  6. Restart CA VM:Tape.
  7. Use the CA VM:Tape LMS command with the START parameter to initialize the LMS interface, synchronizing the locations of the tapes in the ATL with the CA VM:Tape TMC:
    vmtape lms start
    

    Because CA VM:Tape is defining the tape locations in the ATL for the first time, this step will take a few minutes to complete.

    Note: For more information about the LMS command, see the Command Reference Guide.

  8. To make the ATL the default location for all scratch tape mount and allocate requests, use the CA VM:Tape SET LOCATION command. If the ATL location is not available, CA VM:Tape uses tape drives outside the ATL the NONARM drives.

    For example, to specify the ATL location ATLARM01 as the default location, enter:

    vmtape set location atlarm01
    

    Note: For more information about the SET command, see the Command Reference Guide.

  9. You can now use the ATL with CA VM:Tape.