OMPROUTE parameters

OMPROUTE accepts five command line parameters, which govern tracing and debug information. OMPROUTE's trace and debug information is written to stdout with three exceptions:

When OMPROUTE is started with no tracing, and then a MODIFY command is issued to enable tracing. In this case, by default, the output destination is the file omproute_debug in the current temporary directory (the default is /tmp).
When the debug output destination has been overridden with the use of an environment variable (OMPROUTE_DEBUG_FILE or OMPROUTE_IPV6_DEBUG_FILE).
Rule: OMPROUTE_DEBUG_FILE and OMPROUTE_IPV6_DEBUG_FILE can specify only a z/OS® UNIX file. To have debug information go into an MVS™ data set, instead of coding these environment variables, use the SYSPRINT DD card to redirect stdout to the wanted MVS data set.
When the OMPROUTE CTRACE with option DEBUGTRC (or option ALL) is enabled. In this case, the output is sent to the CTRACE facility.

If OMPROUTE is to be started from an MVS procedure, add your parameters to PARM=() in the OMPROUTE cataloged procedure. For example:

//* PARM=('POSIX(ON)',                           
//*       'ENVAR("_CEE_ENVFILE=DD:STDENV")/-t1 -6t1') 
//*

If OMPROUTE is to be started from a z/OS shell command line, enter the parameters on the command line.

For either method of starting OMPROUTE, parameters can be specified in mixed case.

Note: The -tn, -dn, -6tn, -6dn, and -sn parameters affect OMPROUTE performance. If you use these parameters, you might need to increase the Dead_Router_Interval value on OSPF interfaces to prevent neighbor adjacencies from collapsing. If this becomes necessary, you will also need to modify other routers because the Dead_Router_Interval value must be the same for all routers attached to a common network.