Trace information for data table services

The trace table produced by CICS® helps you determine the cause of a problem. It shows the flow of control through the CICS modules. This section describes the entries included in the trace table by data table services. For information on the contents of the trace table and how to obtain it, see CICS Diagnosis Reference.

There are two types of trace points:

Both of these types are listed separately below.

Entry and exit trace points

The following entry and exit trace points are provided by SDT:

0B13
Entry to Remote Read service
0B14
Exit from Remote Read service
0B1B
Entry to Initialize Data Table Support service
0B1C
Exit from Initialize Data Table Support service
0B1D
Entry to Logon service
0B1E
Exit from Logon service
0B1F
Entry to Load service
0B20
Exit from Load service
0B21
Entry to Open, Close, Set Enablement and Statistics services
0B22
Exit from Open, Close, Set Enablement and Statistics services
0B23
Entry to local read services
0B24
Exit from local read services
0B25
Entry to update (add record, add, replace, delete) services
0B26
Exit from update services
0B2D
Entry to Connect and Disconnect services
0B2E
Exit from Connect and Disconnect services

The format of each of these trace points is described in CICS Diagnosis Reference.

Function and qualifier flags

Each entry and exit trace point contains a function field, and most of them contain a qualifier flags field. The function field is a byte that identifies the function that was being performed; the qualifier flags field is a byte that contains flags that qualify some of the functions. The values of these fields are:

Table 7. Function and qualifier flags and values
Function Qualifier flags
X'00' Initialize
X'00' as shared data table server
X'80' as shared data table requester
X'02' Add entry from source
X'00' add issued as a result of a data
set to table read request
X'40' add issued by load transaction
X'03' Write entry to table
X'00' completed write
X'80' pre-write for CMT
X'04' Rewrite entry in table
X'00' completed rewrite
X'80' pre-rewrite for CMT
X'05' Delete entry in table
X'00' completed delete
X'80' pre-delete for CMT
X'06' Commit user-maintained data table updates made by this unit of work
X'07' Roll back user-maintained data table updates made by this unit of work
X'08' Load data table (on exit trace only)
X'00' load OK
X'80' source file is empty
X'09' Point at a record
X'80' equal match
X'40' greater than match
X'20' less than match
(the above can be in various
combinations)
X'10' test if data table is enabled
X'0A' Retrieve record by key
X'80' equal match
X'40' greater than match
X'20' less than match
(the above can be in various
combinations)
X'10' test if data table is enabled
X'0B' Retrieve record by token
X'80' equal match (internal fastpath for a
sequence of records)
X'40' greater than match
X'20' less than match
(the above can be in various
combinations)
X'10' test if data table is enabled
X'0C' Logon as a server
X'0E' Open a data table
X'0F' Close a data table
X'10' Collect statistics
X'11' Set enablement state
X'00' enable data table
X'80' disable data table
X'40' force disablement (always
combined with disable)
X'15' Connect to a shared data table
X'16' Break connection to a shared data table
X'17' Process the completion of loading

Response codes

Each exit trace point contains a two-byte response-code and reason-code field. The first byte is the response code, for which the possible values are:

X'01'
Successful
X'02'
Exception
X'03'
Disaster
X'04'
Invalid
X'06'
Purged

Reason codes

Each exit trace point contains a two-byte response-code and reason-code field. The second byte is the reason code, for which the possible values are:

X'01'
Record not in data table
X'02'
Duplicate (record already in data table)
X'03'
Data table full (already contains the maximum number of records)
X'04'
Record rejected by user exit
X'05'
Failed to get storage3
X'06'
Record not in data table (and table is known to be complete)
X'07'
Data table service failed3
X'08'
Not authorized to connect to file3
X'09'
Resource is not a data table
X'0A'
Remote system has not logged on as a server
X'0B'
Load request failed3
X'0C'
Data table is disabled
X'0D'
Add request (from DASD) deliberately not processed
X'0E'
Record too long
X'0F'
Data table token invalid
X'10'
Record not in data table (but might be in source data set)
X'11'
Data table not closed as other files are still using it
X'12'
Reserved
X'13'
Record is in data table but not currently valid
X'14'
File cannot be closed as it is disabled
X'15'
Protocol error3
X'16'
CICS is not an MVS™ subsystem
X'17'
Not authorized to connect to this file3
X'18'
CICS cannot use cross-memory services
X'19'
Interface parameter block format not recognized

UMT and other flags

This flag byte is included in the entry trace point on OPEN. The significant bits at open time are:

B'1.......'
CICS-maintained data table
B'01......'
Recoverable user-maintained data table
B'00......'
Nonrecoverable user-maintained data table

Exception trace points

The following exception trace points are provided by SDT:

AP 0B0A
Unrecognized function on call to DFHDTRE
AP 0B0B
Unrecognized function on call to DFHDTRR
AP 0B0C
Unrecognized function on call to DFHDTUP
AP 0B0D
Unrecognized function on call to DFHDTST
AP 0B0E
Unrecognized function on call to DFHDTSS
AP 0B0F
Unrecognized function on call to DFHDTRC
AP 0B10
Error on initializing record management
AP 0B11
Error on record manager OPEN
AP 0B12
Error on record manager CLOSE
AP 0B15
Unexpected error on call to retrieval PC
AP 0B19
Error calling data tables SVC when initializing as server
AP 0B1A
Error calling data tables SVC when initializing as requestor
AP 0B27
CLOSE could not find table block
AP 0B28
CLOSE could not find file block
AP 0B29
Error calling data tables SVC when logging on as server
AP 0B2A
Error calling data tables SVC when connecting or disconnecting
AP 0B2B
XDTRD exit returned invalid record length (that is, it changed the length for a CMT, or increased the length for a UMT)
AP 0B2C
Connect index exceeds maximum supported size
AP 0B2F
Disastrous error when acquiring storage to pass parameters to loading transaction

The format of each of these trace points is described in CICS Diagnosis Reference. The following two sections contain guidance on interpreting some of the information that is traced.

Related concepts
Problem determination for data tables
Analyzing errors from the data tables SVC
Analyzing errors from data tables cross-memory services
Dump information for data tables

3.
This reason code might have accompanying error code information. The error code is a four-byte field that is also reported in either an error message or an exception trace point. The possible values are described in CICS Messages and Codes, Analyzing errors from the data tables SVC, and Analyzing errors from data tables cross-memory services.

[[ Contents Previous Page | Next Page Index ]]