Tracing in ECI V2 and ESI V2 applications
Applications should implement an option to enable trace. You can control tracing in ECI and ESI Version 2 applications using the functions and environment variables described here.
You can set trace level, file, data length and offset either by using a function call or by setting an environment variable. Examples of each are shown below. To avoid having to recompile applications, enable trace by setting the environment variable.
Trace levelYou can set 5 trace levels:
- Disables all tracing. This is the default setting.
- Enables exception trace points. This level of tracing can be set on permanently to provide an error log capability. Messages are written only for system errors, socket errors, and other Gateway connection errors.
- Enables event trace points and those from lower trace levels.
- Enables function entry and exit trace points and those from lower trace levels.
- Enables debug trace points and those from lower trace levels.
Trace fileThe default trace destination is the standard error stream.
If the trace file is not set, trace is written to the standard error stream (stderr).
Trace data lengthThe trace data length specifies the maximum amount of data that is written to trace when communicating with CICS® Transaction Gateway and the trace level is set to CTG_TRACE_LEVEL4. The default setting is 128 bytes.
Trace data offsetThe trace data offset specifies an offset into data where tracing begins. When combined with the trace data length this allows a specific section of data to be traced, for example a section of data in a COMMAREA. The default setting is zero.