Task management

When performing DFSMSrmm task management, you can use the:

QUERY ACTIVE operator command from an operator console at any time to display the status of DFSMSrmm, its local tasks, and request queues.
TSO subcommand RMM LISTCONTROL STATUS from TSO or with any of the DFSMSrmm APIs when DFSMSrmm is active and able to process subsystem requests.
CONTROL STATUS ISPF dialog (fast path command, Selection 4.8.12, or Selection 5.7.12 from a TSO ISPF session to interactively display status and manage active tasks when DFSMSrmm is active and able to process subsystem requests

Any task in the system that requests DFSMSrmm subsystem services and fails, or is interrupted because a TSO-user used Attention (ATTN), or is cancelled by the operator, results in any corresponding long-running subsystem request failing. In addition, there are checkpoints built into long-running requests so that when the requestor ends (such as a job being cancelled), DFSMSrmm processing is interrupted at a safe and convenient point. Long running local tasks are DFSMSrmm subsystem requests that last long enough for a task token to be obtained and used.

If the requester is inventory management, the results of the partial processing are available in the MESSAGE file. Long running tasks that support interruption are:

EDGHSKP inventory management, VRSEL, DSTORE, EXPROC, RPTEXT, and CATSYNCH.
Note: EDGHSKP ends with return code 12 when cancelled.
SEARCH xx subcommands.
Note: These end with return code 4, reason code 16 when cancelled.
EDGINERS when building lists of volumes to process.
Note: EDGINERS processing is still attempted even though one or more search requests of the DFSMSrmm control data set may have been cancelled by the operator. Also, cancelling a task that is processing on behalf of EDGINERS does not cause EDGINERS to be cancelled. To cancel EDGINERS processing, you have to cancel the batch job.
ADD xx and DELETE xx subcommands with COUNT specified.
Note: These end with return code 4, reason code 12 when cancelled.

All these long running tasks run within the DFRMM address space and have checkpoints in their processing that determine whether they should be held, released, or ended. These checkpoints include those that relate directly to the use of the MAXHOLD parmlib option. For example, each time that the MAXHOLD value determines that control data set serialization given up and re-established, there is a time period during which HOLD and CANCEL are effective.

Task management applies only to local tasks. This includes all processing on a standard system, local tasks only on a server system, and all local tasks on a client system. To hold or interrupt a task on a server that is a server task, you have to go to the client system and issue the command there. The QUERY ACTIVE operator command, LISTCONTROL STATUS subcommand, and CONTROL STATUS dialog all help you determine the client that originated a request, and therefore, on which client system any task management commands should be entered. For example, see Figure 1 for the results from a QUERY ACTIVE command (the output of the LISTCONTROL STATUS subcommand or CONTROL STATUS dialog would be very similar).

Figure 1. Output from QUERY ACTIVE command

EDG1119I DFSMSrmm STATUS IS ACTIVE. JOURNAL DISABLED.   LISTENER ACTIVE.
EDG1120I Function  System  Task   Name  Started   Token  S IP Status
EDG1113I HSKP     EZU161  JOB=RMMUSERK 04:53:28 00C00001 Re<04:53:35
EDG1114I LOCAL TASKS  10, ACTIVE   0, SERVER TASKS  10, ACTIVE   1
EDG1122I                  HELD     0                    HELD     0
EDG1118I      0 QUEUED REQUESTS, INCLUDING      0 NOWAIT      0 CATALOG
EDG1121I DEBUG: DISABLED, PDA TRACE LEVEL: 1-2-3-4- RESERVE: 04:54:11
EDG1101I DFSMSrmm MODIFY COMMAND ACCEPTED

In Figure 1, the HSKP task is a request running on behalf of system EZU161. To HOLD the task, enter this operator command on the system EZU161 operator console:

F DFRMM,HOLD(HSKP)

You can use a token instead of the HSKP value. You might need to do this if there are multiple HSKP tasks, and you want to be sure to affect the correct task. You also need to use a token for tasks other than HSKP. To use a token, first issue the Q A command on the EZU161 system. Take note of the token for the task to be affected and then use the token with the operator command on the client system.