The scheduler informs you,
by issuing an "APPLICATION INCONSISTENT" message when trying to save
your application, if a common dependency might be needed to link either
side of a condition relationship. You can do this by using a dummy
operation on a non-reporting general workstation or by using an actual
predecessor of the conditional predecessor operation, if one already
exists within the same application.
For example, An example of APPLICATION INCONSISTENT
problem shows an example that would
cause an "APPLICATION INCONSISTENT" message to be displayed because
JOB4 has only one predecessor, which is conditional.
Figure 1. An example of APPLICATION INCONSISTENT
problem
To avoid the APPLICATION INCONSISTENT error from occurring, without
modifying the job processing flow and logic within the application,
it is sufficient to make the following changes:
Add a dummy operation JOB1 as First Operation (FOP).
Set JOB1 as normal predecessor for JOB2, so that JOB1 is completed
as soon as the occurrence starts to run.
Set JOB1 as normal predecessor for JOB4, and also for all operations
that have only conditional predecessors.
Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.