EQQZ045W EQQZ051E
EQQZ045W OPC/ESA SUBTASK
SUBTASK
ENDED UNEXPECTEDLY
Explanation: An TME 10 OPC subtask ended without having been requested to terminate.
System action: TME 10 OPC processing continues.
Problem determination: Review earlier messages in the TME 10 OPC message log to determine the exact reason
for this message. Check if a dump has been created on any dump dataset allocated to the TME 10 OPC started
task.
Operator response: If necessary, restart the failing task using an TME 10 OPC modify command.
EQQZ047E THE GSTASK KEYWORD SPECIFIES A VALUE THAT IS NOT IN THE RANGE 1 - 5
Explanation: The GSTASK keyword in the OPCOPTS initialization statement specifies an invalid value.
System action: TME 10 OPC initialization fails.
System programmer response: Change the GSTASK value to a number within the range 1–5; then restart TME 10
OPC.
EQQZ048I AN OPC/ESA MODIFY COMMAND HAS BEEN PROCESSED. MODIFY
SSNAME
,
FPARAM
Explanation: An TME 10 OPC modify command has been processed successfully.
System action: TME 10 OPC processing continues.
System programmer response: None.
EQQZ049W AN INCORRECT OPC/ESA MODIFY COMMAND HAS BEEN IGNORED. MODIFY
SSNAME
,
FPARAM
Explanation: An TME 10 OPC modify command could not be processed because parameters on the modify
command could not be recognized, or they are inappropriate.
System action: The incorrect command is ignored. TME 10 OPC processing continues.
Problem determination: Check that the syntax of the modify command is correct. If it is correct, you probably have
attempted to start a function that is already active or to stop a function that is not active.
Operator response: Change the modify command, then reissue it.
EQQZ050W THE OPC/ESA SUBSYSTEM HAS BEEN CANCELLED
Explanation: An operator cancel command has been received.
System action: TME 10 OPC terminates without waiting for subtasks to end.
System programmer response: None.
EQQZ051E THE OPC/ESA SUBSYSTEM MOTHER TASK HAS ABENDED
Explanation: A severe error has occurred in the TME 10 OPC subsystem task.
System action: TME 10 OPC terminates without waiting for subtasks to end. A dump is created if a dump dataset
is allocated.
Problem determination: Review earlier messages in the TME 10 OPC message log, SYSLOG dataset, and the
dump dataset to determine what caused the subsystem 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.
412 TME 10 OPC Messages and Codes