IBM  Coordinating troubleshooting efforts

Appendix C: Troubleshooting

Gateway-Library support

NoteSkip this section if you are using the DB2 UDB Option for CICS.

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 datastream 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:

Table C-1 shows the tracing functions:

Table C-1: Gateway-Library 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 IMS TM or MVS debugging tools or third party debugging tools to debug user-written applications.

For more information, see:

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.





Copyright © 2005. Sybase Inc. All rights reserved. Coordinating troubleshooting efforts

View this book as PDF