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


Implementing installation defined storage locations

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

You might implement installation defined storage locations for these reasons:
  • To choose the storage location names you want
  • To change the dominance priority of the locations for inventory management vital record processing for use when moves conflict
  • To separate volumes by shape when sending them to storage locations
  • To use storage locations without shelf management
  • To use more than 3 storage locations
  • To use storage locations that are not applicable for automated movement .

To implement installation defined storage locations, follow these steps:

  1. Identify:
    1. The number of storage locations you require. DFSMSrmm provides you with three built-in storage locations. If you use more than three storage locations, use the LOCDEF parmlib command to define additional storage locations. You can identify any location as an installation defined storage location except the locations ALL, HOME, and CURRENT, which are DFSMSrmm reserved location names.
    2. The location names you will use.
    3. The priority you want to use for each location. Priority is used to resolve movement conflicts that occur when more than one policy applies to a volume or when multiple logical volumes reside on a stacked volume. The relative priority of the locations is used to determine where a volume is sent. Include the location name SHELF and any system-managed libraries to develop your location priority.
    4. The media names you will use in your installation. If you have different media shapes in your installation, you can set movement policies based on the different shapes. For example, you might have separate shelving for tape reels, cartridge tape, and optical media due to differences in their shape.
    5. If you require storage locations without shelf management.
    6. If no movement will be initiated by DSTORE processing .
  2. Define LOCDEF parameters in parmlib. See Defining storage locations: LOCDEF.
  3. Restart or refresh the DFSMSrmm procedure to use the updated parmlib member.
  4. Define the bin numbers for the shelf-managed storage locations using the RMM ADDBIN subcommand. See z/OS DFSMSrmm Managing and Using Removable Media for information.

    When the new location and bin numbers are defined, they are available for assignment to volumes moving to the storage location. In order for DFSMSrmm to use the new storage locations and bin numbers for storage management, you must continue with step 5. Inventory management sequentially assigns the bin numbers to moving volumes. If you do not define vital record specifications and run inventory management, the locations and bin numbers can only be assigned manually by using the RMM CHANGEVOLUME subcommand.

  5. Create new vital record specifications or update existing vital record specifications specifying the location names you defined using LOCDEF.
  6. Run inventory management vital record processing to produce a Vital Records Retention Report. Check the report to ensure that the correct destination is selected for each data set and volume retained by a vital record specification. You might find it helpful to do a trial run of VRSEL with an ACTIVITY file and then run EDGJACTP to review just the changes in retention as a result of the new and changed VRSes.
  7. If you plan to export logical volumes, run export processing before running DFSMSrmm storage location management. See Managing stacked volumes for information on running export processing.
  8. Once the retention report is correct, run inventory management storage location management and report extract processing to assign destinations and bin numbers and to prepare an extract data set which you use as input to EDGRPTD.
  9. Run EDGRPTD to produce the movement and inventory reports for use to pull and ship the volumes to the correct locations.
  10. Once volumes have been moved, use the RMM CHANGEVOLUME subcommand to confirm volume movement.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014