Chapter 4. DFSMSrmm ACS support 165
Use the commands as shown in Figure 4-24 to define all new data set vital
record specifications used in the sample ACS management class routine.
Figure 4-24 Define new data set name vital record specifications
4.1.6 Migration considerations
If you are already using DFSMSrmm, use this new function to migrate your
EDGUX100 managment value and volume pool selection functions to the
DFSMSrmm SMS ACS support as described previously.
Move pooling decisions out of EDGUX100 user exit
You can implement DFSMSrmm scratch pooling using ACS routines based on
storage group names. DFSMSrmm provides support for non-system-managed
tape and for system-managed manual tape libraries. This support enables
pooling at the individual volume level. You assign a storage group name to each
volume by:
Using DFSMSrmm TSO subcommands
Using pool information that you define with the DFSMSrmm EDGRMMxx
PARMLIB VLPOOL command
/* define VRSs for special meaning expdt processing 98001 to 98365 */
RMM ADDVRS DATASETNAME(’M98001’) COUNT(1) LASTREFERENCEDAYS
RMM ADDVRS DATASETNAME(’M98002’) COUNT(2) LASTREFERENCEDAYS
RMM ADDVRS DATASETNAME(’M98003’) COUNT(2) LASTREFERENCEDAYS
/* define VRSs for special meaning expdt processing 90000 and 99000 */
RMM ADDVRS DATASETNAME(’M99000’) CYCLES COUNT(99999) WHILECATALOGED
/* define VRSs for special meaning expdt processing 99001 to 99364 */
RMM ADDVRS DATASETNAME(’M99001’) COUNT(1) CYCLES
RMM ADDVRS DATASETNAME(’M99002’) COUNT(2) CYCLES
RMM ADDVRS DATASETNAME(’M99003’) COUNT(3) CYCLES
RMM ADDVRS DATASETNAME(’M99004’) COUNT(4) CYCLES
/* define VRSs for all other used management classes */
RMM ADDVRS DATASETNAME(’MCDB20’) COUNT(20) BYDAYCYCLES WHILECATALOG -
UNTILEXPIRED SCRATCHIMMEDIATE NEXTVRS(SAVE)
RMM ADDVRS NAME(SAVE) LOCATION(SAVE) COUNT(5)
RMM ADDVRS DATASETNAME(’MCDB21’) COUNT(21) CYCLES WHILECATALOG -
UNTILEXPIRED SCRATCHIMMEDIATE NEXTVRS(EXTRA)
RMM ADDVRS NAME(EXTRA) LOCATION(CURRENT) EXTRADAYS(2)
Note: You can use all available ADDVRS operands to specify your vital record
specification to match SMS managment classes.
166 Converting to DFSMSrmm from ASG-ZARA or AutoMedia
You use the ACS routines to process the special calls that DFSMSrmm makes to
the SMS subsystem for ACS processing. DFSMSrmm requests that the
management class and storage group routines are run.
Move VRS management decisions out of EDGUX100 user exit
You use the ACS routines to process the special calls that DFSMSrmm makes to
the SMS subsystem for ACS processing. In replacement of the EDGUX100 user
exit VRS management value, DFSMSrmm requests that the management class
routine is run.
For each new tape data set, DFSMSrmm processing follows the steps described
here depending on the circumstances (see Figure 4-25):
Pre-ACS processing (see “Pre-ACS support as a way to migrate” on
page 167 for details):
IGDACSXT exit is called, you can implement this exit to set values to
&MSPOLICY, &MSDEST, &MSPOOL, and &MSPARM ACS read-only
variables before ACS routines are called. Then your ACS routines can
refer to these variables.
DFSMSrmm calls EDGUX100 installation exit to enable a VRS
management value to be returned. The selected value is returned in the
&MSPOLICY variable.
OPEN processing after a device has been allocated:
DFSMSrmm calls SMS ACS processing to proceed the management
class ACS routine passing environment information.
If a management class is not returned from ACS processing, DFSMSrmm
calls the EDGUX100 installation exit to enable a VRS management value
to be returned.
The specified management class or VRS management value is recorded
by DFSMSrmm at the data set level.
Attention: The environment variable &ACSENVIR is set to RMMVRS
so that you can differentiate allocation requests for system managed
data sets from requests by DFSMSrmm for a management class name.
Chapter 4. DFSMSrmm ACS support 167
Figure 4-25 DFSMSrmm V2R10 SMS ACS VRS policy management support
Pre-ACS support as a way to migrate
Using the SMS pre-ACS calls to DFSMSrmm, you can use any existing
DFSMSrmm and EDGUX100 exit scratch pool and EDGUX100 exit policy
assignment decisions as input to your SMS ACS logic. This will enable you to
direct new data set allocations to the correct media. You can use SMS ACS to
decide if data sets are to be system-managed or non-system-managed. For
system-managed tape data sets, you can decide to which library or library type
you would like the allocation directed. This can help you with VTS
implementation.
You can use the pre-ACS interface to provide additional information like vault
destination or pool information to the ACS routines. You can use the EDGUX100
installation exit for pre-ACS processing. When called during pre-ACS processing,
values selected by the exit are used as input to the ACS routine.
DFSMSrmm always attempts to pass values for the &MSPOOL and
&MSPOLICY ACS read-only variables. If you do not use an EDGUX100 exit, the
&MSPOOL variable is set to the DFSMSrmm system-based scratch pool
DFSMSrmm
(at OCEOV)
New Allocation
if not set
(&ACSENVIR=
RMMPOOL)
EDGUX100
MC ACS
VRS policy
management
SC ACS
DC ACS
SC=NULL
?
IGDRMM00 EDGUX100
pre-ACS Processing
DFSMSrmm SMS ACS Processing
y
IGDACSXT
&MSPOLICY
&MSPOOL
&MSDEST
&MSPARM
DFSMSrmm
PARMLIB OPTIONS
VLPOOL
SMS
Managed
Tape
n

Get Converting to DFSMSrmm from ASG-ZARA or AutoMedia now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.