Edit Server - Trace

Application Application Container Auxiliary Trace Active Cold Start Diagnostics File Communications Dump on System Abend Exit Local Trace Size Maximum Diagnostics File Size | Request Handler RM Interface Storage Control Table Management Task Control Trace Flags Trace Table Size

Edit Server - Trace

  Use this page to change the trace attributes of a server.

  Warning: Changing the properties of a registered server may cause application connection errors and loss of data.

  Top

Trace Table Size

  Specify the number of entries the trace buffer can hold before it wraps back to the start. (The trace buffer is also written to disk at this point if you checked Auxiliary Trace Active.) A value of 2 means that there is space for only one entry, and if you checked Auxiliary Trace Active each entry is written straight out to disk. Each entry is 24 bytes long.

  Top

Local Trace Size

  Specify the number of entries the local trace table can hold before it wraps back to the start. A value of 0 (zero) means that no local trace table is allocated. Each service execution process has its own local trace table. Each entry is 24 bytes long.

  Top

Maximum Diagnostics File Size

  Specify the maximum size of the auxiliary trace and dump file in kilobytes. A value of 0 (zero) means that there is no maximum size.

  Top

Cold Start Diagnostics File

  Check this to indicate that the auxiliary trace and dump files are to be deleted when the server starts.

  Top

Dump on System Abend

  Check this to indicate that the server should produce a dump if one of its own processes, such as a service execution process, terminates abnormally. The dump information can help you to determine the cause of the abnormal termination

  Top

Auxiliary Trace Active

  Check this to indicate that trace records are to be flushed to disk before the trace table is overwritten. You should do this only if you have adequate disk space available, since the file can become very big very quickly. If you have a high-activity system use this field in conjunction with Maximum Diagnostics File Size to limit the disk usage. Writing out to a file also degrades performance.

  Top

Trace Flags

  Use these flags to control what information is written to the trace file for this server. Any changes you make to these fields while a server is running take effect immediately.

  Top

Task Control

  Check this to indicate that the server is to trace its task control component.

  Top

Storage Control

  Check this to indicate that the server is to trace its storage control component.

  Top

Table Management

  Check this to indicate that the server is to trace its table management component.

  Top

Application Container

  Check this to indicate that the server is to trace its application container component.

  Top

Request Handler

  Check this to indicate that the server is to trace its request handler component.

  Top

RM Interface

  Check this to indicate that the server is to trace its resource manager interface component.

  Top

Communications

  Check this to indicate that the server is to trace its communications component.

  Top

Application

  Check this to indicate that the server is to trace the CICS API calls made by a CICS application.

  Top

Exit

  Check this to indicate that the server is to trace user and system exits.

  Top