To pass BMC AMI Energizer for IMS Connect information to the Logger, you must enable "Pass IMS Connect data to Logger" in the IMS Connect options. This allows viewing and correlating Energizer traces and events data in the BMC AMI OPS.
The IMS Connect options are:
Select (type a '/') any of the following:
_ Cache security resource profiles
/ Activate tracing for types selected below
/ Activate journaling for types selected below
/ Pass IMS Connect data to Logger
_ Activate IBM IMS Connect RSM RTN/RSN Codes
To activate the BMC AMI OPS interface:
- Select Pass IMS Connect data to Logger in the IMS Connect options.
- Save IMS Connect options.
- Reload or recycle IMS Connect.
The following messages are printed in the IMS Connect address space JESMSGLG DD, indicating the successful start of interface between Energizer and the BMC AMI OPS.
BMCIPR5112I Logger registration completed successfully
BMCIPR5113I DBC Jobname: QA$ITDBC, JobID: STC9 , ASID: 00B1
BMCIPR5116I Logger registration dataset name: NGL RTCS PRODUCT REGISTRY
The jobname is the name of the DBC address space.
Tips
- BMC Execution Component for z/OS (DBC) address space is running in the LPAR.
- The Energizer logspace is defined in the parm dataset used by both the DBC and the BMC AMI OPS started tasks. The logspace name for Energizer should always be set to IPR.
- The configuration member MVLOPTS in DBCENV dataset in the DBC PROC should point to the UBBPARM dataset as follows:
Copy LOGGER00 and MVINGINI members from UBMCSAMP TO UBBSAMP.
- The UBBPARM dataset points to the member MVNGLINI to create initialization parameters for the Logger agent running in the DBC address space.
- MVNGLINI member SYSP= parameter should point to the correct LOGGERxx member.
For example: SYSP=(00, 01, AA) will point to LOGGER00, LOGGER01, and LOGGERAA.
The following parameters in the LOGGERxx member requires user-defined values:
| |
|---|
| Identifies the data set prefix for the allocated log data sets. |
| Specifies the one- to four-character subsystem ID that is to be used by the started task procedure. |
| Specifies a three- to eight-character name for the logspace to which this LOGGERxx member applies. For Energizer, specify LOGSPACE=IPR. |
- The LOGSSID value in LOGGERxx member should match the MVLOGSS in UBBPARM member BBISSP00.
MVLOGSS=ssid
* MVLOGSS= XXXX SPECIFIES THE SSID OF THE LOGGER TO
* SEND JOURNAL RECORDS TO.
The following sample syntax creates a LOGGERxx member for Energizer Connection to the Logger. This member can end with any suffix except 00.
MVSSYSTEM=&SYSNAME
COMPRESSION=YES
DATACLASS=DEFAULT
LOGPREFIX=xxxxx.IPR&SYSNAME
LOGSSID=MV02
LOGSPACE=IPR
MULTIREC=NO
The following is an example of MVINGINI created from configuration step in install:
*--------------------------------------------------------------------*
* PURPOSE: *
* THIS MEMBER IS USED TO DEFINE ALL KNOWN INPUT. *
* *
* *
* *
* *
*--------------------------------------------------------------------*
SYSP=(00) you would add the created suffix number here (ie (00,02)
* - USE TO SPECIFY PREVIOUS MVLOGGER
* PARMS TO CONVERT. THERE IS A MAX
* OF 10 SUFFIXES THAT CAN BE SPECIFIED.
* THE FORMAT IS SYSP=(XX,XX,XX)
*
*PARMDSN=<PARM DATA SET>
* - PDS DATASET NAME WHERE PREVIOUS
* LOGGERXX (WHERE XX IS IN THE
* SYSP= LIST)
*
DBCID=DC&SYSCLONE.
* - USED TO SEND ALL XML TO DBC
*
*NGLID=
* - USED TO SEND ALL XML TO NGL
*
RETENTION=60 *LSRETAIN
*
DSMAX=10 *DSMAX
*
DSMIN=5 *DSMIN
*
SPACE=500 *LSSIZE
*
The following is an example of the MVLOPTS member in the DBCENV dataset in the DBC PROC:
*
PIID=MVL1
INIP=NI
*OGS=xxxx.xxxx.UBMCPARM
LOGS=xxxx.xxxx.UBBPARM