
	Version 4.3.2	SEARCH INDEX CONTENTS \| PDF PAGE PDF BOOKS \| HOME UP PREV NEXT

— Field Reference —

Transaction Processing Monitor Fields (TP)

Field Description

CALLPGM Under CICS, this field contains the names of programs called by the CICS EXEC LINK or XCTL commands. Since Natural does not issue these calls, this field is empty under Natural. To obtain Natural program names, use the NATPROG field (see section Natural Fields (NAT)).

CQEUID

Contains the 28-byte Adabas communication user ID for the user who issued the Adabas call.

Note:
This field may contain different data when an X'48' call is issued. To avoid such a call in Natural, set Natural parameter ADAMODE=0 (the default value is 2).

ETID The Adabas ET (end transaction) ID that was established during the OP (open) call to Adabas.

SECGID Contains the security system group ID for the user who issued the Adabas call. This field is available under OS/390 or z/OS when the user is running with an external security system (RACF, ACF2, or Top Secret).

SECUID Contains the security system user ID for the user who issued the Adabas call. This field is available under OS/390 or z/OS when the user is running with an external security system (RACF, ACF2, or Top Secret).

TID The Com-plete terminal ID number of the user who issued the Adabas call.

TPTRANCT

A transaction count field. Possible values for this field are either "1" or "0" (zero).

A transaction is started with a TP terminal read and completed with a TP terminal write. For the first command of a transaction by a user, this field is set to "1". For all subsequent calls of the same transaction for the same user, this field is set to "0".

This field is most useful as a SUM field in conjunction with the field TRANSID. Used in this manner, you can determine the work rate per transaction.

TPTRANNM The transaction number as established by the user's TP system for the transaction that issued the Adabas call.

TPUSERID The user ID on the TP monitor from which the Adabas call was issued.

TRANSID The name of the root transaction or program that issued the Adabas call.

UBUID

Contains the last 8 bytes of the 28-byte Adabas communication ID (CQEUID) for the user who issued the Adabas call.

Note:
This field may contain different data when an X'48' call is issued. To avoid such a call in Natural, set Natural parameter ADAMODE=0 (the default value is 2).

UOWID Contains the instance number and the sequence number of the CICS field NETUOWID, which is 27 bytes long. This field can only be filled in by CICS. The evaluation of this field requires a large amount of CPU time and, therefore, can only be activated by a special ZAP. Following is a description of the bytes in NETUOWID:

Offset 0 (Length 1)	Length ( L ) of the Logical-Unit-of-Work-Identifier-Field, not including this field. The NETUOWID contains Logical-Unit-of-Work-Identifier-Field plus padding bytes. Values: 0 or 10 < = L < = 26
Offset 1 (Length 1)	Length of Network Name, not including this field, m = L - 9 , 1 < = m < = 17
Offset 2 (Length m)	Network name, format: ABCDEFGH.ABCDEFGH, Networkid.Luname
Offset m + 2 (Length 6)	Instance number
Offset m + 2 + 6 (Length 2)	Sequence number
Offset m + 2 + 6 + 2 (Length until 27)	Residual data

UQUID Contains the unique 4-byte UQE (user queue element) user ID for the user who issued the Adabas call. This value is allocated in numerically ascending sequence for each UQE allocated by the Adabas nucleus.

USERTYPE The type of TP system from which the Adabas call was issued. For example, if the Adabas call was issued from a CICS session, the USERTYPE field contains "CICS".

SEARCH INDEX CONTENTS | PDF PAGE PDF BOOKS | HOME UP PREV NEXT