Skip this section if you are not using Server Option
RPCs.
The Gateway-Library is a set of functions available for writing applications to enable mainframe environments to communicate with clients attached to TRS. These functions convert client calls into the TDS needed to communicate with TRS and its clients.
Stubs provide access to the Gateway-Library functions. These stubs are a set of object libraries that application programmers can include in job steps used to link-edit programs they create.
Gateway-Library tracing functions enable you to trace program activity globally, for all transactions, or specifically, for individual transactions. Based on the transaction processor, tracing functions provide: A
API tracing for Gateway-Library calls, using the CICS auxiliary (aux) facility
TDS header tracing, using the CICS Error Log
TDS data tracing, using the CICS Error Log
Table G-1 shows the tracing functions:
Function |
Description |
|---|---|
TDINFLOG |
Determines what types of tracing are set |
TDINFSPT |
Indicates whether tracing is on or off for a transaction and returns the transaction ID |
TDLSTSPT |
Lists all transactions for which tracing is enabled |
TDSETLOG |
Turns system-wide tracing options on or off |
TDSETSPT |
Turns tracing on or off for a specific transaction |
TDWRTLOG |
Writes a user message or system entry |
You can use standard CICS debugging tools or third party debugging tools to debug user-written applications.
For more information, see:
Chapter 5, “Tracing and Accounting,” which describes the logging processes.
The Mainframe Connect Server Option Programmers Reference for the appropriate programming language, which describes Gateway-Library tracing functions. PL/1 and COBOL versions of this guide are available.
For CICS, Gateway-Library tracing stores information about the TDS traffic between the mainframe and workstation in the VSAM ESDS file, SYTDLOG1. This information includes any errors detected in the traffic.
Remember that some TDS calls fill up internal TDS buffers before sending them out to the network. For example, a TDSNDROW or TDSNDMSG call does not cause execution of a corresponding CICS EXEC SEND call unless the TDS buffer becomes full.
WARNING! To avoid losing records, periodically archive or delete the trace records on SYTDLOG1. Trace records are appended to this file until it is full; then the records are rejected.
