Scheduling Through a Non-Control-M Production Control System

The primary advantage of invoking Control‑D report decollating missions from the user exit of a production control system is that scheduling criteria only have to be defined once (under the production control system). The user does not have to update scheduling criteria of report decollating missions each time they are updated in the production control system.

The following methods can be used to implement Control‑D in data centers that use a production control system other than Control‑M:

• Control‑D scheduling is managed independently of the production control system. This method is the same as managing the scheduling without any production control system.
• The scheduling of report decollating missions under Control‑D is controlled by the production control system (described in the following paragraphs).

Most production control systems include some means of passing control to a user exit before a job is submitted. Some products have user exits in earlier stages (when the decision to schedule a job for a specific day is made). The basic idea is to invoke the Control‑D report decollating mission from the user exit of the production control system.

Operating a production control system and Control‑D together in the same environment may cause the following situations:

• A job that is to be run by the production control system does not have any reports. It does not need to be processed by Control‑D.
• A job that is to be run by the production control system does not yet have a report decollating mission defined for the job.
• A job is to be run by the production control system and decollated by Control‑D.

To handle the situations mentioned above, the user must use some method of specifying to the production control system user exit whether to issue a report decollating mission for the job. The decision of how to mark a job is local for each installation and can be performed using one of the following methods:

• Specify a flag in a job scheduling parameter of the production control system that is otherwise unused, or is used for another purpose (for example, the job description).
• Use a list accessed by or internal to the user exit. The list must be modified whenever a new report decollating mission is defined.

When the production control system user exit receives control and a decision is made to invoke a report decollating mission, the user exit must activate program CTDRRQ. This program performs a search for the report decollating mission. For more information about program CTDRRQ and its parameters, seePrograms Called During New Day Processing.

The search is made for a member name with the same name as the job name and for the specified category. The scheduling criteria of the Control‑D report decollating mission (if any) are ignored. The report decollating mission parameters are passed to Control‑D User Exit CTDX001. This exit can alter the contents of the decollating parameters or cancel the decollating mission. If the report decollating mission is not cancelled by the exit, it is placed in the Control‑D Active Missions file.