EQQ0355W EQQ0384E
EQQ0355W PREDECESSOR ******** **************** **.** FOR ******** **************** **.** MISSING
Explanation: A predecessor could not be found as expected. It is probably caused by an error in the LTP and/or
OCP.
System action: The job continues
User response: Check the flagged occurrences and contact your system programmer.
System programmer response: Collect documentation and contact IBM Service representative. The following
documentation is required: long-term plan, current plan, job tracking logs. Both the LTP and CP should reflect status
BEFORE the job was run during which the message was issued.
EQQ0370W THE POTENTIAL PREDECESSOR RECORD FOR APPLICATION
appl
COULD NOT BE UPDATED.
THE MAXIMUM NUMBER (1000) OF POTENTIAL SUCCESSOR OPERATIONS HAS BEEN REACHED.
Explanation: The Daily Plan program was unable to add any more successor operation entries to a potential
predecessor record. Since the record could not be updated as intended, it now does not define all potential
successors for application
appl
. If new occurrences of this application will be added by PIF programs or by the ETT
function it will not be possible to add all possible successor dependencies automatically.
System action: The Daily Plan program continues normal processing.
Problem determination: This message indicates that very many different operations in different applications have
defined operations of one application as external predecessors. If the message is unexpected, review the contents of
the AD data base and remove old applications that are no longer used.
User response: When using the MCP dialog to add new occurrences of the application defined by this message the
DEP primary command should be used to verify that successor dependencies have been set up correctly.
EQQ0380E DEPENDENCY LOOP IN APPL NETWORK. OPERATIONS AFFECTED
Explanation: Dependent operations in separate application descriptions form a loop. (Loops in one application are
checked in the application description dialog.) The dependencies between the operations are such that none of the
operations can ever be started. For example: A is dependent on B, B is dependent on C, C is dependent on A. This
message is issued together with EQQ0381E.
System action: No new current plan is produced; however, a printed plan is produced for all valid networks.
User response: Use the Long-Term Planning dialog to change the dependencies, and then resubmit the job.
EQQ0381E APPL **************** ******** **.** OP ******** IN DEPENDENCY LOOP
Explanation: This message is issued together with EQQ0380E. It is issued once for each operation involved in the
dependency loop.
System action: No new current plan is produced; however, a printed plan is produced for all valid networks.
User response: Use the Long-Term Planning dialog to change the dependencies, and then resubmit the job.
EQQ0384E
DLATEXT
Explanation: This message is issued by the Dependency Loop analysis function of the TME 10 OPC Daily Planning
program. This function is invoked whenever a planned network is found to contain one or more loops. That is, a
dependency chain may be such that an operation effectively is dependent on itself.
The dependency loop analysis function studies the contents of this network, and reports the contents of the loop and
related information via this message. The text contained in the variable
DLATEXT
may be one of the following:
DEPENDENCY LOOP FOUND IN AN APPLICATION NETWORK
Dependent operations in separate application descriptions form a loop. (Loops in one application are checked in
the application description dialog.) The dependencies between the operations are such that none of the
operations can ever be started. For example: A is dependent on B, B is dependent on C, C is dependent on A.
This message may also be issued as EQQ0380E.
Chapter 34. EQQnnnn Messages 451