Explanation: MAXSSMTASKS(CLEANUP(nn) | TAPEMOVEMENT(mm)) is used to define the maximum number of secondary space management tasks that can run concurrently.
| Subparameter | Explanation |
|---|---|
| CLEANUP(nn) | MAXSSMTASKS(CLEANUP(nn)) specifies the maximum number of secondary space management migration cleanup tasks that can run concurrently. For nn, substitute a decimal number from 0 to 15 for the maximum number of concurrent migration cleanup tasks. A value of 0 indicates that there are no cleanup tasks, and therefore the secondary space management window includes no cleanup processing. |
| TAPEMOVEMENT(mm) | MAXSSMTASKS(TAPEMOVEMENT(mm)) specifies the maximum number of automatic secondary space management tape migration tasks that can run concurrently. This parameter applies to the migration of data sets from level 1 volumes to level 2 tape volumes. Note that if you are duplexing migration tapes, each TAPEMOVEMENT task you define will require two tape drives. For mm, substitute a decimal number from 0 to 15 for the maximum number of concurrent tape migration tasks.A value of 0 indicates that there are no tape movement tasks, and therefore DFSMShsm performs no ML1-to-ML2 data movement. This setting is useful when no tape drives are available. |
SMS relationship: Parameter has the same meaning when applied to SMS-managed or non-SMS-managed DASD volumes or data sets.
SETSYS default: None.
DFSMShsm default: If you do not specify the CLEANUP parameter on any SETSYS command, the DFSMShsm default for nn is 2. If you do not specify the TAPEMOVEMENT parameter on any SETSYS command, the DFSMShsm default for mm is 1.