Syslogd environment variables

Table 1 provides a list of environment variables used by syslogd that can be tailored to a particular installation.

Table 1. Syslogd environment variables
Environment variable	Description	Specific coding rules
SYSLOGD_CODEPAGE	Used by the syslog daemon to specify the EBCDIC code page to be used for the configuration file. The default code page is IBM-1047.	The following code pages are supported: IBM-037 IBM-273 IBM-274 IBM-275 IBM-277 IBM-278 IBM-280 IBM-281 IBM-282 IBM-284 IBM-285 IBM-297 IBM-500 IBM-871 IBM-1047 IBM-1140 IBM-1141 IBM-1142 IBM-1143 IBM-1144 IBM-1145 IBM-1146 IBM-1147 IBM-1148 IBM-1149 Example: `SYSLOGD_CODEPAGE=IBM-1141`
SYSLOGD_CONFIG_FILE	Specifies the name of the syslogd configuration file.	The -f start option overrides this value. Example: `SYSLOGD_CONFIG_FILE=/etc/syslog.conf`
SYSLOGD_DEBUG_DATASET	If this environment variable is not set, the debug output goes to STDOUT. The environment variable can be set to STDOUT, which will also cause the output to be written to STDOUT. On SYSLOGD shutdown, the SYSLOGD_DEBUG_VARIABLE is reset, which causes residual debug output to be written to STDOUT.	Write debug output to an MVS™ dataset `export SYSLOGD_DEBUG_DATASET="//'USER1.SYSLOGD.DEBUG'"` Write debug output to a UNIX file `export SYSLOGD_DEBUG_DATASET="/tmp/syslogd_debug"`
SYSLOGD_DEBUG_LEVEL	Specifies the debug level to be used by syslogd.	You can specify the following debug levels. You can add these together in any combination to select the type of debug messages to be written. 1 Base debugging information. 2 Configuration file processing. 4 Processing of messages being logged by syslogd. 8 Automatic archive processing. 16 Operator command processing. 32 Thread-specific processing. 64 Mutex lock processing. Locks that are specific to threads are logged only if the debug level includes 32. For example, `SYSLOGD_DEBUG_LEVEL=91` includes all debugging information except for message handling and thread-specific processing (including locks). The default debug level is 127, which includes all debug information.
SYSLOGD_PATH_NAME	Specifies the path name for the datagram socket.	The -p start option overrides this value.

When starting syslogd from a shell script, export the environment variables before starting syslogd. The following example defines the syslogd configuration file:
```
#
# Shell script to start syslogd
#
export _BPX_JOBNAME='SYSLOGD1'
export SYSLOGD_CONFIG_FILE="//'HLQ.SYSLOGD.CONFIG(DEFAULT)'"
 /usr/sbin/syslogd &
```
When starting syslogd directly from a started procedure, place the syslogd environment variables in a z/OS® UNIX file or MVS data set. Use the following technique to pass the environment variables to syslogd.
```
// PARM='ENVAR("_CEE_ENVFILE=DD:STDENV")/'

//STDENV DD PATH='/etc/syslogd.env',PATHOPTS=(ORDONLY)
or
//STDENV DD DSN=HLQ.SYSLOGD.ENV(DEFAULT),DISP=SHR
```
When you use an MVS data set for your syslogd environment variables, place the environment variables in a data set with the VB record format [RECFM(VB)] and a logical record length of 256 [LRECL(256)]. If you use any other record format for the data set, use the _CEE_ENVFILE_S environment variable in place of the _CEE_ENVFILE environment variable in your syslogd started procedure. When the _CEE_ENVFILE_S environment variable is used, the system removes trailing blank spaces from each NAME=VALUE line that is read. For additional information about the _CEE_ENVFILE_S environment variable, see z/OS XL C/C++ Programming Guide.