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


Performing inventory management

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

DFSMSrmm samples provided in SAMPLIB

  • EDGJHSKP Sample JCL for Using the EDGHSKP Utility
  • EDGJHKPA Sample IBM Tivoli Workload Scheduler for z/OS Job for Allocating the Data Sets Required for Inventory Management

DFSMSrmm provides the EDGHSKP utility to help you perform inventory management. You can run inventory management functions in a single job step or can split requests into multiple steps and jobs if required. Running inventory management as a single step allows DFSMSrmm to optimize processing. The default processing for EDGHSKP is to run all inventory management functions in sequence as described in EXEC parameters for EDGHSKP. Use this topic to set up and run inventory management activities and to schedule all DFSMSrmm utilities.

You use the EDGHSKP utility to request that DFSMSrmm perform inventory management processing. The utility validates parameters, checks that the correct files are allocated and can be used, and requests that the DFSMSrmm subsystem performs the functions you request. The utility uses the EDGBKUP utility to perform backup processing.

During DFSMSrmm subsystem inventory management processing, you can see the address space executing EDGHSKP waiting for the subsystem processing to complete. Use the RMM LISTCONTROL subcommand with the CNTL operand to see which inventory management functions are active and when the individual functions were last successfully processed. If you cancel a batch job running DFSMSrmm processing (such as EDGHSKP), the processing in the DFSMSrmm subsystem is interrupted and the function ends early.

During inventory management the DFSMSrmm subsystem issues messages that describe processing. Messages are in the MESSAGE data set. During expiration processing, DFSMSrmm identifies data sets that might be open and puts them in a list in the MESSAGE file. See Figure 1 for an example of this output.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014