Daily plan consistency checks on shadow jobs and remote engine workstations

Depending on the type of workstation selected, some fields in the job definition become mandatory. To avoid incongruences, the daily plan batch program, at plan creation or extension, performs consistency checks to ensure that no mismatch has occurred in between the definition of jobs and workstations in the database and their inclusion in the current plan.

Based on the results of the checks, the daily plan batch program can:

Complete successfully.
Generate the plan, providing a return code and a warning message.
Fail to generate the plan, issuing an error message documenting the exception that occurred.

The possible results of the checks run by the daily plan batch against shadow jobs and remote engine workstations are defined in the following sections.

The daily plan batch program generates the plan providing a return code 4 and logging a warning message in the report, if the workstation involved was not yet present in the plan and one of the following situations occurred:

A job, defined on a non-remote engine workstation, contains remote job information.: This situation might occur, for example, if the type of workstation changed from remote engine into another type after the job was defined. In this case the job is no longer considered as a shadow job, but its definition still includes the information that applies to a shadow job.
The daily plan completes with return code 4, message EQQ0396W is logged in the DP batch report, the job is added to the plan, and its remote engine information settings are ignored.
A job, defined on a remote engine workstation, does not contain remote job information.: This situation might occur, for example, if the type of workstation changed to remote engine type after the job was defined. In this case, the jobs defined on that workstation are automatically considered as shadow jobs and so they lack the remote job information.
The daily plan completes with return code 4, message EQQ0391W is logged in the DP batch report, and the occurrence is not added to the plan.
The remote engine type of a workstation was changed causing an inconsistency in the remote job information set in the shadow job.: Because the remote engine type determines the set of information that is necessary to map a shadow job to a remote job instance, if you change the remote engine type you cause an inconsistency in the shadow job definition.
In this case, the daily plan completes with return code 4, message EQQ0392W is logged in the DP batch report, and the occurrence is not added to the plan.

The daily plan batch program fails, at plan extension or replan time, if the workstation is already present in the plan and one of the following situations occurs:

The remote engine type of a workstation existing in the plan was changed.: The daily plan fails and message EQQ0397E is logged in the DP batch report.
The type of a workstation existing in the plan was changed.: The daily plan fails and message EQQ0316E is logged in the DP batch report.