Ts commands, Load hold/release, Retrieve wait/start – IBM Transaction Server OS User Manual
Page 82
TS commands
v
The affinity here is between all transactions that use the same TS queue. It
applies to both MAIN and AUXILIARY TS. The match is made on the name of
the TS queue.
v
The affinity relation can be GLOBAL, BAPPL, LUNAME, or USERID.
v
Lifetime can be PCONV, LOGON, SIGNON, ACTIVITY, PROCESS,SYSTEM, and
PERMANENT. A MAIN queue cannot be recovered, regardless of definition, so
cannot cause PERMANENT.
v
No data is collected if a TS queue is defined as remote or if a remote SYSID is
specified on the TS command. In such cases, the request is satisfied by a
remote CICS region or by a temporary storage pool in the coupling facility.
v
Commands in error are treated in the same way as commands that give a
NORMAL response, so data is collected.
v
If a TS queue is created and deleted within the same task, no data is collected.
Scanner differences: Scanner detects all instances of TS commands.
LOAD HOLD/RELEASE
v
The affinity here is between all transactions that LOAD HOLD and RELEASE the
same program (or, more probably, table). The match is made on the program
name.
v
The LOAD and RELEASE protocol applies only to programs that are defined with
RELOAD(NO). If the Detector can not establish the RELOAD attribute for some
reason, RELOAD(NO) is assumed.
v
Once a LOAD HOLD has occurred for a program, any subsequent LOAD (with or
without HOLD) or RELEASE is part of the affinity.
v
The affinity relation is GLOBAL or BAPPL.
v
Lifetime is always SYSTEM.
v
Commands in error are treated in the same way as commands that give a
NORMAL response, so data is collected.
v
LOAD with no HOLD for programs defined as RESIDENT is not treated as an
affinity because relying on residency for sharing is inherently unsafe, the program
can be replaced by SET PROG() NEWCOPY.
v
The incorrect use of RELEASE for a program defined with RELOAD(YES) is not
detected.
Scanner differences: Scanner detects all instances of LOAD, not just LOAD HOLD,
and all instances of RELEASE.
RETRIEVE WAIT/START
v
The affinity here is between all the transactions that issue START commands for
a particular transaction at a terminal, where that transaction issues RETRIEVE
WAIT. The transaction that issues the RETRIEVE WAIT is also part of the affinity.
The match is made on the transid.
v
The affinity relation can be GLOBAL or USERID.
v
Lifetime can be SYSTEM or PERMANENT. PERMANENT is assumed if
PROTECT is specified on any START.
66
CICS Transaction Affinities Utility Guide
|
|
|