Defining z/OS log stream(s) for z/OS Connect EE V3.0.39 or higher

Note: If you do not have z/OS Connect EE V3.0.39 or higher, please refer to Overview: Configuring API Monitoring for z/OS Connect EE V3.0.20 or higher.

These instructions assume that you have already completed installation and configuration of a Runtime Environment (RTE) for IBM Z OMEGAMON for JVM, and configured z/OS Connect EE for JVM resource monitoring (Configuring the server for IBM Z OMEGAMON for JVM resource monitoring).

  1. Install the OMEGAMON interceptor V3 product extension for z/OS Connect EE by running script kjjconfig-3.sh.
    This script is located in directory <rtehome>/<rtename>/kan/bin/IBM.
  2. Define DASD-only log streams to the z/OS System Logger.
    Note: A separate z/OS log stream needs to be defined for each monitored z/OS Connect server instance.
  3. Modify and submit the sample job in kjjlogstrm-3.jcl. This job is located in directory <rtehome>/<rtename>/kan/bin/IBM. 
    //STEP1    EXEC PGM=IXCMIAPU
//SYSPRINT DD   SYSOUT=*
//SYSABEND DD   SYSOUT=*
//SYSIN    DD   *
  DATA TYPE(LOGR) REPORT(NO)
  CONTINUE
  DELETE LOGSTREAM NAME(@SMFID@.@COLL-ID@.@JOBNAME@)
  DELETE LOGSTREAM NAME(@SMFID@.@COLL-ID@.@JOBNAME@.REQ)

  DEFINE LOGSTREAM NAME(@SMFID@.@COLL-ID@.@JOBNAME@)
         DASDONLY(YES)
         EHLQ(@EHLQ@)
         AUTODELETE(YES)
         HIGHOFFLOAD(80)
         LS_SIZE(10000)
         STG_SIZE(10000)
         RETPD(1)

  DEFINE LOGSTREAM NAME(@SMFID@.@COLL-ID@.@JOBNAME@.REQ)
         DASDONLY(YES)
         EHLQ(@EHLQ@)
         AUTODELETE(YES)
         HIGHOFFLOAD(80)
         LS_SIZE(10000)
         STG_SIZE(10000)
         RETPD(1)
Next step: Configuring z/OS Connect EE Servers to use the OMEGAMON for JVM Request Monitor 3.0 Interceptor.