Updating the BMC AMI Datastream for Ops Insight parameter file

To update the BMC AMI Datastream for Ops Insight control file

1. Open the BMC AMI Datastream for Ops Insight partition data set (PDS) identified by the CZAPARMS DDNAME. You can use the CZAPOI sample member or another member if you require more than one set of options.

   PARMS example

   PARMS=CZAPOI

   Important

   The CZAPOI member contains the customized BMC AMI Datastream for Ops Insight parameters for connecting the BMC AMI Datastream for Ops Insight task to the BMC AMI Ops Insight task described below.

   CZAPARMS example

   CZAPARMS DD DSN=amihlq.CZAGENT.PARM,DISP=SHR

   Important

   DSN= indicates where the member is located.

2. Modify the OPTIONS INSTNAME line to indicate the relevant instance of BMC AMI Datastream for Ops Insight.

   Important

   INSTNAME must be a 16-character unique name used to identify and isolate the relevant instance of BMC AMI Datastream for Ops Insight running on your z/OS system (LPAR). Each BMC AMI Datastream for Ops Insight task on an LPAR must have its own unique INSTNAME identifier.

3. Modify the SERVER statement as follows:

   • Enter the IP address or DNS entry for the z/OS TCP/IP server where BMC AMI Ops Insight is running. Enter the port number specified in the stream.port parameter within the BMC AMI Ops Insight's SMF record handler custom properties file, located in Installation Directory > aoidata/srhinst/conf/custom.properties. You can also find the custom properties in member CUSTPROP within AMIHLQ.UBMCSAMP. If the PORT parameter is not specified in the custom.properties file, enter the default port number of 32000 in the BMC AMI Datastream for Ops Insight SERVER statement. The port number must be between 1024 and 65535.
   • Make sure the following two parameters are included. If they aren't, add them:
     • TRANS(TCP)
     • MAXMSG(34000)

   After modification, the SERVER statement should be as follows:

   SERVER <IP_Address|DNS name>:<PortNumber> TRANS(TCP) MAXMSG(34000)

   For example:

   SERVER SJSD:42000 TRANS(TCP) MAXMSG(34000)

   For more information about SERVER statements, see SERVER statement.

4. You can use BMC AMI Datastream for Ops Insight to ensure Db2 functionality and processing is enabled. To do this, update the parameters in the SMF OPERINS section.

   SMF OPERINS               +         ; Do not alter                   
    IFCID(1 2 225)          +         ; Do not alter                   
    PROCESS('')             +         ; Do not alter                   
    FILTER(                 +         ; Do not alter                      
    OI_timesec(GE 10)       +         ; Do not alter                     
    OI_timesec(LE 58))      +         ; Do not alter                  
    FIELDS(OI_Record        +         ; Do not alter                   
           OI_DB2Ver        +         ; Do not alter                   
           OI_DB2Plex       +         ; Do not alter                   
           OI_DB2SSI)       +         ; Do not alter                   
   /* START      */         +         ; Auto-start DB2 traces          
   /* SSIDS()    */         +         ; DB2 Subsystems                 
   /* INHIBIT(1 2 202 225 230)  */    ; Stop IFCID SMF output  

   The SSIDS parameter allows for limiting processing through BMC AMI Datastream for Ops Insight to the listed Db2 subsystems. The START command allows for setup of the Db2 traces required by BMC AMI Ops Insight. Specifically, its starts Db2 traces to ensure IFCIDS 0001, 0002 and 0225 are created. For more information see SMF Db2 statement.
   The ability to manage Db2 traces from BMC AMI Datastream for Ops Insight requires inclusion of the Db2 SDSNLOAD LINKLIB as part of the STEPLIB concatenation specified for the BMC AMI Datastream for Ops Insight step.

5. Ensure that SMF Exit processing is enabled on each of the LPARs on which Db2 records are created and for which BMC AMI Datastream for Ops Insight collects SMF 100 records to send to the BMC AMI Ops Insight LPAR. Specifically, ensure the SMFPRMxx PARMLIB members have enabled SMF exits for IEFU83, IEFU84 and IEFU85. The SMFPRMxx parmlib member must allow for inclusion of the SMF 100 records and enable the required SMF exits.

   Example

   SYS(NOTYPE(42,43,45,47:49,52:58,79,99,110),

   EXITS(IEFU83,IEFU84,IEFU85,IEFACTRT,IEFUJV,IEFUSI,IEFUJI,IEFUTL,IEFU29),NOINTERVAL,NODETAIL)