CAIENF Configuration › Customize the ENFSNMPM Procedure

Previous Topic: CAIENF/USS Configuration Tasks

Next Topic: CAICCI Configuration

Customize the ENFSNMPM Procedure

This task is required if you will use the ENF SNMP Monitor.

The ENF SNMP Monitor runs as a started task in its own address space. It runs after the primary ENF address space has been brought up. The proc to start the ENF SNMP Monitor is delivered in the YourdeployHLQ.CAW0PROC Library as member ENFSNMPM. This procedure should be customized according to user solution standards.

To customize the ENFSNMPM procedure

  1. Copy the SNMPVARS member of CAW0OPTV data set to the ENVVAR dsn that will be used by the started task and customize it as needed.

    If the ENFSNMPM Monitor will be used with CA Audit, the library containing the eTrust DLLs must be APF authorized as well as the YourdeployHLQ.CAW0PLD in which the executable for CAW1SNMP resides. For this reason, these libraries should be invoked through STEPLIB in the proc instead of from the linklist.

    If the DLL's exist in a linklisted library and a non-APF authorized STEPLIB, the system will use the linklisted copies, which can cause misleading results when testing.

  2. Use the delivered CAW0PROC ENFSNMPM proc as a sample to customize. The previous release of CA Common Services for z/OS used sample procs CAW1SNMP for IPv4 only and CAV6SNMP for IPv6 or IPv4. This release only delivers one proc, ENFSNMPM which can support both IPv4 or IPv6.
  3. Add a DCM ENF Parm statement for the CAS9DCM4 data collector in order to use the ENF SNMP Monitor. CAS9DCM4 is delivered in YourdeployHLQ.CAW0DCM.
  4. Define a security OMVS segment for the user ID associated with the ENF SNMP Monitor started task because it uses TCP/IP. You can define a new user ID to the security package or you can use an existing user ID that already has an OMVS segment definition.
  5. Define a TSS ACID with a valid OMVS segment for the ENFSNMPM procedure. For example, for TSS users: 
    TSS ADD(stc) PROCNAME(ENFSNMPM) ACID(omvs)

    where you call your procedure ENFSNMPM as delivered, you run it as a started task, and OMVS is the proper ACID to use in your environment.

    If you do not do this properly, you may get a U4093 ABEND with a reason code of x'90'.

Note: With IPv6 support, you may supply the nodename or IP address in many different ways.

IPv4 IP address examples

141.202.65.31

141.202.66.11

Nodename examples

USILCA11

TCPIP11V

USI286ME.CA.COM

IPv6 IP address examples

::1

fd00:7a06:0a20:0100:0000:0000:0000:0011..1086 

0000:0000:0000:0000:0000:ffff:c0a8:060b..1088