TRMD runs as an APF-authorized program. The user ID associated with TRMD must be defined with a UID of 0, or must be permitted to become a superuser by having READ access to the BPX.SUPERUSER resource in the FACILITY class. See the EZARACF member of SEZAINST for sample RACF® commands for TRMD.

Use the -p start option or the resolver configuration file to determine the stack that TRMD uses. Ensure that you specify the -p start option or that the RESOLVER_CONFIG environment variable is correctly set before starting TRMD. A separate instance of TRMD must be run for each TCP/IP stack.

The Log records written by TRMD contain two timestamps:
  • A timestamp generated when the event was detected by the stack. This timestamp is generated by the stack and is always Coordinated Universal Time (UTC).
  • A timestamp that is generated when the syslogd record ID is created. This timestamp is dependent on the setting of the TZ environment variable at the time that TRMD is started. If you want this timestamp to be based on UTC, then ensure that the TZ environment variable is properly set (for example, export TZ=0) before starting TRMD.

You can set the TZ environment variable in the following ways:

You can also set the TZ environment variable for all applications in the CEEPRMxx PARMLIB member. You should define the TZ environment variable for all three LE option sets (CEEDOPT, CEECOPT, and CELQDOPT). For example:


For more information on specifying run-time options, see z/OS Language Environment Programming Guide. For details on setting the TZ environment variable, see z/OS UNIX System Services Command Reference.

If running multiple instances of TRMD, consider using the syslogd -u option when starting syslogd. The -u option causes the jobname of the application writing the log record to be included in the log record.

The TCP/IP stack must be running before TRMD can be started.

TRMD can be started from the z/OS shell or as a started task.