Destination of OMPROUTE trace and debug output

If the OMPROUTE CTRACE with option DEBUGTRC (or option ALL) is not enabled, then output from OMPROUTE tracing and debugging is written to the debug output destination. The debug output destination is based on the OMPROUTE_DEBUG_FILE and OMPROUTE_IPV6_DEBUG_FILE environment variables. If OMPROUTE was started without tracing enabled and OMPROUTE_DEBUG_FILE/OMPROUTE_IPV6_DEBUG_FILE is not defined and tracing is started later using the MODIFY command, the trace output destination is $TMP/omproute_debug, where $TMP is the value of the TMP environment variable.

When OMPROUTE_DEBUG_FILE is defined, the first trace file created for OMPROUTE initialization and IPv4 routing protocol tracing is named using the value coded on OMPROUTE_DEBUG_FILE. When OMPROUTE_IPV6_DEBUG_FILE is defined, the first trace file created for IPv6 routing protocol tracing is named using the value coded on OMPROUTE_IPV6_DEBUG_FILE. When either of these first files is full, the extensions are changed to 00N, where N is in the range of 1 to the number of files specified in the OMPROUTE_DEBUG_FILE_CONTROL environment variable (default 4). The current file is always the file named using the value coded on OMPROUTE_DEBUG_FILE/OMPROUTE_IPV6_DEBUG_FILE and the oldest file is the highest N value. This eliminates the danger of OMPROUTE filling the z/OS® UNIX file system when tracing is active for a long time.

The size and number of debug files created can be controlled by the OMPROUTE_DEBUG_FILE_CONTROL environment variable. This allows you to adjust how much OMPROUTE trace data is saved. You tailor this parameter to your network complexity or available z/OS UNIX file system storage capacity. See z/OS Communications Server: IP Configuration Guide for details on this environment variable.

If the OMPROUTE CTRACE with option DEBUGTRC (or option ALL) is enabled, then output from OMPROUTE tracing and debugging is sent to the CTRACE facility. The OMPROUTE CTRACE facility can write trace records to an internal buffer or to an external writer. When the OMPROUTE CTRACE with option DEBUGTRC (or option ALL) is active, the normal debug output destinations are ignored. If the CTRACE is disabled, and a trace level is modified, then OMPROUTE once again follows the above rules for determining the debug output destination.