EQQN000I EQQN003E
Chapter 17. EQQNnnn Messages
EQQN000I THE NORMAL MODE MANAGER TASK HAS BEEN REQUESTED TO TERMINATE
Explanation: The Normal Mode Manager has been requested to terminate processing. This request will be
propagated to all active subtasks. The Normal Mode Manager will start its own termination when all subtasks have
ended.
System action: The Normal Mode Manager waits for all subtasks to end. When there are no more active subtasks,
the Normal Mode Manager will back up the current plan dataset and terminate.
Problem determination: If the Normal Mode Manager has not ended within a few minutes, there may be a problem
in one of the subtasks that prevents it from ending normally. If the problem cannot be resolved, cancel the subsystem
started task and request a dump.
System programmer response: None.
EQQN001I REFRESH IS COMPLETE. CURRENT PLAN IS NO LONGER AVAILABLE
Explanation: A current plan refresh request has been processed by the NMM. The current plan dataset has been
closed and the checkpoint dataset has been updated to indicate that no current plan is available. All TME 10 OPC
functions that need access to the current plan dataset are inoperative.
System action: All TME 10 OPC functions that do not need access to the current plan continue processing.
TME 10 OPC administrator response: Schedule a batch job to create a new current plan using only long-term plan
information as input.
EQQN002E THE NMM TASK WAS UNABLE TO READ OR UPDATE CURRENT PLAN OPERATION RECORD
WITH KEY (HEXADECIMAL): F0F3

OPRINDEX

Explanation: The NMM was reading the job tracking log dataset during restart from checkpoint, and met an error
accessing a current plan operation record while processing an automatic job recovery event.
System action: The current job tracking event record is not processed. The NMM continues reading the job tracking
log dataset.
Problem determination: Review the preceding messages in the TME 10 OPC message log and SYSLOG datasets
to determine the cause of the error.
System programmer response: Save the message log dataset containing this error message, and the job tracking
log dataset containing the incorrect record. Then contact your IBM representative.
EQQN003E VSAM ABENDED WHILE ATTEMPTING TO CLOSE DDNAME
FILE
. FOR ADDITIONAL
INFORMATION SEE SYSLOG MESSAGES AND DUMP DATA SET
Explanation: A severe error occurred while closing a VSAM file.
System action: A dump will be generated. The I/O subtask attempts to continue normal termination processing.
Problem determination: Review earlier messages in the TME 10 OPC message log, SYSLOG dataset, and the
dump dataset to determine what caused the close abend.
System programmer response: Save the TME 10 OPC message log and the dump datasets, then contact your
IBM representative.
Copyright IBM Corp. 1991, 1998 213