EQQN004E EQQN006E
EQQN004E VSAM PHYSICAL I/O ERROR. DETAILED INFORMATION FOLLOWS: ACTIVE TASK IS
TASK
. LOAD
MODULE IS
MODULE
I/O REQUEST IS FROM
MODID
AT OFFSET +
OFFSET
REQUESTED
FUNCTION IS
FUNC
ON LOGICAL FILE
FILE
, DDNAME
DDNAME
VSAM RETURN CODE IS 12,
REASON CODE IS
RSN
, KEY IS
KEY
VSAM MESSAGE:
SYNAD
Explanation: A TME 10 OPC subtask or batch job encountered an I/O error when accessing a VSAM dataset.
System action: The action taken by the TME 10 OPC subtask or batch job is given by additional messages that
follow this message in the TME 10 OPC message log. The VSAM message supplies information such as jobname,
stepname, unit address, device type, ddname, RBA, error description and so on.
Problem determination: The MSGAREA and MSGGEN parameters of the RPL macro are used to extract the
relevant information presented in the VSAM message. Use the VSAM return code, reason code, and message to
determine the cause of the error. For more information, refer to the appropriate documentation for the MVS/DFP
product installed on this MVS/ESA system.
System programmer response: Correct the errors and, if necessary, rerun the batch job or restart the TME 10
OPC subsystem.
EQQN005E THE NORMAL MODE MANAGER TASK HAS ABENDED. FOR ADDITIONAL INFORMATION SEE
SYSLOG MESSAGES AND DUMP DATA SET
Explanation: A severe error has occurred in the NMM task.
System action: NMM processing is terminated. A dump is created if a dump dataset is defined. Message
EQQZ045W is issued.
Problem determination: Review the preceding messages in the TME 10 OPC message log and SYSLOG datasets,
and the dump dataset to determine what caused the NMM to abend.
System programmer response: Save the message log dataset containing this error message, the dump dataset,
and the SYSLOG dataset. Then contact your IBM representative.
EQQN006E THE NORMAL MODE MANAGER HAS IGNORED THE FOLLOWING INVALID EVENT RECORD
WHILE PROCESSING THE JOB TRACKING LOG DATA SET DURING RESTART FROM
CHECKPOINT:
EXITREC
Explanation: An invalid job tracking event record has been found in the job tracking log dataset. The most likely
error is that the last 4 bytes of the record do not contain the TME 10 OPC identifier EQQ3. It is also possible that the
first 3 characters of the job number field do not contain the character string JOB.
System action: The incorrect job tracking event record is not processed. The NMM continues reading the job
tracking log dataset.
TME 10 OPC administrator response: Note the job name and job number in the exit record. If necessary, set the
correct status for this job manually.
System programmer response: Save the TME 10 OPC message log dataset (EQQMLOG) containing this error
message, and the job tracking log dataset containing the incorrect record. Then contact your IBM representative.
214 TME 10 OPC Messages and Codes
