Updating the BMC AMI Defender parameter file

After you install the BMC AMI Defender component, update your BMC AMI Defender control file as follows to enable it to send SMF records to BMC AMI Ops Insight.

To update the BMC AMI Defender control file

1. Open the BMC AMI Defender parameter file, specified in the PARMS parameter in the BMC AMI Defender for Operational Insight PROCEDURE started task .  The PARMS parameter refers to the member contained within the 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=CZAPOI

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

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

   Note: DSN= indicates where the member is located.

2. Modify the OPTIONS INSTNAME  line to indicate the relevant instance of BMC AMI Defender.

   Note

   INSTNAME must be a 16-character unique name used to identify and isolate the relevant instance of BMC AMI Defender running on your z/OS system (LPAR). Each BMC AMI Defender 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 PortNumber specified in the PORT parameter within the BMC AMI Ops Insight Started Task PROCEDURE JCL. You can find the BMC AMI Ops Insight Started Task JCL in member AMIJCL within AMIHLQ.UBMCSAMP.  If no PORT parameter is used in the Started Task JCL, enter the default PortNumber of 32000 in the BMC AMI Defender for Operational Insight SERVER statement. The PortNumber must be between 1024 and 65535.
   • Make sure the following two parameters are included. If they aren't, add them:
     • TRANS(TCP) 
     • MAXMSG(34000)

   When you are finished, 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 Defender to ensure Db2 functionality and process is enablement. To do this, update the parameters in the SMF OPERINS section. 

   SMF OPERINS               +     ;  Do not modify                                                        
    IFCID(1 2 225)          +     ;  Do not modify                                        
    PROCESS('')             +     ;  Do not modify
    FIELDS(Pred_Record)     +  ;       Do not modify
    /* START      */         +         ; Auto-start DB2 traces          
    /* SSIDS(DEEN,DLL1)  */  +         ; Filter SMF exit SSID processing
    /* INHIBIT(1 2 202 225 230)  */    ; Stop IFCID SMF output          

   The SSIDS parameter allows for limiting processing through BMC AMI Defender 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 Defender for Operational Insight requires inclusion of the Db2 SDSNLOAD LINKLIB as part of the STEPLIB concatenation specified for the BMC AMI Defender for Operational 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 Defender 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)