EQQ0384E EQQ0384E
LIST OF OPERATIONS CONTAINED IN LOOP FOLLOWS:
This message follows the loop error condition message above, and is a loop contents header message. The
message is always followed by a set of messages, each containing identification of one operation in the loop.
LOOP: OP
OPID JOBN
IN APPL
APPLID
IA
IADATE IATIME
This message follows the loop contents header message, and the message contains operation and application
identification of one operation contained in the loop.
The variable
OPID
contains the operation ID, for example, CPUA_001 the workstation name and operation
number, while the
jobn
variable contain the jobname. The
applid
variable contains the name of the application
containing this operation. Finally the variables
IADATE
and
iatime
contains the input arrival date and time,
respectively, for this operation occurrence.
SUGGESTED DEPENDENCIES CAUSING LOOP ARE:
This message is a dependency loop analysis header, and precedes the analysis. One or more dependencies are
identified as probable causes of the dependency loop, as follows:
1. The operation input arrival is earlier than its predecessor operation's input arrival. The Dependency Loop
Analyzer uses the input arrival time as a primary criteria for locating loop causing dependencies in the NET.
2. The operation is closest to the entry of the loop. That is, it is a predecessor of the first operation in the
loop—the entry—if such exists. The loop entry operation is the “first” operation in the NET, and any operation
that has the entry on the successor path is a candidate for the close to entry criteria.
3. Removal of this dependency has a minimal impact on the NET, but removes the loop. Minimal impact is
defined as the operation having the lowest number of dependencies (successors plus predecessors) in the
NET. A dependency to that operation is then the minimal disturbance dependency. The Dependency Loop
Analyzer locates such operations primarily among the operations having external dependencies, and hence if
an external dependency is reported, it is of minimal impact among the operations having external
dependencies. If no such dependencies are found in the present NET, a minimal disturbance dependency is
reported disregarding the external criteria.
The criteria are weighted in the listed order, so that any operation dependency satisfying the highest (top of the
list) criteria will be reported as probable cause.
MULTIPLE LOOP PATHS ENCOUNTERED IN NETWORK
TME 10 OPC has, when analysing the dependency loop, located more than one loop path. This means, that there
might be more than one causing dependency reported via subsequent messages. The analyze function will
continue with another pass, reflecting the contents of the subsequent loop.
APPLID1 OPID1
JOBN1 DEPT
PATH TO
APPLID2 OPID2 JOBN2
BY IA TIME CHECK
This message contains identification of a dependency that causes the loop, as deduced by TME 10 OPC. The
variables
APPLID1
,
APPLID2
and the
OPID1
,
OPID2
contains application and operation identifiers for this
dependency. The
DEPT
contains the dependency type (SUCC or PRED) of
APPLID1
to
APPLID2
.
The dependency is selected according to the IAtime criteria. That is, the successor operation has an IAtime that
is earlier than the predecessor operation. Note also, that there may be intermediate operations counting from the
reported predecessor operation to the successor operation. This is due to the fact that some operations are not
significant for the networking process and is as such excluded from the NET.
APPLID1 OPID1 JOBN1 DEPT
PATH TO
APPLID2 OPID2 JOBN2
IS CLOSEST TO LOOP ENTRY
This message contains identification of a dependency that causes the loop, as deduced by TME 10 OPC. The
variables
APPLID1
,
APPLID2
and the
OPID1
,
OPID2
contains application and operation identifiers for this
dependency. The
DEPTYPE
contains the dependency type (SUCC or PRED) of
APPLID1
to
APPLID2
.
The dependency is selected according to the closest to loop entry criteria, that is, the dependency is the last
selectable on the loop path, when traversing the path backwards from the loop entry in the present NET.
REMOVAL OF
APPLID1 OPID1.JOBN1 DEPT
PATH TO
APPLID2 OPID2 JOBN2
CAUSES MINIMUM NET
DISTORTION
This message contains identification of a dependency that causes the loop, as deduced by TME 10 OPC. The
variables
APPLID1
,
APPLID2
and the
OPID1
,
OPID2
contains application and operation identifiers for this
dependency. The
DEPTYPE
contains the dependency type (SUCC or PRED) of
APPLID1
to
APPLID2
.
452 TME 10 OPC Messages and Codes