Verify Module (EVJESPVY)

The verify module, which runs on a NetView autotask, runs only in the Controller NetView.

This module receives the action request buffer from the PPI dispatcher task. Figure 1 shows this process.

The verify module uses the NVxx index to obtain the destination NetView domain ID from the SA z/OS policy database. If the relevant NVxx index specifies SYSPLEX, then all SA z/OS systems in the local sysplex are queried for the status of the application that is associated with the job name of the request. The destination is determined to be the system that has the application in the most active state.

If the destination NetView and the requesting NetView are the same, TWS Automation logs the request buffer and invokes the request module. If the destination NetView and the requesting NetView are different, TWS Automation sends the request to the proper NetView domain by message forwarding.

If TWS Automation does not find the NVxx index then TWS Automation issues a message, posts the operation status to E (ended-in-error, U003), and logs the results. No communications can occur with this workstation until the definition is corrected. On the domain where the TWS controller is running, the workstation must be defined in the WORKSTATION DOMAINS policy object (ODM entry type). You must manually reset operations that are posted-in-error because TWS Automation carries out no automated recovery for definition errors.

If NVxx is associated with the sysplex that the TWS controller is running on (SYSPLEX keyword in the WORKSTATIONS DOMAIN entry) and TWS Automation does not find the job defined to any online SA z/OS in the local sysplex, then TWS Automation issues a message, posts the operation status to E (ended-in-error, S998), and logs the results. To cater for the situation when all domains, where the job runs, are offline, the operation will be retried if a gateway connection to another SA z/OS becomes active.

If TWS Automation successfully forwards messages, it logs the request buffer and returns control to the module. If TWS Automation cannot send the request, it issues an error message and logs it to indicate communication loss with the requested NetView domain. TWS Automation then posts the operation status to E (ended-in-error, S999) due to loss of contact. When TWS Automation re-establishes communications with this NetView domain, it checks for all outstanding errors because of loss of communications on this workstation. If TWS Automation finds any of these errors, it resets the TWS-operation status to R (ready), which re-invokes the EQQUX007 exit.