Configuring Sterling Connect:Enterprise for z/OS

For IBM® Sterling Control Center Monitor to monitor Sterling Connect:Enterprise® for z/OS® events, you must configure Sterling Connect:Enterprise for z/OS.

1. After successfully installing IBM Sterling Control Center Monitor, use a text editor such as Notepad to open the $RLOG file in the ControlCenter\conf\CEOS390 directory (ControlCenter/conf/CEOS390 on UNIX). This file contains the Logging application agent rules.
2. Locate the following lines:

    IPADDR=DNS.CONTROL.CENTER,
                  PORT=162,

3. Replace all occurrences of DNS.CONTROL.CENTER with the IP address or DNS name of the IBM Sterling Control Center Monitor engine.
4. Replace all occurrences of 162 with the port number the IBM Sterling Control Center Monitor engine listens on for SNMP traps from the Sterling Connect:Enterprise server.

   For example, if the IBM Sterling Control Center Monitor engine IP address is 10.20.41.9 and the port number it listens on is 8080, the revised file would look like the following example:

   *********************************************************************
   * LOGGING APPLICATION AGENT RULES *
   *********************************************************************
   RULE NAME=ACNEW
        SNMPTRAP TEXT='FUNC=&ACFUNC BNO=&BATCH# ID=&IDFIELD BID="&BID24" +
                      KEY=&KEY RMT=&RMTNAME LINE=&LINNAME STC=&STCNAME L+
                      IST=&LISTNAM FC=&FAILCODE',
                 IPADDR=10.20.41.9,
                 PORT=8080,
                 GROUP1=STATUS,
                 GROUP2=1,
                 ERROR=CONTINUE
   RULE NAME=ACUPD
        SNMPTRAP TEXT='FUNC=&ACFUNC BNO=&BATCH# ID=&IDFIELD BID="&BID24" +
                      KEY=&KEY RMT=&RMTNAME LINE=&LINNAME STC=&STCNAME L+
                      IST=&LISTNAM FC=&FAILCODE',
                 IPADDR=10.20.41.9,
                 PORT=8080,
                 GROUP1=STATUS,
                 GROUP2=2,
   	ERROR=CONTINUE

5. Save the $RLOG file.
6. Use the text editor to open the $RSCH file. This file contains the Scheduler application agent rules.
7. Replace the information that is highlighted in bold text in the following example with the IP address or DNS name of the IBM Sterling Control Center Monitor engine and the port number on which IBM Sterling Control Center Monitor listens for SNMP traps from the Sterling Connect:Enterprise server.

   *********************************************************************
   *  SCHEDULER APPLICATION AGENT RULES EXAMPLE                        *
   *********************************************************************
   RULE NAME=TIMER0
        SNMPTRAP  TEXT='APKEY="&APKEY" FUNC=0',
                  IPADDR=DNS.CONTROL.CENTER,
                  PORT=162,
                  GROUP1=ALARM,
                  GROUP2=8888,
                  ERROR=CONTINUE
   .
   .

   For example, if the IBM Sterling Control Center Monitor engine IP address is 10.20.41.9 and the port number is 8080, this file would contain the following settings:

   *********************************************************************
   *  SCHEDULER APPLICATION AGENT RULES EXAMPLE                        *
   *********************************************************************
   RULE NAME=TIMER0
        SNMPTRAP  TEXT='APKEY="&APKEY" FUNC=0',
                  IPADDR=10.20.41.9,
                  PORT=8080,
                  GROUP1=ALARM,
                  GROUP2=8888,
                  ERROR=CONTINUE
   .
   .

8. Save the $RSCH file.
9. Upload the $RLOG and $RSCH file to the Sterling Connect:Enterprise for z/OS server.

   If your Sterling Connect:Enterprise for z/OS installation already uses Logging and Scheduler application agents, you can insert the new statements into the existing rules.

   See the IBM Sterling Connect:Enterprise for z/OS Application Agents and User Exits Guide for instructions on implementing rules.

10. Perform a rules refresh on the Sterling Connect:Enterprise server. The server can now communicate with IBM Sterling Control Center Monitor.
11. Repeat this procedure for each Sterling Connect:Enterprise server that IBM Sterling Control Center Monitor monitors.
    Attention: Each Sterling Connect:Enterprise for z/OS server that IBM Sterling Control Center Monitor monitors must use a unique port number for sending the SNMP traps.