Using the DFSMSrmm client and server systems

This topic contains recommendations for using the client or server system.

In order to manage a single tape inventory across multiple sysplexes where there is no shared DASD available, you can create one or more DFSMSrmm client systems. Any tape usage on a client system uses the server system to dynamically validate and record tape usage. If the server system is not available for any reason, for example, the IP connection is unavailable or fails, you cannot use tapes on the client system until the server is reconnected or restarted.

All DFSMSrmm users on a client system can use the DFSMSrmm ISPF dialog, RMM TSO subcommands, and batch utilities, including use of DFSMSrmm API and High Level Language API.

Recommendation: Users who need regular access to DFSMSrmm data should log on to the server system. Storage administrators and tape librarians should use a server system or an DFSMSrmm system with direct access to the control data set except when there is a specific reason for using a client system.

Performing a task for a system-managed tape library that is known to the client and not the server.
- Ejecting a volume from a system-managed tape library
- Adding volumes to a system-managed tape library using STATUS(VOLCAT)
- Changing volume attributes that are also maintained in the TCDB
- Running expiration processing
- Confirming moves for exported stacked volumes
- Running EDGUTIL VERIFY with the TCDB and optionally the Library Manager
Using DFSMSrmm catalog processing for cataloged data sets that are cataloged only on the client system.
- Confirming the erasure or initialization of a volume
- Returning volumes to scratch status and DFSMSrmm is to perform the return to scratch cleanup actions
- Deleting volumes that contain cataloged data sets