NetView and BMC AMI Ops Automation communication

Communication between the NetView address space and the 

BMC AMI Ops Automation

 address space is achieved by individual tasks in the address spaces.

A task in the BMC AMI OpsA address space acts as the recipient of all requests issued through the NAIEXEC command from the NetView address space.

Related topic

Using-BMC-AMI-Ops-Automation-Access-NV

The task in the NetView address space services all requests addressed to it from the BMC AMI OpsA address space (IMFEXEC NETVIEW commands as well as emulator requests). The NetView task is implemented as an OPT (Optional task). At startup, NetView automatically attaches this task. Alternatively, a NetView operator can start the task manually.

A NetView address space in this configuration primarily addresses requests to one specific partner BMC AMI OpsA, the associated subsystem (SS). If a request is not specifically destined for this BBI-SS PAS, then BMC AMI OpsA routes the request to its final destination, which might be on a local or remote system.

Any BMC AMI OpsA on the same MVS system as the NetView system can request directly service from it. An BMC AMI OpsA request to NetView does not require a one-to-one connection.

NetView communication to an BMC AMI OpsA requires that NetView attach to only one BMC AMI OpsA. For requests initiated in the BMC AMI OpsA address space, any number of SS-NV relationships can be maintained. This feature allows a terminal session to access a NetView system through its target (CICS1 or NV1 in this example).

In the example, the terminal session user, TS1, accesses CICS2 and enters a NetView command. The command is processed at the NetView related to CICS2, which is NV1.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*