Below is an example of the display the DSES transaction produces. Leading zeros have been suppressed.
Teradata Database--CICS SESSION CROSS REFERENCE DISPLAY TRAN TASK# TERM TDP SESS# REQUEST# FUNCTION STA IBUSZ OBUSZ #START #CONT H331 123 1A4B 0 1012 298 CONNECT INC 1024 1024 0 0 H331 125 1A4D 0 1014 3122 STARTREQ INC 1024 1024 2 0 HICE 129 0 1022 3i55 STARTREQ INC 1024 1024 5 11
The headings in the example are defined as follows:
|TRAN||The CICS transaction ID of the last transaction that issued a request on this session|
|TASK#||The CICS task ID number of the last transaction that issued a request on the session|
|TERM||The terminal ID that owns the session if the transaction is started from a terminal. This field contains blanks if the transaction is not started from a terminal|
|TDP||The TDPID of the TDP through which the transaction has established the database session|
|SESS#||The number of the database session (in decimal)|
|REQUEST#||The number of the last database request (in decimal)|
|FUNCTION||The last CLI function that was issued on this session|
|STA||The status of the last request issued on this session, including CMP (complete) or INC (incomplete)|
|IBUSZ||The size (in bytes) of the application’s fetch buffer|
|OBUSZ||The size (in bytes) of the application’s request buffer|
|#START||The count of all database start requests initiated on the session|
|#CONT||The count of all database continue requests issued on the session|
DSES uses Basic Mapping Support (BMS) paging. This enables the operator to page through the DSES output using BMS paging commands.
Teradata recommends that the terminals from which operators issue the DSES transid are defined to CICS with Automatic Transaction Initiation (ATI) so that after invoking DSES, the CICS paging facility can display the first output page.
If the DSES output does not fit on one screen, you can display additional screens by using the CICS operator paging commands. Normal CICS paging conventions apply.