Configuring and Installing Optional Components › Tasks for Separately Licensed Components › Customize the CA NSM SSM CA OPS/MVS Option

Customize the CA NSM SSM CA OPS/MVS Option

This section contains information on customizing CA OPS/MVS for the CA NSM SSM CA OPS/MVS Option product. We recommend that you install and customize CA OPS/MVS before installing the CA NSM SSM CA OPS/MVS Option product. You may use the Agent Technology agent in any supported release of CA OPS/MVS as the communication method between CA OPS/MVS and CA NSM SSM CA OPS/MVS Option.

To use the Agent Technology agent

1. After you install CA OPS/MVS, customize the following parameters:
   • CAUNICONFIGSET - Set this parameter to the Agent Technology configuration name that was specified during the installation of the Agent Technology agent interface for CA OPS/MVS and CA NSM SSM CA OPS/MVS Option. The configuration data is most likely to be found in member CFGSSMO of the prefix.CCLXCNTL data set for the CA OPS/MVS product. The name after the colon in the statement #CONFIGSET stateman:OPSCNFG is the required name for this parameter. There is no default value.

     The configuration statements also contain the SNMP community names that will be used and the IP address or host names of the CA OPS/MVS and CA NSM SSM CA OPS/MVS Option workstations that will receive SNMP traps from the agent.

     #CONFIGSET stateman:OPSCNFG
     

     Then the CAUINCONFIGSET parameter is set in the CA OPS/MVS initialization REXX EXEC (typically OPSSPA00), as follows:

     OPSPRM('SET', 'CAUNICONFIGSET',"OPSCNFG")
     

   • CAUNICONNECTWAIT - Determines how many minutes the CA OPS/MVS subtask running in the CA OPS/MVS address space waits between retry attempts to connect to Agent Technology running on the same z/OS image. This product parameter is in your CA OPS/MVS start up OPS/REXX EXEC (usually called OPSSPA00). You can set this parameter to any numeric value between 0 and 120. This parameter can be modified at any time.

     Default Value: 0 (no attempt to connect is made)

     Recommended Value: 2

   • INITAWS - Set this parameter to YES to initialize CA OPS/MVS and CA NSM SSM CA OPS/MVS Option.

     Default Value: NO

     Recommended Value: YES

   • CAUNIAGENT - Determines what SNMP agent will be used for communications with CA NSM workstations that are running the CA OPS/MVS and CA NSM SSM CA OPS/MVS Option product.

     Default Value: AWS

     Recommended Value: AWS

     Important! This parameter should not be set to anything other than the default value unless instructed to do so by CA OPS/MVS Technical Support.

   • CAUNIALLOWSET - Determines whether SNMP set requests from the workstation are permitted. If CAUNIALLOWSET is set to a value of NO, set requests will be prohibited; if it is set to a value of YES, requests to modify System State Manager table and resource values that are modifiable on the workstation will be performed, regardless of the origin of the request.

     Note: You can use CA NSM security or Windows security to further filter the use of set requests by user.

   • CAUNIUSERCURRENT and CAUNIUSERDESIRED - Defines a current, desired, or current-desired state combination that is assigned the user status value, which is displayed as the black icon on the CA NSM 2D map.

     Default: No user status definition.

2. Start CA OPS/MVS.

   Note: The CA OPS/MVS main address space must have read access to the TCP/IP data set (hlq.TCPIP.DATA) to determine the correct TCP/IP started task with which it will communicate. The data set must be allocated to ddname SYSTCPD automatically by the system, explicitly in the OPSSPA00 REXX program that is run at CA OPS/MVS initialization, or through a JCL statement in the OPSMAIN started procedure. Consult your systems programmer responsible for installing Agent Technology for the correct data set name to use for the TCP/IP that Agent Technology is communicating with. For example:

   ADDRESS TSO "ALLOCATE FI(SYSTCPD) DSN('hlq.TCPIP.DATA') SHR"
   

   For more information about TCP/IP client data set requirements, see the IBM documentation.

   For more detailed information, see the CA Network and Systems Management Systems Status Manager CA OPS/MVS Option User Guide.

3. (Optional) Complete this step only if your System State Manager tables do not contain the TNGNOTIFY, TNGELIGIBLE, and RESOURCE_TEXT columns.

   Insert these new columns into your System State Manager directory table and all resource tables. The OPTNGCOL member in the SAMPLES library in CA OPS/MVS contains an OPS/REXX program to assist you with this operation.

   The arguments in the OPTNGCOL REXX EXEC are:

   SUBSYS

   The name of the CA OPS/MVS subsystem (usually OPSS).

   ACTIVATE

   A list of currently managed System State Manager tables for which the value in the TNGNOTIFY column is set to ALWAYS. If a currently managed System State Manager table is not listed in the ACTIVATE argument, then when the TNGNOTIFY column is added, it will have a value of NEVER.

   Note: The RESOURCE_TEXT column is added when the TNGNOTIFY column is added.

   RESTABLE

   A list of table names to add the TNGNOTIFY and RESOURCE_TEXT columns and set the TNGNOTIFY value to NEVER. If the ACTIVATE argument is NULL, then this argument defaults to ALL. RESTABLE(ALL) means that the TNGNOTIFY and RESOURCE_TEXT columns will be added to all currently monitored System State Manager tables.

   The following is an example of the program:

   OX 'OPS.CCLXSAMP(OPTNGCOL)' SUBSYS(OPSS) ACTIVATE(SSMQA1)
   

4. For every System State Manager resource whose status you want reported to CA OPS/MVS and CA NSM SSM CA OPS/MVS Option, set the TNGNOTIFY column in its resource table to ALWAYS.
5. For every table that contains a System State Manager resource whose TNGNOTIFY column you set to ALWAYS, set the TNGELIGIBLE column in your directory table to YES (the default directory table is SSM_Managed_TBLS).
6. Decide whether to establish the daily warm start trap. Use the OPSMTRAP OPS/REXX function, which allows the CA OPS/MVS agent to generate warm or cold start SNMP traps on demand. You can also use any variety of AOF rule, such as a daily midnight AOF TOD rule. If you have multiple systems communicating with CA NSM SSM CA OPS/MVS Option, then we recommend that each system send the daily warm start trap at a different time to avoid overloading the network.