Interface Modules for Specific Vendors

When a request for an automated tape library function has been allowed by Exit 8 (described above), the central interface module passes the request to a module that is used to interface with a specific automated tape library.

Note: If more than one automated tape library type is in use at your site, a different interface module is used for each automated tape library. Each request is sent to one automated tape library interface module at a time, until either executed or rejected for all the automated tape library modules.

Control-M/Tape automated tape library interface modules use basic commands supported by the automated tape library API to perform certain tasks. For example, to scratch a volume, Control-M/Tape first uses the query command to verify that the volume is in the automated tape library and then uses the scratch command to scratch it.

The following basic commands are used by Control-M/Tape:

Table 21 Control-M/Tape Basic Commands

Note: Since only a base level API is used, the Control-M/Tape interface to the automated tape library should not be affected if the automated tape library software is upgraded.

To perform the above commands, Control-M/Tape uses a different interface module for each type of automated tape library.

The following table lists the interface modules that are provided with Control-M/Tape:

Table 22 Control-M/Tape Interface Modules

Note: The interface modules listed above are provided as samples. If necessary, they can be customized to comply with your site’s operating procedures. No functions supported for Comparex libraries are initiated by Control-M/Tape. Therefore, no interface module is necessary for the Control-M/Tape/Comparex interface.