Conventional Request Flow

This section contains a detailed description of the flow of a request from TWS to NetView and the return confirmation, including the modules that are involved.

Figure 1 uses a request to start RMF, located in a NetView domain NVREG with a workstation definition of NV04. This request is an operation in a TWS-defined application known as MAINT.
Figure 1. NetView-TWS Interface Flow. Note that syntax and definition errors, target system availability, recovery, and resynchronization via TWS API and NetView PPI are not shown in this example.
- Interface Flow

Using dependency control to ensure an orderly flow of operations, TWS defines the TWS-controlled application named MAINT. TWS defines the application on an automatic general workstation, specifying the NetView that the request is sent to. NVxx specifies a NetView automatic general workstation with a NetView domain index of xx. This is resolved in the Controller NetView to the target NetView domain ID using the definitions in the SA z/OS policy database. TWS can define the NVxx workstation with all regular specifications, such as parallel servers and special resources. If the NVxx index specifies *LOCAL, the command is processed locally.

In the MAINT example in Figure 1, TWS defines the last batch application that is processed before starting RMF with an operation number of 15. Once this completes properly, the normal TWS dependency control readies the NV04_20 operation on the NV04 workstation. This signifies that the request contained within the operation description field is sent to the NetView with a domain ID of NVREG.

TWS Automation uses the NetView PPI to transfer the request from TWS to NetView. This transfer is through the EQQUX007 exit in the OPC/ESA controller.