Use the DBCTL Thread Indoubts attributes to create table views, charts, and situations that monitor indoubt threads.
IMSID The IMS Subsystem identifier. Valid format consists of up to four alphanumeric characters. Example: I61A.
MVS System The MVS System Management Facility (SMF) identifier. Valid format consists of up to four alphanumeric characters. Example: SP11.
Originating System Identifier Fully identifies the originating IMS subsystem. Valid format consists of up to 32 alphanumeric characters. Example: I91A:SP22:IMS
PSB Name Name of the PSB (program scheduling block). Valid format consists of up to eight alphanumeric characters.
Pseudo Recovery Token Pseudo recovery token used to the resolve the indoubt thread. Valid format consists of up to eight alphanumeric characters.
Recovery Token Recovery token or UOW token (in hex). The full recovery token is 16 bytes; the first 8 bytes are the CICS APPLID and the second 8 bytes are the UOW identifier. This contains the UOW portion of the full recovery token Valid format consists of up to 16 alphanumeric characters.
Region ID DBCTL region identifier (PST number). Valid format is an integer.
Sysplex Name Indicates the originating sysplex for this request. Valid format consists of up to eight alphanumeric characters.
Thread ID CCTL identifier which is the CICS applid. Valid format consists of up to eight alphanumeric characters.
Timestamp The date and time when the monitoring agent retrieved the data. This attribute is intended for logging and reporting data collection times rather than for creating situations. To specify a time of day for monitoring, use attributes from the Universal Time or Local Time groups. See the Tivoli Enterprise Portal help for instructions on specifying timestamp attributes in situations and queries.
UOR Start Time Unit of Recovery (UOR) start date and time. Valid format is string of sixteen integers.