Starting and Stopping Universal Enterprise Controller - z/OS
- Former user (Deleted)
- IT Stonebranch
Overview
Universal Enterprise Controller (UEC) for z/OS executes as a started task.
Starting UEC
The UEC started task, UECTLR, is started with the z/OS START command:
Stopping UEC
The UEC started task, UECTLR, is stopped with the z/OS MODIFY STOP command:
After the STOP command is issued, UEC may take several seconds to shut down.
Note
The UECTLR started task should run at a high dispatch priority in order to avoid not being dispatched in a timely enough manner to process the agent polling protocol. If UECTLR is not dispatched appropriately, the Broker may be reported as timed out when the Broker itself still is operational.
System MODIFY Command
The UEC started task accepts commands via the system MODIFY command. The MODIFY command's APPL= parameter is required, since UEC runs as a USS address space.
DUMP Command
The DUMP command directs UEC to produce a Language Environment dump. The dump is written to the CEEDUMP ddname. While the dump is being produced, UEC is paused by LE until the dump completes, after which UEC continues processing.
In the following example, the procedure name UECTLR is assumed:
The DUMP command is used for diagnostic purposes. It should be executed only at the request of Stonebranch, Inc.
BROKERSTAT Command
The BROKERSTAT command provides on-demand Broker status alerting. It causes UEC to issue an alert message for all defined Brokers indicating their current internal state.
- Alert UNV1056T (Unable to connect) is issued for Brokers that are down.
- Alert UNV1059T (Broker responding) is issued for Brokers that are up.
The alert message is equivalent to what UEC issued at the time the alert was originally generated.
In the example below, the procedure name UECTLR is assumed:
Alerts issued on-demand (by BROKERSTAT) are not sent to the I-Activity Monitor client. (When issued under normal processing by UEC, the alerts are sent to I-Activity Monitor.)