Canceling DFSMShsm requests

DFSMShsm lets you cancel queued requests for:

An individual command
A user ID
A data set name

Rule: If you are using the common recall queue, you must submit the cancel request on the same host that originated the recall request that you want to cancel.

Use the CANCEL command to identify the commands for cancelation. The only commands that can be canceled are those commands that have not started. Identification of the commands to cancel can be specified by the DFSMShsm request number, user ID, or data set name. Use the QUERY command to find the request numbers, user IDs, or data set names. Use the QUERY ACTIVE command to determine which DFSMShsm requests are currently being processed. Use the QUERY ACTIVE(TCBADDRESS) to obtain the Task Control Block addresses of active DFSMShsm data movement tasks.

Exceptions:

Depending on whether you choose to back up data sets that are in use (see Specifying how DFSMShsm should respond to a data set in use), DFSMShsm during a BACKVOL can schedule multiple requests to retry backing up (BACKDS) data sets found to be open for update when backup was initially attempted. All requests scheduled during one BACKVOL are assigned the same request number originally assigned to the BACKVOL request itself. Canceling the request number cancels all requests. To cancel only one request, use the DATASETNAME parameter.
Data set recoveries scheduled during a volume recovery (or during APPLYINCREMENTAL processing following a volume restore) are assigned the same request number originally assigned to the volume recovery or volume restore request. Canceling that request number cancels all those requests. To cancel only one request, use the DATASETNAME parameter.

A CANCEL command with the USERID or DATASETNAME parameters cancels all existing nonexecuting requests having the specified user ID or data set name.

The following command cancels a single request:

CANCEL REQUEST(num)

If you issue the CANCEL REQUEST(num) command for an active FRRECOV DSNAME request that is processing more than one single data set, then all queued data set requests for that command fail and no additional requests are generated. All data set recovery MWEs generated by a single FRRECOV DSNAME command have the same request number. Hence, the CANCEL REQUEST(num) command cancels all queued data set recovery MWEs that originate from the same FRRECOV command.

If you issue the CANCEL REQUEST(num) command with a request number of the Fast Replication dumps, all dumps in progress are canceled, any queued DUMP MWEs fail, and no additional requests are generated. When a Fast Replication DUMP command is processed, individual volume DUMP MWEs with the same request number are generated for all volumes in each storage group defined to the copy pool.

The following command cancels the requests of a particular user:

CANCEL USERID(userid)

The following command cancels the requests for a particular data set:

CANCEL DATASETNAME(dsn)

Note:

Depending on whether you choose to back up data sets that are in use (see Specifying how DFSMShsm should respond to a data set in use), DFSMShsm during autobackup can schedule multiple requests to retry backing up (BACKDS) data sets found to be open for update when backup was initially attempted. Each request scheduled during autobackup has a request number of zero, which you cannot specify with the REQUEST parameter. You should use the DATASETNAME parameter to cancel one of these requests.
You can cancel individual data set MWEs generated from the same FRRECOV command by using the CANCEL DATASETNAME(dsn) command. You cannot use the CANCEL DATASETNAME command to cancel the main FRRECOV DSNAME MWE.

The following command cancels a particular ABARS secondary address space:

CANCEL SASINDEX(sasindex)

sasindex is an integer value between 1 and 64 received from the QUERY ACTIVE(TCBADDRESS) command. The CANCEL command may be controlled by RACF® FACILITY class.

The following command cancels a particular active task:

CANCEL TCBADDRESS(X'tcbaddress')

tcbaddress is an 8 digit value received from the QUERY ACTIVE(TCBADDRESS) command. Volume level activity generally goes to the next data set after a data set task is canceled, so to also end the volume task you should issue the appropriate HOLD command before canceling the data movement task.

'TCB' is the first tcbaddress to cancel. If the function does not end, then a 'TCB2' address is given, and the tcbaddress in 'TCB2' can then be used. If the function still does not end and a 'TCB3' address is given, then the tcbaddress in 'TCB3' can be used. If the TCB value is '****?***', then no TCB was found.

When canceling a hung journal back task, allow any active CDS backup tasks to run to completion. If a CDS backup task is also hung, cancel it before canceling the hung journal backup task. The CANCEL command may be controlled by RACF FACILITY class.

The CANCEL and QUERY commands cannot be canceled.