Cancel interval control requests.

CANCEL
>>-CANCEL------------------------------------------------------->
>--+-------------------------------------------------------+---><
'-REQID(name)--+-------------------+--+---------------+-'
'-SYSID(systemname)-' '-TRANSID(name)-'
Conditions: ISCINVREQ, NOTAUTH, NOTFND, SYSIDERR
Note for dynamic transaction routing: Using CANCEL
with REQID (of a POST, DELAY, or START) could create inter-transaction affinities
that adversely affect the use of dynamic transaction routing. See the CICS® Application Programming Guide for
more information about transaction affinities.
Description
CANCEL cancels a previously issued
DELAY, POST, or START command. If you include the SYSID option, the command
is shipped to a remote system. If you omit SYSID, the TRANSID option, if present,
indicates where the command is to be executed. The effect of the cancelation
varies depending on the type of command being canceled, as follows:
- A DELAY command can be canceled only before it has expired, and only by
a task other than the task that issued the DELAY command (which is suspended
for the duration of the request). The REQID used by the suspended task must
be specified. The effect of the cancelation is the same as an early expiration
of the original DELAY. That is, the suspended task becomes dispatchable as
though the original expiration time had been reached.
- When a POST command issued by the same task is to be canceled, no REQID
need be specified. Cancelation can be requested either before or after the
original request has expired. The effect of the cancelation is as if the original
request had never been made.
- When a POST command issued by another task is to be canceled, the REQID
of that command must be specified. The effect of the cancelation is the same
as an early expiration of the original POST request. That is, the timer event
control area for the other task is posted as though the original expiration
time had been reached.
- When a START command is to be canceled, the REQID associated with the
original command must be specified. The effect of the cancelation is as if
the original command had never been issued. The cancelation is effective only
before the original command has been honored.
Note: A NOTFND response to a CANCEL command of a START with REQID
signifies that the start request is no longer outstanding. It does not imply
that the task to be started has completed by this point in time; neither
does it imply that the started task has issued a RETRIEVE command to read
the FROM data from the REQID queue. A subsequent START command reusing the
same REQID value may fail with an AEIQ abend (IOERR condition), if the REQID
queue still exists at this time.
Options
- REQID(name)
- specifies
a name (1–8 characters), which should be unique, to identify a command. This
name is used as a temporary storage identifier. The temporary storage queue
thus identified must be defined as a local queue on the CICS system where
the CANCEL command is processed.
This option cannot be used to cancel
a POST command issued by the same task (for which, the REQID option is ignored
if it is specified).
- SYSID(systemname)
- (remote
systems only) specifies the name (1–4 characters) of the system for the CANCEL
command.
- TRANSID(name)
- specifies
the symbolic identifier (1–4 characters) of a transaction to be used to determine
where the CANCEL command is to be executed, if SYSID is not specified. If
the TRANSID is defined as REMOTE, the CANCEL request is function-shipped to
the remote system.
Conditions
- ISCINVREQ
- occurs
when the remote system indicates a failure that does not correspond to a known
condition.
Default action: terminate the task abnormally.
- NOTAUTH
- occurs
when a resource security check has failed on the specified TRANSID or on the
TRANSID of the START command that corresponds to the request identification.
Default action: terminate the task abnormally.
- NOTFND
- occurs
if the request identifier specified fails to match an unexpired interval control
command.
Default action: terminate the task abnormally.
- SYSIDERR
- occurs
when the SYSID option specifies a name that is neither the local system nor
a remote system (made known to CICS by defining a CONNECTION). It also occurs
when the link to the remote system is closed.
Default action: terminate
the task abnormally.