Starting syslogd with a cataloged procedure
Update the cataloged procedure, syslogd, by copying the sample in SEZAINST(SYSLOGD) to your system or recognized PROCLIB. Specify syslogd parameters and change the data set names to suit your local configuration. See the syslog daemon section of SEZAINST(EZARACF) for SAF considerations for started procedures. When you start syslogd from a procedure that does not use BPXBATCH, the resulting job name is the same as the procedure name. When you start syslogd from the z/OS® UNIX shell or from a procedure that uses BPXBATCH, the resulting job name is the user ID or the value of the _BPX_JOBNAME environment variable.
See Starting syslogd from the UNIX shell for the syntax of the start options for syslogd.
Below is a copy of the sample procedure:
//SYSLOGD PROC
//*********************************************************************
//* Descriptive Name: SYSLOGD Start Procedure *
//* *
//* File Name: tcpip.SEZAINST(EZASYSLG) *
//* tcpip.SEZAINST(SYSLOGD) *
//* *
//* SMP/E Distribution Name: EZASYSLG *
//* *
//* Licensed Materials - Property of IBM *
//* "Restricted Materials of IBM" *
//* 5650-ZOS *
//* Copyright IBM Corp. 1992, 2023 *
//* Status = ZCSV2R5 *
//* *
//* Note: *
//* The SYSLOGD Daemon can read its configuration file from either a *
//* PDS or the HFS. The procedure defaults to the HFS. *
//* If you are running the IVP for SYSLOGD or if you simply prefer *
//* to use a PDS to store your configuration file, *
//* either delete or comment the CONFHFS DD card *
//* then uncomment the CONFPDS DD card and specify the data set and *
//* member name. *
//* *
//* If you would like to run two instances of syslogd, make a second *
//* copy of this proc and replace -i with -n in the second instance. *
//* The instance using -n will process only log messages received *
//* over the network. One instance must use -i and the other must *
//* use -n in order to run two instances. *
//* *
//* The -c command-line option specifies that syslogd should create *
//* any log files or directories which do not already exist. *
//* *
//* The -i command-line option specifies that syslogd should not *
//* process log messages received over the network. *
//*********************************************************************
//CONFHFS EXEC PGM=SYSLOGD,REGION=0M,TIME=NOLIMIT,
// PARM='ENVAR("_CEE_ENVFILE_S=DD:STDENV")/-c -i'
//*
//*** 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 config data set
//*
//*CONFPDS EXEC PGM=SYSLOGD,REGION=0M,TIME=NOLIMIT,
//* PARM='ENVAR("TZ=EST5EDT")/-c -i -f //''TCPIP.TCPPARMS(SYSLOG
//* )'''
//*
//* Example 2: Environment variables inline, UNIX config file
//*
//*CONFHFS EXEC PGM=SYSLOGD,REGION=0M,TIME=NOLIMIT,
//* PARM='ENVAR("TZ=EST5EDT")/-c -i -f /user1/syslogd.conf'
//*
//* Example 3: Environment variables in STDENV DD
//*
//*CONFSTD EXEC PGM=SYSLOGD,REGION=0M,TIME=NOLIMIT,
//* PARM='ENVAR("_CEE_ENVFILE_S=DD:STDENV")/-c -i'
//*
//* 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 should
//* contain at least TZ (unless you choose to specify TZ in a
//* different fashion), but can contain other environment variables
//* as in this example:
//*
//* SYSLOGD_CODEPAGE=IBM-1047
//* SYSLOGD_CONFIG_FILE=/user1/syslogd2.conf
//* SYSLOGD_DEBUG_LEVEL=127
//* TZ=EST5EDT
//*
//* 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=#
//*
//* 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.SYSLOGD.ENV(SYSLOGD),DISP=SHR
//* Sample UNIX file containing environment variables:
//*STDENV DD PATH='/etc/syslogd.env',PATHOPTS=(ORDONLY)
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSERR DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//CEEDUMP DD SYSOUT=*