Previous Topic: Create VTAM Terminals for the EPI ComponentNext Topic: Install the NetView Operator Facility

Configuring and Installing Optional Components › Configuration Tasks for Optional Base Components › Install the NetView Interface

Install the NetView Interface

Perform these steps to install the CA OPS/MVS NetView interface:

  1. To gain access to the NetView unsolicited message stream, module OPNVEX11 must be relinked with a NetView exit alias name of DSIEX11. To add the DSIEX11 alias using SMP/E, apply usermod OPUM003 contained in library SYS1.OPS.CCLXCNTL(USEREX11). If necessary, copy exit module OPNVEX11 and alias DSIEX11 from SYS1.OPSCCLXLOAD to a library in your NetView STEPLIB concatenation. If you already have a DSIEX11 exit in NetView, then modify it to include the logic in the CA OPS/MVS-supplied exit. Copy exit DSIEX11 from SYS1.OPSCCLXLOAD to a library in your NetView STEPLIB concatenation.

    DSIEX11 resides, in source format, in SYS1.OPS.CCLXASM. The exit sends unsolicited messages to the master console, which in turn routes them through the subsystem interface where CA OPS/MVS can access and automate them.

    Important! If you decide to no longer use the DSIEX11 exit, then you can safely delete the alias name from the load library. The DSIEX11 exit is only an alias name of the OPNVEX11 module.

  2. Copy SYS1.OPS.CCLXEXEC(OPSALERT) to a data set in your NetView DSICLD concatenation. This program is a NetView REXX EXEC.
  3. Establish a connection between NetView and your MCS master console. The interface to issue NetView commands from CA OPS/MVS rules or REXX programs is the same interface that IBM provides to enable NetView commands to be issued from z/OS consoles.

    Use a NetView AUTOTASK command to create an association between the MCS master console and a NetView user ID. You can issue this command at a NetView terminal, or in the NetView initial CLIST member.

    The command has this syntax:

    AUTOTASK CONSOLE=consolenumber,OPID=operatorid
    consolenumber

    The MCS console number.

    operatorid

    The NetView operator ID to be associated with the MCS console. NetView operator IDs are defined in the DSIOPF member of the NetView parameter data set.

    The CA OPS/MVS NetView interface assumes that you have established an association between a NetView operator ID and your MCS master console. Consider modifying your NetView start up CLIST to issue the AUTOTASK command for you when NetView starts.

  4. Modify your NetView startup CLIST to issue the following command: 
    OPSALERT NOTIFY

    This command issues a series of NPDA set recording filter (SRF) commands to give CA OPS/MVS access to NetView alert information. You can issue this command without restarting NetView after you complete step 2 of this NetView installation process.

  5. Copy the message table entry in SYS1.OPS.CCLXCNTL(OPSAUTO) to your NetView automation message table. If you do not have a NetView automation message table, copy the OPSAUTO member to a data set in the NetView DSIPARM concatenation and issue the following command: 
    AUTOMSG MEMBER=OPSAUTO

    To have this command invoked automatically at NetView startup, place it in the NetView start up CLIST.

    If you already have a NetView message table, copy the message table entry to the bottom of your existing message table and reactivate it with the AUTOMSG command.

  6. Copy SYS1.OPS.CCLXEXEC(ALERT) to a library that CA OPS/MVS rules can access (that is a library in the SYSEXEC concatenation). Doing this enables CA OPS/MVS rules and programs to use the ALERT function.
  7. CA OPS/MVS message rules can set or reset a bit in the MSG.AFLAGS variable.

    For more information, see the AOF Rules User Guide.

  8. To use the subset of POI command processors that can run as NetView command processors, define each command processor in the DSICMD member of the NetView parmlib.

    For example:

    *-------------------------------------------------*
*     CA OPS/MVS NETVIEW CAPABLE POI COMMANDS  *
*-------------------------------------------------*
OPSGETV  CMDMDL  MOD=OPSGETV,TYPE=R,RES=Y,PARSE=N
           CMDCLASS=1,2,3
OPSGETVL CMDMDL  MOD=OPSGETVL,TYPE=R,RES=Y,PARSE=N
           CMDCLASS=1,2,3
OPSSETV  CMDMDL  MOD=OPSSETV,TYPE=R,RES=Y,PARSE=N
           CMDCLASS=1,2,3
OPSDELV  CMDMDL  MOD=OPSDELV,TYPE=R,RES=Y,PARSE=N
           CMDCLASS=1,2,3
OPSQL    CMDMDL  MOD=OPSQL,TYPE=R,RES=Y,PARSE=N
           CMDCLASS=1,2,3
*-------------------------------------------------*
*        AUTOMATE/MVS COMMAND ALIASES OF OPSMODE  *
*-------------------------------------------------*
GETVAR   CMDMDL  MOD=GETVAR,TYPE=R,RES=Y,PARSE=N
           CMDCLASS=1,2,3
GETVARL  CMDMDL  MOD=GETVARL,TYPE=R,RES=Y,PARSE=N
           CMDCLASS=1,2,3
SETVAR   CMDMDL  MOD=SETVAR,TYPE=R,RES=Y,PARSE=N
           CMDCLASS=1,2,3
DELVAR   CMDMDL  MOD=DELVAR,TYPE=R,RES=Y,PARSE=N
           CMDCLASS=1,2,3
SQL      CMDMDL  MOD=SQL,TYPE=R,RES=Y,PARSE=N
           CMDCLASS=1,2,3
OPSMODE  CMDMDL  MOD=OPSMODE,TYPE=R,RES=Y,PARSE=N
           CMDCLASS=1,2,3

If the load modules defined in the example above are not available in the system linklist or LPA, you must add a STEPLIB for the CA OPS/MVS load library to the NetView procedure JCL and the library must be APF-authorized.

Since multiple CA OPS/MVS subsystems may be active on one system, default routing of all command requests to a desired subsystem name can be accomplished by allocating a dummy data set with a ddname of OPS$xxxx, where xxxx is the subsystem name; you may use JCL or the NetView ALLOCATE command. OPSS is the default subsystem name. For example:

ALLOC FILE(OPS$OPST) DUMMY
//OPS$OPST DD DUMMY

The CA OPS/MVS security rules do not currently have access to the NetView user ID for security checking of global variable access. To permit global variable access to NetView command processors, you must enable a generic security rule for the NetView address space. For example:

)SEC OPSGLOBAL*
)PROC
  If Opsinfo('JOBNAME') = 'netview job name' Then
    Return 'ACCEPT'
  Else
    Return 'NOACTION'
)END