Starting the traffic regulation manager daemon (TRMD) as a started task

The offset from Coordinated Universal Time (UTC) of the syslog time in the timestamp of TRMD messages is determined by the TZ environment variable described in z/OS UNIX System Services User's Guide.

To cause the timestamp to appear in coordinated universal time (UTC), specify the TZ environment variable in the start TRMD procedure. For example:
//   PARM=('POSIX(ON) ALL31(ON)',                              
//   'ENVAR("LIBPATH=/usr/lib"',                               
//   '"TZ=0")/-d 1') 

Use the S TRMD command on an MVS™ console or SDSF to start the TRM daemon. A sample procedure is included in member EZATRMD in SEZAINST.

//TRMD      PROC
//*
//*   IBM Communications Server for z/OS
//*   SMP/E distribution name: EZATRMDP
//*
Start of change//*   5650-ZOS Copyright IBM Corp. 1996, 2013End of change
//*   Licensed Materials - Property of IBM
//*   "Restricted Materials of IBM"
//*
Start of change//*   Status = CSV2R1End of change
//*
//*   Function: Sample procedure for running the Traffic
//*             Regulator Management Daemon (TRMD)
//*
//TRMD   EXEC PGM=EZATRMD,REGION=4096K,TIME=NOLIMIT,
//   PARM=('POSIX(ON) ALL31(ON)',
//   'ENVAR("LIBPATH=/usr/lib")/')
//*
//*** Notes:
//*
//* - TRMD can also be invoked from the Unix System Services shell
//*   as a shell command: trmd
//*
//* - The system link list concatenation must contain the TCP/IP
//*   runtime libraries and the C runtime libraries.  If they are
//*   not in the link list concatenation, this procedure will need
//*   to be changed to STEPLIB to them.
//*
//* - To pass parameters to TRMD, specify them after the final slash
//*   on the PARM statement.  For example:
//*      //   PARM=('POSIX(ON) ALL31(ON)/-d 1')
//*
//* - TRMD must find the TCP/IP job name with which it should be
//*   associated.  It uses the -p start option or the TCPIPJOBNAME value
//*   from the TCPIP.DATA file.  The TCPIP.DATA file used can be
//*   controlled by setting the RESOLVER_CONFIG environment variable.
//*   See examples below.
//*
//*** Examples for specifying environment variables and parameters
//*** (parameters must extend to column 71 and be continued in
//*** column 16):
//*
//*  Example 1: Environment variables inline, MVS resolver data set
//*
//*   PARM=('POSIX(ON) ALL31(ON)',
//*   'ENVAR("RESOLVER_CONFIG=//''SYS1.TCPPARMS(TCPDATA)''","TZ=EST5EDT
//*            ")/')
//*
//*  Example 2: Environment variables inline, UNIX resolver file
//*
//*   PARM=('POSIX(ON) ALL31(ON)',
//*   'ENVAR("RESOLVER_CONFIG=/etc/resolv.conf","TZ=EST5EDT")/')
//*
//*  Example 3: Environment variables in STDENV DD
//*
//*   PARM=('POSIX(ON) ALL31(ON)',
Start of change//*   'ENVAR("_CEE_ENVFILE_S=DD:STDENV")/')
//*
//*   For this method, the STDENV DD statement below must be
//*   changed to point to a MVS data set or UNIX file containing
//*   settings for any environment variables.  For example, it shouldEnd of change
//*   contain at least TZ (unless you choose to specify TZ in a
//*   different fashion), but can contain other environment variables
//*   as in this example:
//*
//*     RESOLVER_CONFIG=//'SYS1.TCPPARMS(TCPDATA)'
//*     TZ=EST5EDT
//*
Start of change//*   If you want to include comments in the data set or
//*   z/OS UNIX file, specify the _CEE_ENVFILE_COMMENT
//*   environment variable as the first environment variable
//*   in the data set or file.  The value specified for
//*   the _CEE_ENVFILE_COMMENT variable is the comment character.
//*   For example, if you want to use the pound sign, #, as
//*   the comment character, specify this as the first
//*   statement:
//*     _CEE_ENVFILE_COMMENT=#
//*End of change
//*   The use of the STDENV DD statement works well when more than
//*   one environment variable is specified, as there is a JCL limit
//*   of 100 characters on the PARM statement.
//*
//*   Note: Language Environment recommends a variable record format
//*         for the STDENV file.
//*
//*   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:
//*
//*     CEECOPT(ALL31(ON), ENVAR('TZ=EST5EDT') )
//*     CEEDOPT(ALL31(ON), ENVAR('TZ=EST5EDT') )
//*     CELQDOPT(ALL31(ON), ENVAR('TZ=EST5EDT') )
//*
//*   For more information on specifying run-time options, see z/OS
//*   Language Environment Programming Guide. For details on setting
//*   the LIBPATH and TZ environment variables, see z/OS UNIX System
//*   Services Command Reference.
//*
//STDENV   DD DUMMY
//* Sample MVS data set containing environment variables:
//*STDENV   DD DSN=TCPIP.TRMD.ENV(TRMD),DISP=SHR
//* Sample UNIX file containing environment variables:
//*STDENV   DD PATH='/etc/trmd.env',PATHOPTS=(ORDONLY)
//SYSPRINT DD SYSOUT=*,DCB=(RECFM=F,LRECL=80,BLKSIZE=80)
//SYSIN    DD DUMMY
//SYSERR   DD SYSOUT=*
//SYSOUT   DD SYSOUT=*,DCB=(RECFM=F,LRECL=80,BLKSIZE=80)
//CEEDUMP  DD SYSOUT=*,DCB=(RECFM=FB,LRECL=132,BLKSIZE=132)
Figure 1. TRMD sample procedure