Skip to content
CA Datacom Tools - 15.0
Documentation powered by DocOps

INQ=TRACE--Displaying the Trace Table

Last update October 18, 2018

If the CA Datacom® CICS Services Trace facility is active, CA Datacom® CICS Services posts each CA Datacom®/DB request to an internal table. The Trace Table provides history data for at least 100 events (or for the number of events specified for DBCVTPR's TRACE= parameter). When the Trace Table is full, CA Datacom® CICS Services begins writing over the recorded events, from the top. The events traced are limited to those established on the Trace Criteria List. For details on establishing trace criteria, see TRACE= Using the Trace Facility. Invoke one of the following transactions to display the trace data in the Trace Table.

►►─┬─ DBOC ─┬─ INQuire=TRACE ─┬─ ,TERMID=nnnn ──┬─────────────────────────────►◄
   └─ DBIC ─┘                 └─ ,TRANSID=aaaa ─┘

Note: The DBOC INQ=TRACE command is not available from the console.
  • DBOC/DBIC
    (Required) Specify a transaction ID valid with Operational commands used to monitor system resources. Select the transaction ID for which you are authorized. Leave a space between the transaction ID and the command.
  • INQuire=
    (Required) Command specifying a status display. You may shorten this command to INQ=.
  • TRACE
    (Required) Specifies that CA Datacom® CICS Services is to display the CA Datacom®/DB Trace Table. When INQ=TRACE is specified without any other operand, CA Datacom® CICS Services displays all the traces in the CA Datacom®/DB Trace Table.
  • ,TERMID=nnnn
    Specifies a 4-character terminal ID, limiting the display to Trace Table entries for requests originating from the specified terminal.
  • ,TRANSID=aaaa
    Specifies a 4-character CICS transaction ID, limiting the display to Trace Table entries for requests originated by the named transaction.

When you issue this inquiry, the Trace Table that appears includes the most recent entries. Use the following keys to page the display:

  • PF7 or PF19
    Page Backward to view earlier entries
  • PF8 or PF20
    Page Forward to view more recent entries

To view the Trace Criteria used in generating the displayed Trace Table, use the DBOC/DBIC TRACE command (see TRACE: Displaying Trace Criteria List).

Note: DBOC INQ=TRACE has the ability of shift right/left to display the additional fields of Operator-ID (OPID) and User-ID (USERID).

  • Use PF11/23 to shift the TRACE screen to the right and display OPID and USERID replacing the TERMID and PROGRAM NAME in that sequence.
  • Use PF10/22 to shift left and restore the screen to its original status.

Display Example DBOC INQ=TRACE

TRACE TABLE INQUIRE
 
SEQ   TIME   TASK TERM TRAN PROGRAM  TCB TCB CMMD  TBL  KEY  RTN    URT DBID MUF
NR   HHMMSS    ID   ID   ID NAME     NAM  ID       NAM  NAME CODE    ID       ID
                                                                                
0301 110526    92 ???? NXXU B4XXNTVU L8  002 ADDIT HST SQ005       0400 00400 01
0302 110526    94 ???? NXXU B4XXNTVU L8  006 REDKY ACC SQ004       0400 00400 01
0303 110526    92 ???? NXXU B4XXNTVU L8  002 REDKY ACC SQ004       0400 00400 01
0304 110526    93 ???? NXXU B4XXNTVU L8  004 REDKY ACC SQ004       0400 00400 01
0305 110526    93 ???? NXXU          L8  004 COMIT                 0000       01
0306 110526    92 ???? NXXU          L8  002 COMIT                 0000       01
0307 110526    94 ???? NXXU          L8  006 COMIT                 0000       01
0308 110526    95 ???? NXXU B4XXNTVU L8  005 RDUKY BRN SQ001       0400 00400 01
0309 110526    91 ???? NXXU B4XXNTVU L8  003 RDUKY BRN SQ001       0400 00400 01
0310 110526    95 ???? NXXU B4XXNTVU L8  005 UPDAT BRN SQ001       0400 00400 01
0311 110526    91 ???? NXXU B4XXNTVU L8  003 UPDAT BRN SQ001       0400 00400 01
0312 110526    95 ???? NXXU B4XXNTVU L8  005 ADDIT HST SQ005       0400 00400 01
0313 110526    91 ???? NXXU B4XXNTVU L8  003 ADDIT HST SQ005       0400 00400 01
0314 110526    95 ???? NXXU B4XXNTVU L8  005 REDKY ACC SQ004       0400 00400 01
0315 110526    91 ???? NXXU B4XXNTVU L8  003 REDKY ACC SQ004       0400 00400 01
0316 110526    95 ???? NXXU          L8  005 COMIT                 0000       01
0317 110526    91 ???? NXXU          L8  003 COMIT                 0000       01
                                                                                
PF7/PF19=UP                                               ****  AT END   ****

Note: Routing of the output messages for the DBOC INQ=TRACE command to the JES log is not supported and if used will have unpredictable results.

Field Descriptions

  • SEQ NR
    The number of the trace entry within the Trace Table. Indicates where within the Trace Table the display is positioned.
  • TIME HHMMSS
    The time of day to the tenth of a second at which each event occurred.
  • TASK ID
    The CICS task number.
  • TERM ID
    The ID of the terminal which initiated the listed command or ???? if no terminal was attached to the issue of the command.
  • TRAN ID
    The CICS transaction ID associated with the listed task.
  • PROGRAM NAME
    The name of the program which issued the listed command.
  • TCB NAM
    Task Control Block name in which the transaction was run. This can be the QR TCB of CICS when OPENAPI=NO is specified in the DBCVTPR or in the case of running with OPENAPI=YES, the open TCB NAME where the transaction was run.
  • TCB ID
    Task Control Block sequence number which identifies the CA Datacom® thread used by the current event.
  • CMMD
    The CA Datacom®/DB command being traced.
  • TBL NAM
    The name of the CA Datacom®/DB table accessed by the current event, if any.
  • KEY NAME
    The name of the key for the listed CA Datacom®/DB table.
  • RTN CODE
    Interpret the return code xx.yy as follows:
    • xx
      CA Datacom®/DB external return code (decimal), return code 0 (zero) if value is blank.
    • yy
      CA Datacom®/DB internal return code (hexadecimal), '40' is a blank internal return code.
  • URT ID
    The number of the URT accessed by the current event.
  • DBID
    The ID of the database accessed by the current event, consisting of five numbers nnnnn, where nnnnn can be 00001 through 05000. This field is blank for commands other than actual CA Datacom®/DB data requests such as locates, reads, and maintenance requests as opposed to such commands as opens, closes, and log commands.
  • MUF ID
    The ID of the MUF accessed by the current event, consisting of two numbers nn, where nn can be 01 through 99.
Was this helpful?

Please log in to post comments.