IBM CICS Transaction Server for OS/390 SC33-1686-02 - Manual (Page 190)

CEMT SET DB2ENTRY
──CEMT Set DB2Entry─ ─ ─┬ ┬ ───────────── ────────
└ ┘ ─ ─(data-area)
┌ ┐ ── ───────────────────────────
─ ─ ── ┴ ┬ ┬ ───────────────────────── ─
├ ┤ ─ ─┬ ┬ ─ ─ACCOUNTREC(cvda) ───
│ │ ├ ┤ ─UOW──────────────
│ │ ├ ┤ ─TASK─────────────
│ │ ├ ┤ ─TXID─────────────
│ │ └ ┘ ─NONE─────────────
├ ┤ ─ ─AUTHID(data-area) ──────
├ ┤ ─ ─┬ ┬ ─ ─AUTHTYPE(cvda) ─────
│ │ ├ ┤ ─GROUP──────────
│ │ ├ ┤ ─SIGN───────────
│ │ ├ ┤ ─TERM───────────
│ │ ├ ┤ ─TX─────────────
│ │ ├ ┤ ─OPID───────────
│ │ └ ┘ ─USERID─────────
├ ┤ ─ ─┬ ┬ ─ ─DISABLEDACT(cvda) ──
│ │ ├ ┤ ─ABEND─────────────
│ │ ├ ┤ ─SQLCODE───────────
│ │ └ ┘ ─POOL──────────────
├ ┤ ─ ─┬ ┬ ─ ─ENABLESTATUS(cvda) ─
│ │ ├ ┤ ─ENABLED────────────
│ │ ├ ┤ ─DISABLED───────────
│ │ └ ┘ ─FORCEDISABLED──────
├ ┤ ─ ─PLAN(data-area) ────────
├ ┤ ─ ─PLANEXITNAME(data-area)
├ ┤ ─ ─┬ ┬ ─ ─PRIORITY(cvda) ─────
│ │ ├ ┤ ─HIGH───────────
│ │ ├ ┤ ─EQUAL──────────
│ │ └ ┘ ─LOW────────────
├ ┤ ─ ─PROTECTNUM(data-area) ──
├ ┤ ─ ─THREADLIMIT(data-area) ─
└ ┘ ─ ─┬ ┬ ─ ─THREADWAIT(cvda) ───
├ ┤ ─TWAIT────────────
├ ┤ ─NOTWAIT──────────
└ ┘ ─TPOOL────────────
Options
ACcountrec
specifies the minimum amount of DB2 accounting
required for transactions using this DB2ENTRY. The
specified minimum may be exceeded, as described in
the following options. CVDA values are:
UOW
The CICS DB2 attachment facility causes an
accounting record to be produced for each UOW,
assuming that the thread is released at the end of
the UOW.
TASK
The CICS DB2 attachment facility causes a
minimum of one accounting record to be produced
for each CICS task.
A transaction containing multiple UOWs may use
a different thread for each of its UOWs (assuming
the thread is released at syncpoint). The result
may be an accounting record produced for each
UOW.
TXID
The CICS DB2 attachment facility produces at
least one accounting record to be produced when
the transid using the thread changes.
This option applies to DB2ENTRYs that are used
by more than one transaction ID. As threads are
typically released st syncpoint, a transaction
containing multiple UOWs may use a different
thread for each UOW. The result may be that an
accounting record is produced per UOW.
NONE
No accounting records are required for
transactions using threads from this DB2ENTRY.
DB2 does, however, produce at least one
accounting record for each thread when the thread
is terminated. Additionally, authorization changes
cause accounting records to be produced.
AUTHID
specifies the id to be used for security checking when
using this DB2ENTRY. If AUTHId is specified,
AUTHTYpe may not be specified.
AUTHTYPE
returns the type of id that can be used for security
checking when using this DB2ENTRY. If AUTHTYpe is
specified, AUTHid may not be specified. CVDA values
are:
GROUP
Specifies the 8-character USERID and the
connected group name as the authorization ID.
The following table shows how these two values
are interpreted by DB2.
To use the GROUP option the CICS system must
have RACF external security SEC=YES specified
in the CICS system initialization table (SIT).
If no RACF group ID is available for this USERID,
an 8-character field of blanks is passed to DB2 as
the group ID.
SIGN
Specifies the SIGNID parameter of the DB2CONN
should be used as the resource authorization ID.
IDs passed to DB2 How DB2 interprets values
CICS sign-on user ID
(USERID) Represents the primary DB2
authorization ID.
RACF-connected
group name If the RACF list of group options
is not active, DB2 uses the
connected group name supplied
by the CICS attachment facility
as the secondary DB2
authorization ID. If the RACF list
of group options is active, DB2
ignores the connected group
name supplied by the CICS
attachment facility, but the value
appears in the DB2 list of
secondary DB2 authorization
IDs.
172 CICS Supplied Transactions