Step 36C: Update ZWS Parameters and Exits

About this task

If you use the 'command request interface' that is based on automation workstations, you have to install the exit module EQQUXSAZ.

If you use the 'Conventional Request Interface' that uses general workstations named NVxx, the ZWS exit EQQUX007 has been configured or installed. A recycle of ZWS is required to install the exit 7 module EQQUX007 or the exit 11 module EQQUX011. If you are using an existing exit 7 or exit 11, you can combine these exits with modules that are supplied by ZWS Automation.

ZWS Automation supplies EQQUX007 to detect workstations that are used for NetView communication. The following modules are used as part of this process:
EQQUX007
UX007001
UX007004
EQQUX011
UX011001

EQQUX007 and EQQUX011 are the exit driver programs. They call other modules in turn, as though ZWS is calling each module directly.

The EQQUX007 driver searches for UX007001 through UX007010, and the EQQUX011 driver searches for UX011001 through UX011010. UX007001, UX007004, and UX011001 are supplied with ZWS Automation.

If you have an existing exit 7, rename your module from EQQUX007 to UX007005. If you have an existing exit 11, rename your module from EQQUX011 to UX011002.

The called routines are passed the same parameters as the call to EQQUX007 or EQQUX011.

If you want to add additional exit 7 or exit 11 modules, use the next available name, such as UX007005 or UX011002. This makes it easier to integrate exits that are supplied by various products. Also, because modules are loaded dynamically by the exit driver on each invocation, you may add, delete, or modify an exit module without recycling ZWS.

You must specify the CALL07(YES) parameter in the ZWS z/OS initialization parameters.

You must specify the CALL11(NO) parameter in the ZWS z/OS initialization parameters if you want to monitor CP deletes. CP delete monitoring allows ZWS Product Automation to clear outstanding SDF alerts when an application or operation is deleted from the current plan. However, use of this exit will increase the CPU used by ZWS z/OS.

Other initialization parameters must be specified in the ZWS initialization member (EQQPARM) so that ZWS will issue some of its messages to the MVS console.

The DURATION, ERROROPER, LATEOPER, and OPCERROR messages are automated by ZWS Automation. The RESCONT and QLIMEXCEED messages are useful for further customer automation.

You must specify the following in EQQPARM:

ALERTS WTO (DURATION
   ERROROPER
   LATEOPER
   RESCONT
   OPCERROR
   QLIMEXCEED)

In addition, you must edit the ZWS-supplied message members for certain messages.

The following messages are automated and may require changes to the ZWS-supplied message members in the SEQQMSG0 data set:
Table 1. SEQQMSG0 Data Set
Member Message
EQQE026I EQQE02
EQQE036I EQQE03
EQQE037I EQQE03
EQQE107I EQQE10
EQQFCC1I EQQFCC
EQQN013I EQQN01
EQQPH00I EQQPH0
EQQW011I EQQW01
EQQW065I EQQW06
EQQW079W EQQW07
EQQZ006I EQQZ00
EQQZ086I EQQZ08
EQQZ128I EQQZ12
EQQZ200I EQQZ20
EQQZ201I EQQZ20

Modify these message members to include WTO=YES for the indicated message IDs. Full details for customizing ZWS can be found in IBM Z Workload Scheduler Customization and Tuning.

Note: If you use SDF to monitor the status of ZWS operations, you should enable UX007004 and update INGMSGU1 to remove the Message Automation traps for EQQE026I and EQQE036I. This is to prevent you from receiving multiple SDF alerts for the same ZWS event as a result of the following:
  • SDF alerts that are generated from EQQE036I do not contain an operation number. Therefore, if an application contains operations that have identical job names (with the same IATIME and same workstation ID), it is possible that duplicate or ambiguous alerts are generated.
  • Alerts that are generated from EQQE026I and EQQE036I are not removed from SDF if UX007004 is not active. This is because ZWS does not issue a message when these operations exit error status.