Deploying configuration files

When starting the deploy process, the controller loads the CRC numbers and uses them to check whether or not any connected tracker needs a new copy of the configuration file.

As result of the deploy process, each tracker that:

Is connected to the controller
Is at the same level as the controller
Has its destination associated with a workstation present in the current plan

receives an event configuration file updated according to the current content of the controller EQQEVLIB data set. The refreshed configuration file is stored in the EQQEVLST member of the tracker EQQJCLIB data set.

Note: If EQQJCLIB contains also the EQQDSLST member, the resulting triggering selection table is the union of EQQEVLST and EQQDSLST.

Then, each tracker monitors for the events that match the refreshed data, based on an in-storage copy of the configuration file.

The deploy process starts in the following cases:

At tracker connection time.
Periodically, depending on the frequency of handshakes initiated by the trackers, specified by the PULSE parameter of the ROUTOPTS initialization statement.
When processing a modify command with the DEPLOYCF option.

If a tracker destination is referenced in the ROUTOPTS initialization statement, but it is not currently connected, the tracker acquires the configuration file data when the connection is restored.