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


Example of redefining a day for automatic primary space management of SMS volumes

z/OS DFSMShsm Implementation and Customization Guide
SC23-6869-01

There are times when a user may want to modify the definition of a processing day to enable automatic processing to occur more often or less often. By changing the bytes that define the minimum amount of time between automatic processing, you can permit automatic functions to be performed at a different frequency. For example, a user may want a volume to be processed more frequently than every 14 hours. If you were causing DFSMShsm automatic primary space management to occur at the next hour, for example 10 a.m. and you wanted to process all the volumes that had not been processed in the past 30 minutes, perform the following two steps:

  1. Apply the following patch to allow automatic primary space management to process the SMS volumes that have not been processed within the last 30 minutes:
    PATCH .MCVT.+414 X'00000708' VER(.MCVT.+414 X'0000C4E0')
  2. Set the PRIMARYSPMGMTSTART time to request automatic primary space management to begin at 10 a.m. The following is an example of a PRIMARYSPMGMTSTART command with a planned start time of 10:00 and a stop time of 10:45:
    SETSYS PRIMARYSPMGMTSTART (1000 1045)

In another instance a user may want to migrate all the volumes of a large storage group, but not have enough time available in one day to process all the volumes. By processing the volumes less often, such as every other day, all the volumes can be processed once over the course of two days. To illustrate this example, assume that the user has 200 volumes to migrate and only 105 volumes can be processed per day.

  1. The user adds one day to the minimum time between processing.
         Current minimum processing interval  =  14 hours
       + Processing interval                  =  24 hours
         ________________________________________________
     
         New minimum processing interval      =  38 hours
    The hex values used to specify the minimum processing intervals for DFSMShsm automatic functions are expresses in seconds. An example of these values follows:
            X'00000708' =   1,800 seconds = 30 minutes
            X'0000C4E0' =  50,400 seconds = 14 hours
            X'00021560' = 136,800 seconds = 38 hours
    The following patch defines the minimum processing interval for space management of SMS volumes to be 38 hours:
    PATCH .MCVT.+414 X'00021560' VER(.MCVT.+414 X'0000C4E0')
  2. Day one: Volumes 1 through 105 get processed before the stop time causes migration to stop.
  3. Day two: Volumes 1 through 105 are viewed as having already been processed "today" (within the past 38 hours), so volumes 106 through 200 get processed.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014