EQQ0531I EQQ0537I
EQQ0531I GENERATED DUP OMITTED:
ADID
DATE
TIME
RCTEXT01
RCDATA01
Explanation: A unique occurrence consists of application description ID, run date, and input arrival time. When
generating occurrences, duplicates have resulted.
RCTEXT01
is 'NORMAL RUNCYCLE:' for offset-based runcycles,
and 'REGULAR RULE:' for rule-based runcycles.
RCDATA01
is
PNAM
SIGN
OFFS
for offset-based runcycles, and
PNAM
for rule-based runcycles.
System action: One occurrence is selected; the others are bypassed. The occurrence selected will be the one
added using the Long-Term Planning dialog (if one exists), or the one with the lowest run cycle number.
User response: Check if the application should really run more than once at the same time. If it should, add it but
make it a unique occurrence, for instance, by altering the input arrival time by one minute.
EQQ0532I
ADID
DAY
TIME
SUPPRESSED DUE TO ONLINE DELETE
Explanation: The occurrence indicated cannot be created because the old long-term plan contains the same
occurrence but is marked as deleted.
System action: The job continues processing but the indicated occurrence is not created.
User response: To create the occurrence, it is necessary to add it again using the Long-Term Planning dialog.
EQQ0534W ORIGIN DATE MAY BE MISSING FOR PERIOD
PNAM
APPLICATION
ADID
Explanation: To be sure of the proper use of the calendar database, you should, for a noncyclic period, have at
least one origin date beyond the specified end date of the long-term plan. This ensures that no work remains
unplanned for the period in question.
System action: The job continues processing.
User response: Investigate whether the noncyclic period
PNAM
should be extended further into the future.
EQQ0535W COULD NOT MOVE
ADID
DATE
TIME
RUNCYCLE:
PNAM
SIGN
OFFS
NOT PLANNED
Explanation: The run date calculated using the run cycle information identified in the message for the occurrence
ADID DATE
TIME
is a free day, and the specified free day rule is 1 (run on the closest work day before the free day).
However, TME 10 OPC could not move the occurrence prior to the free day because the closest work day is before
the current plan end date.
System action: The occurrence is not included in the LTP.
User response: If the occurrence should be scheduled, add it manually to the current plan, or change the run cycle
or calendar information and rerun the LTP batch job.
EQQ0536W CAN NOT MOVE, MODIFY OR DELETE
ADID DATE TIME
. OCCURRENCE HAS SUCCESSOR IN
THE CURRENT PLAN.
Explanation: The occurrence indicated can not be moved, modified, or deleted because it has at least one
successor in the current plan. It occurs in the current plan as a pending predecessor. This message is followed by
message EQQ0537I, which identifies the successor occurrence.
System action: Long-term planning processing continues. The indicated occurrence is not moved, modified, or
deleted.
User response: If required, the occurrence can be modified or deleted using the long-term plan dialog.
EQQ0537I
ADID DATE TIME
Explanation: This message identifies the successor to a pending occurrence in the current plan. This message is
issued together with message EQQ0536W.
System action: Long-term planning processing continues.
User response: Review message EQQ0536W to determine the reason for this message.
Chapter 34. EQQnnnn Messages 461
