356 Converting to DFSMSrmm from ASG-ZARA or AutoMedia
8.7.2 Other tape libraries
Whatever tape library is installed in your system, DFSMSrmm can support it
through a user interface that tells the library which volumes to return to scratch
status and which volumes must be ejected and moved to another storage
With DFSMSrmm's reporting and command capabilities it is simple to build this
interface, using REXX, DFSORT, DFSMSrmm utilities, and TSO RMM
You must analyze what the vendor tape library requires as input for retention and
movement processing and then customize DFSMSrmm to provide the library
with the correct input.
Be sure to keep the vendor tape library catalog and the DFSMSrmm database
synchronized to avoid any mismatch that would cause rejection of tape mounts.
STK tape libraries
Below we provide you with a simple interface example between an STK Silo tape
library and DFSMSrmm to eject tapes that need to be moved to another location.
After running DFSMSrmm inventory management (storage location management
processing DSTORE), you can create a list of all volumes that are moving by
using DFSMSrmm commands. Follow these steps:
1. Use DFSMSrmm commands as shown in Example 8-3.
Example 8-3 RMM SEARCHVOLUME subcommands with specific destinations
RMM SV VOLUME(*) DESTINATION(LOCAL) CLIST(' ',' -')
RMM SV VOLUME(*) DESTINATION(REMOTE) CLIST(' ',' -')
RMM SV VOLUME(*) DESTINATION(DISTANT) CLIST(' ',' -')
RMM SV VOLUME(*) DESTINATION(my_loc) CLIST(' ',' -')
The resulting list, which is stored in the RMMCLIST data set, or the data set
prefix.EXEC.RMM.CLIST consists of VOLSERs only. The data set uses blocked,
Note: Unless you exploit the capability of APAR OW30790, and use a
pre-allocated RMMCLIST DD name, you can use only one TSO RMM
subcommand at a time, because each call to the CLIST option will
overwrite the data created before.