Preparing the environment for configuration

You must prepare your system before adding the OMEGAMON for JVM agent to your RTE.

Procedure

  1. Make sure that IBM OMEGAMON for JVM on z/OS (FMID HKJJ540) is SMP/E installed in the same CSI as other monitoring components.
  2. Create a new file system for OMEGAMON for JVM that uses the RTE_USS_RTEDIR home directory parameter. If the RTE already enabled SDA, or has OMEGAMON for CICS TG agent configured, it means the z/OS® UNIX System Services directory already exists, and you can skip this step.
    This file system must be created, mounted, and in read/write mode before the z/OS UNIX jobs that define the file system paths are submitted. Select a name for your RTE that establishes or fits a naming convention that can be used as you install additional RTEs. The KCIUSSJB sample job in the gbl_target_hilev.TKANSAM SMP/E target library is run in the following RTE configuration task.
    In the MOUNT FILESYSTEM command, the MOUNTPOINT() parameter equates to the value you will specify for the RTE_USS_RTEDIR parameter. For example:
    "MOUNT FILESYSTEM('&hlq_rte_home') TYPE(ZFS) MODE(RDWR) MOUNTPOINT('/rtehome') PARM('AGGRGROW')"
    So an example of this using RTE name TSTEST might be:
    "MOUNT FILESYSTEM('OMVS.TSTEST.HFS') TYPE(ZFS) MODE(RDWR) MOUNTPOINT('/tstest') PARM('AGGRGROW')"
    Note: Take note of the SMP/E TKANJAR DDDEF location in z/OS UNIX, which is key to the PARMGEN WCONFIG($GLB$USR) GBL_USS_TKANJAR_PATH required parameter when OMEGAMON for JVM V5.4.0 is installed.
  3. To use the autodiscovery function properly, give the user ID proper RACF authorities and make sure the SMPTLOAD DDDEF statement is defined in the CSI:
    • The user ID must have the following authorities:
      • READ access is recommended for all the data sets in the system PARMLIB concatenation used during IPL.
      • An OMVS segment with authority to issue the netstat, host and home commands.
    • If you are upgrading from an older version of a product that does not support IBM Discovery Library Adapter for z/OS, make sure that SMPTLOAD is defined in the CSI. Use the following sample job to define the SMPTLOAD DDDEF. Change all occurrences of the following lowercase variables to values suitable to your installation before submitting.
      #globalcsi - The dsname of your global CSI.
#tzone - The name of the SMP/E target zone.
#dzone - The name of the SMP/E distribution zone.
//SMPTLOAD JOB 'ACCOUNT INFORMATION','SMPTLOAD',
// CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID
//
// D e f i n e D D D E F E n t r i e s 
//
//SMPTLOAD EXEC PGM=GIMSMP,REGION=496K
//SMPCSI DD DISP=OLD,DSN=#globalcsi
//SMPCNTL DD 
SET BDY(GLOBAL) .
UCLIN .
ADD DDDEF(SMPTLOAD) CYL SPACE(2,1) DIR(1)
UNIT(SYSALLDA) .
ENDUCL .
SET BDY(#tzone) .
UCLIN .
ADD DDDEF(SMPTLOAD) CYL SPACE(2,1) DIR(1)
UNIT(SYSALLDA) .
ENDUCL .
SET BDY(#dzone) .
UCLIN .
ADD DDDEF(SMPTLOAD) CYL SPACE(2,1) DIR(1)
UNIT(SYSALLDA) .
ENDUCL .
/*
  4. Authorize the monitoring programs.
    1. Authorize the product started tasks:
      1. Update RACF® or equivalent security system for the user ID (with OMVS segment) you will use for the started task of OMEGAMON for JVM (the default started task is IBMJJ).
      2. Identify the user ID you created as a Superuser: 
        ALU <user ID> OMVS(UID(0) HOME(/) PROGRAM(/bin/sh))
      3. Use the RDEFINE commands to associate the ID with the started task IBMJJ and IBMJT (the started tasks of the OMEGAMON for JVM agent and collector):
        */associate the user ID with started tasks
RDEFINE STARTED IBMJJ.* STDATA(USER(userID) GROUP(SYS1))
RDEFINE STARTED IBMJT.* STDATA(USER(userID) GROUP(SYS1))
      4. After you issue all the RDEFINE commands, issue the refresh command:
        SETROPTS RACLIST(STARTED) REFRESH