Enabling and Disabling TWS Automation

SA z/OS TWS Automation may be disabled and enabled by specification of subsystems with an application type of OPC.

To disable SA z/OS TWS Automation, do not specify any TWS applications in the Policy Database for the system that is to have TWS Automation disabled. Disabling occurs on a system-by-system basis, so by not linking TWS type applications to a system, automatically disables TWS Automation.

Disabling TWS Automation causes the message traps in the SA z/OS NetView to also be disabled. This will speed message processing for those systems that do not participate in TWS functions. Disabling TWS Automation does not prevent execution of the INGTWS command. As long as at least one system in the sysplex contains a Controller or Tracker, the INGTWS command will work.

If you disable SA z/OS TWS Automation for any reason, be sure to unlink the TWS Command Receiver NON-MVS subsystem and the TWS Request Receiver NON-MVS subsystem from systems that TWS Automation is disabled for.

To enable SA z/OS TWS Automation, specify the TWS applications for the Controllers and Trackers in the Policy Database of all systems that have either Controllers and Trackers running on them. Include any Trackers that belong to foreign Controllers; that is, Controllers not present anywhere in the sysplex that the Trackers belong to.