Virtual Tape System support

This chapter describes the support for Virtual Tape Systems (VTS) provided in ThruPut Manager.

Description

In order to provide accurate unit and volume counts during Job Analysis, ThruPut Manager must know which unit names are used for Virtual Tape Systems (VTS). The following description explains this interface.

Implementation Summary

VTS support varies depending on the way your installation manages virtual tape volumes.

• For IBM 3495 Automated Tape Library Tape Dataserver (ATLDS) virtual volumes:
  • New virtual volumes are recognized by the storage group name, as detected automatically by ThruPut Manager.
  • Old virtual volumes are identified by calling the Library Management Software (LMS) interface to determine if the volume is associated with the detected library.
• For BTLS mode for the IBM 3495 ATLDS:
  • New virtual volumes are recognized by the unit name specified by the VTS_ UNIT keyword on the TM BTLS initialization statement.
  • Old virtual volumes are recognized by the library name as specified on the VTS_LIBRARY on the TM BTLS initialization statement.
• For StorageTek Automated Cartridge System (ACS) virtual volumes:
  • New virtual volumes are recognized by the unit name, as detected automatically by ThruPut Manager.
  • Old virtual volumes are identified by calling the Programmatic Interface of the ACS Host Software Component.
• For Sutmyn (Memorex) 5400 Automated Tape Library (ATL) virtual volumes:
  • New virtual volumes are recognized by the unit name, as specified by the VTL keyword of the TM ATL initialization statement.
  • Old virtual volumes are identified by calling the ATL Library Management Software interface.
• For VTFM virtual volumes:
  • New virtual volumes are recognized by the unit name, as specified by the ESOTERIC keyword on the TM VTFM initialization statement.
  • Old virtual volumes are recognized by the unit name, as specified by the GENERIC keyword on the TM VTFM initialization statement.
• For CA-Vtape (formerly SAMS:VTAPE) virtual volumes:
  • New virtual volumes are recognized by the DFSMS dataclass as specified by the DATACLAS keyword on the TM VTAPE initialization statement.
  • Old virtual volumes are recognized by calling the CA-Vtape API.

Dependencies

For StorageTek ACS, the Programmatic Interface must be installed. ThruPut Manager assumes that the program name is SLSXCAL, as documented in the StorageTek HSC System Programmer's Guide. It must be available to be called from any address space in your system.

There are no other specific dependencies for ThruPut Manager VTS support.

TMSS Initialization Statements

VTS support requires a TMSS initialization statement, but the specific statement required depends on the method your installation uses to manage virtual volumes:

• IBM 3495 ATLDS and StorageTek ACS virtual volumes managed by SMS are handled automatically by ThruPut Manager.
• StorageTek ACS virtual volumes are also handled automatically by ThruPut Manager.
• IBM 3495 ATLDS virtual volumes managed by BTLS require the TM BTLS initialization statement.
• Sutmyn (Memorex) 5400 ATL virtual volumes require the TM ATL initialization statement.
• VTFM virtual volumes require the TM VTFM initialization statement.
• CA-Vtape virtual volumes require the TM VTAPE initialization statement.

For descriptions of these statements, refer to TMSS-initialization-statements.

How ThruPut Manager VTS Support Works

ThruPut Manager can provide volume and unit counts for VTS once you provide initialization statements that reflect the way your installation manages virtual volumes. These counts are provided through Range Descriptors in JAL:

$SCRATCH_VTS
$UNIT_VTS
$VOL_VTS

Virtual volumes and units are not included in any other counts, e.g. the Range Descriptor $SCRATCH does not include virtual scratch volumes.

Facilities Summary