If you are using a tape management system, you can set up TSM to use scratch tapes from the scratch pool controlled by the tape management system. Although tape management systems vary, the procedure for setting up TSM to work with them follows the same basic steps:
When TSM requires a new scratch volume, it asks for a private mount. The tape management system can then give TSM a volume from the scratch pool. However, in most installations, the operator selects the scratch volume from a list provided by the tape management system. The tape management system verifies that the volume mounted is a scratch volume. TSM uses the volume serial number of this tape to define the volume to the storage pool. The tape label is rewritten with the expiration date from the device class, if it was specified, and the data set name.
When the tape volume becomes empty, usually due to reclamation, it is deleted from TSM. During the deletion process, the tape deletion exit is called and notifies the tape management system that it can return the tape to the scratch pool. See Setting Up Tape Installation-Wide Exits for details about the exit.
If you are using IBM's DFSMSrmm or DFRMM tape management system products, you do not have to define TSM to either of them. The Removable Media Manager is designed to support all tape data sets, including those created by TSM and DFSMShsm.
If you are using a different tape management system product, refer to the product documentation. Defining TSM to tape management systems varies by product, and it is important that you understand how to complete this task for the one being used by your installation.
If your tape management system uses program names to identify External Data Managers, the TSM program name is ANRSERV.
You might need to tell the tape management system that a volume must be permanently retained.
If you are using IBM's DFSMSrmm or DFRMM tape management system products, you should define policies (vital record specification's) to cover the TSM tape data sets. A single policy specifying the TSM high level qualifier is sufficient to include all TSM tape data sets.
You can retain all DFSMShsm tapes that require no movement, with the exception of tapes written by ABARS, by specifying the RMM TSO subcommands shown in following example:
RMM ADDVRS DSNAME('mprefix.**') COUNT(99999) OWNER(owner) RMM ADDVRS DSNAME('bprefix.**') COUNT(99999) OWNER(owner) RMM ADDVRS DSNAME('authid.**') COUNT(99999) OWNER(owner)
where:
For more information on defining policies, refer to DFSMS/MVS DFSMSrmm Implementation and Customization Guide. For more information on vital record specifications, refer to DFSMS/MVS DFSMSrmm Guide and Reference.
If you are using a different tape management system, one of the most commonly used ways to specify permanent tape retention is to set up the expiration date in the TSM device class definition.
You should keep the following in mind when setting up the expiration date:
You can update a cartridge device class for permanent retention by entering the following command:
update devclass cartridge expiration=99365
+---------------------Programming interface information----------------------+
You must use the deletion installation-wide exit to notify your tape management system that the Tivoli Storage Manager server has deleted a tape from its database. This exit can provide a tape management system with the information required to maintain an accurate inventory of TSM tapes. However, you do not have to use this exit to use tapes with TSM.
The deletion exit is called when the TSM server is returning a tape to scratch after it no longer contains valid files, and when the DELETE VOLUME command is used to delete a volume from the database. The tape volume is deleted from the TSM server database before the deletion exit is called.
To use the deletion exit, include the DELETIONEXIT option in the server options file. Specify the name of the module on the option. If you are using a tape management system, specify the module name of the deletion exit provided by the tape management system. For example, if you are using the DFSMShsm ARCTVEXT module, specify:
DELetionexit ARCTVEXT
DFSMSrmm provides a programming interface called EDGTVEXT that can be used instead of ARCTVEXT.
The deletion exit allows your tape management system to accurately reflect the server tape usage. You need to use the tape management system facilities to notify itself that the server has deleted the tape from its database. After the deletion exit sends the notification to the tape management system, it returns control to the server. Tape deletions cannot be cancelled.
If you are using DFSMSrmm or DFRMM, the vital record specification policy is used to determine the management of the volume. If you are using a different tape management system, it should recognize that the volume is being managed by an external data manager (EDM). It should then insure that only TSM has access until the volume is returned to the tape management system's control via the DELETIONEXIT.
If you are using the DFSMShsm ARCTVEXT exit or the DFSMSrmm exit or a deletion exit supplied with a tape management system, include the coding required for the TSM deletion exit in your existing exit. The coding considerations for this exit are similar to those for the DFSMShsm ARCTVEXT exit or the DFSMSrmm exit, including entry and exit linkage. A non-zero return code or an abend in the exit results in an error message but has no other effect on TSM processing.
The deletion exit must be reentrant and run in either the 24-bit or 31-bit addressing mode (AMODE). You should always return to the caller in the caller's AMODE.
The registers contain the following information on entry to the deletion
exit:
Register | Description |
---|---|
1 | The address of the parameter list passed to the exit. |
13 | The address of a 72-byte standard MVS save area. |
14 | The address to which the exit must return control. |
15 | The address of the deletion exit. |
0, 2-12 | These registers contain nothing of use to the exit. |
Table 4 shows the parameter list passed to the tape deletion
exit. Register 1 contains the address of this parameter list.
Table 4. Deletion Exit Parameter List (MVS)
Offset | Length (bytes) | Data Type | Description |
---|---|---|---|
0 (X'00') | 4 | Address of the data area | Pointer to an 8-byte data area containing information about the volume the server has deleted from its database. Table 5 shows the format of the data area. |
4 (X'04') | 4 | Address of the return code | The address of a full word containing the return code that the exit must set after completing processing. The return code is binary, and should be 0 if processing is successful, or any other number if processing is unsuccessful. TSM generates an error message if the processing is unsuccessful. The high order bit of the return code address is set to 1. |
Table 5 shows the format of the data area pointed to by the deletion
exit parameter list.
Table 5. Deletion Exit Data Area (MVS)
Offset | Length | Data Type or Bit Pattern | Description |
---|---|---|---|
0 (X'00') | 6 | Character | The volume serial number of the tape volume deleted from the database. |
6 (X'06') | 2 | Binary | Informational flags. |
1... .... .... .... | The tape volume is purged from the server's database. | ||
.1.. .... .... .... | The server has protected the files on the volume with expiration
dates. This information is determined from the device class associated
with the volume.
| ||
.... .... 1... .... | The DFSMShsm SCRATCHTAPE option was used on the SETSYS TAPEDELETION command for this tape category. | ||
.... .... .... ..1. | Backup tape. |
When you return control to the server, restore the registers to the values they had on entry.
+------------------End of Programming interface information------------------+