- The affinity here is between the transaction that issues the DELAY,
POST or START command and the transaction that issues the CANCEL command
via REQID. The match is on REQID.
- In order for another task to CANCEL a DELAY, REQID must be explicitly
specified on the DELAY command. If no REQID is specified on a DELAY
command, it cannot be canceled, and therefore cannot be detected.
In order for another task to CANCEL a START or POST, it is not necessary
to specify REQID on the command because CICS® supplies
a unique REQID that may be used (unless START specifies NOCHECK).
So only START commands that do not both specify NOCHECK and omit REQID,
and all POST commands, are detected.
- Further, data is not collected for commands that expire on entry
to Interval Control, because they cannot be canceled (because an element
control interval (ICE) is not created). DELAY and POST commands get
an EXPIRED response. For START commands there is no such response;
so 'expired on entry' is deduced if INTERVAL(0) was specified.
This detects most 'expired on entry' STARTs, but not all.
- START, DELAY, and POST commands in error are ignored, so no data
is collected.
- CANCEL commands that omit REQID are ignored because they cannot
cancel another task. CANCEL commands that return a NOTFND response
are also ignored because the ICE must have expired and the CANCEL
must have failed. No data is collected for these.
- REQIDs are assumed to be unique; that is, there are no simultaneous
pairs of START/CANCEL using the same REQID. Having such a pair violates CICS programming guidelines, and
the results from CICS are unpredictable.
The affinity relation for START might be GLOBAL,
BAPPL, LUNAME, or USERID. The lifetime for START might be PCONV, LOGON,
SIGNON, ACTIVITY, PROCESS, SYSTEM, or PERMANENT. If the PROTECT option
is specified on the START, the lifetime is SYSTEM or PERMANENT. However,
the Detector always worsens LOGON and SIGNON to SYSTEM or PERMANENT,
because of limitations in the way that this affinity is detected. 
The affinity relation for DELAY and POST might
be GLOBAL, BAPPL, LUNAME, or USERID. The Lifetime might be only SYSTEM,
PROCESS, ACTIVITY, or PCONV. If the affinity relation is LUNAME or
USERID, the lifetime must be PCONV because neither DELAY nor POST
exist beyond task termination. 
- If the transaction specified on a START or CANCEL command is defined
as remote, or a remote SYSID was specified on the command so that
the command is function shipped to a remote CICS region, no data is collected. (It is not
possible to function ship POST or DELAY commands.)
- A CANCEL affinity is considered to be initiated from a terminal
if the START, DELAY or POST is initiated from a terminal. Whether
the CANCEL was so initiated or not is irrelevant.
Scanner differences: Scanner detects all instances of POST,
all instances of DELAY REQID, all instances of CANCEL REQID, and all
instances of START that either omit NOCHECK or specify REQID or specify
TERMID (because of RETRIEVE WAIT affinity).