z/OS DFSMSrmm Implementation and Customization Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Running DFSMSrmm utilities

z/OS DFSMSrmm Implementation and Customization Guide
SC23-6874-00

DFSMSrmm provides utilities to manage your inventory, create reports, maintain the DFSMSrmm control data set, and erase and initialize volumes. DFSMSrmm uses IKJTSOEV, if necessary, to establish a TSO environment for each of its batch utilities. See z/OS TSO/E Programming Services for additional information about IKJTSOEV.

All data sets used by DFSMSrmm can be eligible for allocation in the extended addressing space of an EAV. This includes the DFSMSrmm journal and any dynamically allocated temporary files.

Temporary sort files created by DFSMSrmm for use by DFSORT are always large format EAS-eligible data sets when inventory management or EDGUTIL are used. EAS-eligible data sets can be placed in an extended addressing space (EAS) on an extended address volume (EAV). See z/OS DFSMS Using the New Functions for more information on EAS and EAV. DFSMSrmm specifies EATTR=OPT on the dynamic allocation that creates the temporary data set.

All DFSMSrmm utilities and programs support NON_VSAM_XTIOT=YES options in the DEVSUPxx parmlib member.

For the correct and full functioning of DFSMSrmm, DFSORT must be installed. If you have another sort product instead of DFSORT, you need equivalent sort product capability to support large format sequential input and output data sets.

If you do not have DFSORT installed and either EDGUTIL or inventory management fails with ABEND 213-14, pre-allocate the temporary data sets as non-large format data sets:
  • For EDGUTIL, the DD name is VCINOUT and must be included in the EDGUTIL JCL.
  • For EDGHSKP (inventory management), the DD names are SRTINOUT, DATUPD, VOLCON, VOLSET, and CONSET and must be included in the started procedure JCL, usually called DFRMM.
  • Example JCL is:
    //SRTINOUT DD DISP=(,DELETE),
    //         SPACE=(472,(pp,ss)),AVGREC=U,
    //         BLKSIZE=0,LRECL=472,
    //         RECFM=FB,UNIT=(SYSALLDA,v),DSORG=PS
    • The LRECL in this example is approximate and will be overridden by DFSMSrmm at run time.
    • pp - primary space. This is usually half the number of the data set records (TCDB volume records for EDGUTIL). See messages EDG2223E and EDG6840E for an explanation.
    • ss - same as pp.
    • v - volume count. Usually 1 is enough.
Use the EDGHSKP utility to run inventory management activities.
  • For volumes managed by the VRSEL retention method, vital record processing determines which data sets to retain and what volume moves are required based on the retention and movement policies you define to DFSMSrmm.

    DFSMSrmm supports trial run and production run vital record processing. Trial run vital record processing does not change data set and volume information in the DFSMSrmm control data set. Use trial run vital record processing to analyze the effect that your movement and retention policies will have. Based on your analysis, you can then determine if you need to change vital record specifications before performing production run vital record processing. This is helpful when you are defining your initial set of policies and when you need to make changes as you gain more experience with DFSMSrmm.

  • Expiration processing identifies volumes ready to be released and returned to scratch.
  • Storage location management processing assigns shelf locations to volumes being moved to storage locations.
  • DFSMSrmm control data set functions back up the control data set and the journal, reset the journal data set when the control data set and journal are backed up, and create an extract data set.

Use the EDGAUD and EDGRPTD utilities and the EDGRRPTE exec to get information about your removable media library and storage locations. You can also get security trail information about volumes and data sets defined to DFSMSrmm and audit trail information about volumes, shelf assignments, and user activity.

Use the EDGUTIL utility to create, update, mend, and verify the control data set.

Use the EDGBKUP utility to back up and recover the control data set and journal.

Use DFSMSrmm backup utilities instead of other backup utilities, such as access method services EXPORT, because DFSMSrmm provides the necessary serialization and forward recovery functions using the journal data sets. DFSMSrmm backup utilities check whether the control data set is in use and tell the DFSMSrmm subsystem that backup or recovery is in process.

Use the EDGINERS utility to erase and initialize tape volumes either automatically or manually and to scan tape labels manually. You can use EDGINERS instead of the DFSMSdfp utility IEHINITT. See Replacing IEHINITT with EDGINERS for details on the differences between the utilities and for information on controlling the use of IEHINITT.

You can schedule these utilities to run at the time and frequency that are best for your installation. Use a scheduling system such as IBM Tivoli® Workload Scheduler for z/OS for this purpose.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014