Topics Map > University of Chicago > IT Services > Business Systems > Mainframe
Mainframe - Removable Media Manager (RMM)
This article provides an overview of the Removable Media Manager (RMM) for Mainframe Systems.
During System Test Time on Sunday, December 7, 1997, we converted our 3480-cartridge Tape Library management system from CA1 to IBM’s RMM (Removable Media Manager). A Mainframe - Removable Media Manager (RMM) Manual is available. RMM message definitions are available in QuickRef (QW at ISPF Command Lines).
RMM’s ISPF User Interface Panels will look different from CA1’s but will offer the same functions. Examples are available.
In order to access the User Interface Panels via ISPF L.RMM, a User’s 7-character LogonID must be defined to RMM. This can be achieved in several ways:
- All Users who currently have cartridges under CA1 control will be defined to RMM during our conversion process.
- New Users will be automatically defined to RMM when requesting their first cartridge mount or when first asccessing RMM ISPF panels.
RMM’s ISPF User panels have full HELP capability.
Conventions for controlling Retention Periods and Expiration dates in JCL DD statements will not change in RMM.
To retain a volume until a certain date, code EXPDT=yyyy/ddd (which is Year2000 compliant). A code of EXPDT=yyddd (standard Julian Date) is also acceptable.
To retain a volume permanently, code EXPDT=99365 (or EXPDT=99366).
To retain a volume for a certain period of days, code RETPD=dddd; (e.g., to retain a volume for three weeks, code RETPD=21). The default retention period at UC is 14 days unless a different value is specified. Coding RETPD=0 is valid and will allow the use of a volume for the duration of a job without the volume being assigned to the user.
To request that sensitive data be erased from a volume under catalog control before it is returned to Scratch status, code EXPDT=97000 in the DD statement creating the dataset. Requests to Erase sensitive data can also be made via the Update panels in ISPF. Erase requests cannot be combined with other Retention and Expiration options in JCL under RMM as was the case under CA1. RMM also assigns a default Retention Period of 14 days: If a dataset is uncataloged before the 14 days are up, RMM will extend retention of the volume to complete the 14 day default before requesting erasure; should the 14 default days have already passed, RMM will request erasure on the next day. NOTE that this is different from the CA1 routine of always extending Volume retention for two days past uncataloging.
To retain a volume for as long as its associated dataset is cataloged, code EXPDT=99000. Uncataloging the dataset will release the volume from RMM Control and return it to Scratch status. However, RMM also assigns a default Retention Period of 14 days: If a dataset is uncataloged before the 14 days are up, RMM will extend retention of the volume to complete the 14 day default; should the 14 default days have already passed, RMM will move the volume to scratch status on the next day. NOTE that this is different from the CA1 routine of always extending Volume retention for two days past uncataloging.
To identify a volume being mounted as one not under RMM control or protection, code EXPDT=98000 in the DD statement for that volume.
Questions about RMM may be directed to firstname.lastname@example.org.