StorageTek Automated Cartridge System function
This sectionprovides a description of the interface to the ACS and the logic that ACS Support uses to classify cartridges.
Description
In order to provide accurate unit counts during Job Analysis, ThruPut Manager must know which unit names are used for the StorageTek Automated Cartridge System (ACS), and how they are used. The following description explains this interface.
Implementation Summary
ThruPut Manager provides an interface to the StorageTek ACS. The call to the interface is issued automatically.
Dependencies
You must install the Host Software Component of the ACS at the appropriate level. It must include the Programmatic Interface.
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.
How ACS Support Works
This description does not apply to virtual tape volumes. Please refer to Virtual-Tape-System-support.
For installations with an ACS, ThruPut Manager provides a means to determine whether a given cartridge is ACS managed.
The ACS support function works as follows:
- At TMSS initialization time, the ACS Programmatic Interface is called. If the LOAD macro fails, TMSS terminates with appropriate messages. Otherwise, TMSS automatically detects AUTOMATED and MANUAL units.
- During resource determination, ThruPut Manager's ACS support uses the following logic to determine when to interrogate the ACS API:
- For a non-specific request, no ACS call is made:
- If the unit name matches any of the unit names detected as MANUAL, it is treated as a MANUAL (non-ACS) request.
- If the unit name does not match any of the unit names detected as MANUAL, it is treated as an AUTOMATED (ACS) request.
- For specific requests, ThruPut Manager interrogates the ACS interface to determine whether or not the cartridge is resident:
- If the cartridge is resident, it is treated as an AUTOMATED (ACS) request, unless a unit name was coded in the JCL:
- If the unit name is detected as MANUAL, the volume is treated as a MANUAL (non-ACS) volume.
- If the unit name is not detected as MANUAL, the request is treated as an AUTOMATED (ACS) volume.
- If the cartridge is not resident and a unit name was coded in the JCL, then:
- If the unit name is detected as AUTOMATED, it is treated as a cartridge to be returned to the Automated Library System.
- If the unit name is not detected as AUTOMATED, the request is treated as a MANUAL (non-ACS) volume.
- If the cartridge is not resident and a unit name was not coded in the JCL, it is treated as a MANUAL (non-ACS) volume.
- If failure occurs during Job Analysis, a non-deletable message is issued and the cartridges are treated as manual cartridges. The Job Analyzer continues to interrogate the interface for each cartridge, but no further messages are produced if the interface fails. Once the interface is re-established, the non-deletable message is removed.
Facilities Summary
ACS Exits | ||
---|---|---|
Exit # | Exit Name | Description |
Exit 4 | Unit Name/Device Type | A flag is provided to indicate that an ACS esoteric unit name has been encountered. |
Exit 5 | Volume Status | A flag is provided to show that ACS has responded to the ThruPut Manager, indicating that the volume is ACS managed. |
Exit 6 | Job Action Modification | Three ACS related Job descriptors are provided: The maximum number of ACS managed drives, the number of ACS volumes, and the minimum number of ACS scratches. |