StorageTek Silo Managed by CSC

1. Specify CSC as one of the values for the RBTTYPE parameter in the CTTPARM member (through Control-M/Tape step 2.10 in ICE).
2. Use the ICE Automatic Exit Installation Tool to compile the CTTRCSC member. For details about this tool, see the exits chapter in the INCONTROL for z/OS Administrator Guide).
3. Save the CTTRTM procedure under the name CTTRTM2. Rename the CTTRTMC procedure in the procedure library to CTTRTM. The new CTTRTM procedure contains an additional step (CTTRBM) that interfaces with the StorageTek Silo.
4. Allocate a sequential file as a fixed block with a record length of 80 bytes. Use the value specified for the %OLPREFT% parameter in the DEFPARM member to name this file as follows:

   olpreft.DASCRCMD

   This sequential file should be large enough to hold the maximum number of volumes that might be expired by the CTTRTM utility in one day (one record per volume).

   Note: StorageTek CSC cannot perform automatic ejects. After running the CTTVTM utility, all necessary ejects must be performed manually.

   No application Program Interface (API) is supplied with StorageTek CSC. For this reason Control-M/Tape uses the SCUADMIN CSC utility to notify CSC about expired tapes. As a result of this method of operation, note the following:

   CSC is not notified when a volume status is modified manually from the Control-M/Tape Online environment or through the CTTMUP utility.

   When an External Data Manager (EDM) is set to scratch volumes immediately, CSC is not notified of the scratched tapes. It is therefore recommended that the EDM exit (for example, ARCTVEXT for DFSMShsm) scratch volumes in deferred mode. When deferred mode is used, EDM volumes are given the status PENDING SCRATCH by the EDM exit, and are scratched by the CTTRTM utility the next time it is run, at which time CSC is notified.