Using the syslog daemon for CIM server logging

The z/OS CIM server will connect to the syslog daemon and send all of its log messages to it, where the filtering according to the logLevel configuration property applies as described above. Therefore no messages will be submitted to the syslog daemon which have a higher log level than what's specified in the current value of the logLevel configuration property.

Messages that go to the syslog daemon are prepended with an according z/OS message number, which is either one of the generic CFZ00001E, CFZ00002W or CFZ00004I messages followed by a PGSxxxxx message number, or one of the directly mapped z/OS specific CFZxxxxx message numbers.

Syslog messages from the z/OS CIM server will have an identifier of “CFZCIM" and also contain the CIM server's process ID.

The log levels of the z/OS CIM server are mapped to the following syslog levels:

The syslog service must be properly configured for CIM, and the syslog daemon must be started as described in z/OS Communications Server: IP Configuration Reference and z/OS Communications Server: IP Configuration Guide.

Following is a sample syslog configuration file (/etc/syslog.conf) entry for the CIM server, which tells the syslog daemon to create log files:

...
*.CFZ*.*.debug 	/var/wbem/logs/cimserver_%Y.%m.%d.syslog
... 

When configured like this, the CIM server log messages will be displayed in the format shown by the following example:

Nov  7 12:48:38 BOECFZ1 CFZCIM[33557318]:
CFZ10025I: The CIM server is listening on HTTP port 5,988.
Nov  7 12:48:38 BOECFZ1 CFZCIM[33557318]:
CFZ10028I: The CIM server is listening on the local connection socket.
Nov  7 12:48:38 BOECFZ1 CFZCIM[33557318]:
CFZ10030I: Started CIM Server version 2.11
Nov  7 12:48:38 BOECFZ1 CFZCIM[33557318]:
CFZ12533I: The CIM server failed to register with ARM using
element name CFZ_SRV_PEG2: return code 0x0C, reason code 0x0168.
Nov  7 12:49:01 BOECFZ1 CFZCIM[33557318]: CFZ10031I: CIM Server stopped.

Except for the CIM server's logLevel property, all configuration now occurs through the syslog service as described in z/OS Communications Server: IP Configuration Referenceand z/OS Communications Server: IP Configuration Guide.

Configuration of the syslog daemon for specific processes/daemons is done based on the job name of the process writing the logs.

When you run the CIM server as started task,

the job name is always CFZCIM.

When you have started the CIM server from the UNIX System Services command prompt,

the job name of the CIM server is the user ID that started the CIM server. Be sure that you have set environment variable _BPX_JOBNAME to CFZCIM in order to set the job name of the CIM server correctly. Otherwise it will be difficult to create a syslog configuration for the CIM server.