Skip to main content
Skip table of contents

z/IRIS Client logging

Created: | Updated:

z/IRIS clients automatically merge DD:STDOUT and DD:STDERR into DD:SYSOUT.

Events that require System Programmer attention are written to SYSLOG.

Example SYSOUT from z/IRIS client Started Task:
2023-08-31 09:30:26   INFO     ZIRIS ZIR001I z/IRIS Client V1.14.0 is starting.
2023-08-31 09:30:42   INFO     ZIRIS ZIR002I Configuration loaded. Properties follow:
                        mode = kafka
                        kafkatopic = ziris
                        INMEM ID:1 = IFASMF.S0W1.INMEM.DB2
                        Kafka Nodes =
                        Kafka Properties = /kafka/
                        alias =
                        reconnect = 10 seconds
                        timeout = 7 seconds

2023-08-31 09:30:42   INFO     ZIRIS ZIR003I Evaluating SMF streaming configuration.
2023-08-31 09:30:42   INFO     ZIRIS ZIR013I MVS commands are enabled.
2023-08-31 09:30:42   INFO     ZIRIS ZIR011I 1 SMF in-memory resources will be opened for streaming.
2023-08-31 09:30:43   INFO     ZIRIS ZIR012I Setting Kafka
2023-08-31 09:30:43   INFO     ZIRIS ZIR005I Initiating Kafka Producer.
2023-08-31 09:31:19   INFO     ZIRIS ZIR006I Kafka Producer initiated.

Logging properties

The $APP_HOME/lib/ file contains the logging properties for the z/IRIS z/OS client.


All valid values for java.util.logging.Level apply.

Changing the logging level to FINER or FINEST should only occur when troubleshooting the z/OS client’s operations. FINEST will produce large amounts of output to STDOUT is not recommended unless instructed by z/IRIS support.

Logging z/OS Client communication metrics

The z/OS Client can be configured to log its communication metrics to DD:STDOUT. To activate metrics logging, perform the following steps:

  1. In the $APP_HOME/lib/ file, change com.msc.zos.ziris.level to FINE.

  2. In the $APP_HOME/lib/ziris.comm.config, change monitor.thruput.interval={5-3600} to the desired interval, in seconds, at which the metrics should be logged.

  3. Change the DD:STDOUT in the z/IRIS started task proclib member to indicate that STDOUT should be spun after 500,000 lines.

  4. Restart the z/OS Client Started Task.


Level.FINE is reserved for logging metrics only and will not result in any additional debugging log records.

The following example of log output represents the z/OS Clients metrics:

2023-08-31 09:32:32   FINE     ZIRIS ID: 1 #Recs_Read: 267, #Recs_Send_SUCCESFUL: 267, #Recs_Send_FAILED: 0
2023-08-31 09:33:32   FINE     ZIRIS ID: 1 #Recs_Read: 598, #Recs_Send_SUCCESFUL: 598, #Recs_Send_FAILED: 0
2023-08-31 09:34:32   FINE     ZIRIS ID: 1 #Recs_Read: 926, #Recs_Send_SUCCESFUL: 924, #Recs_Send_FAILED: 0

JZOS Batch Launcher Logging Levels

The logging level for the JZOS batch launcher is controlled by the LOGLVL parameter in the z/OC Client’s started task JCL.

// JAVACLS='com.msc.zos.ziris.zIrisClient',                                      .
//   LOGLVL='+N'

Changing the logging level to '+T' or '+D' will result in large amount of log output and should only be used to debug z/OS Client system.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.