EQQG001I EQQG004E
EQQG001I SUBTASK
SUBTASK
HAS STARTED
Explanation: The subtask
SUBTASK
has been successfully initialized.
System action: Processing for the subtask indicated is started.
User response: None.
EQQG002E INITIALIZATION OF SUBTASK
SUBTASK
FAILED. REASON CODE:
RS
Explanation: The subtask indicated could not acquire all the resources needed for normal operation.
System action: Processing continues but no requests from the dialog or the program interface for TME 10 OPC can
be served.
Problem determination: The message variable
RS
can have the following values:
02 The main task, the normal mode manager, is unavailable.
11 The application description file is unavailable.
12 The workstation description file is unavailable.
13 The calendar file is unavailable.
14 The period file is unavailable.
15 The all workstations closed record is unavailable.
16 The operator instruction file is unavailable.
|17 The JCL variables file is unavailable.
|18 The resource description file is unavailable.
|19 The ETT criteria file is unavailable.
User response: Review earlier messages in the TME 10 OPC message log to determine the cause of the error.
System programmer response: Correct errors shown by the earlier messages and restart the subtask indicated.
EQQG003I SUBTASK
SUBTASK
HAS ENDED
Explanation: This message is issued when the TME 10 OPC subsystem is being stopped by an operator command.
System action: TME 10 OPC termination processing continues.
User response: None.
EQQG004E SUBTASK
SUBTASK
ABENDED, IT IS RESTARTED AT
RETRYAT
Explanation: A serious error caused the
SUBTASK
subtask to end abnormally.
SUBTASK
has been able to restart,
at
RETRYAT
.
System action:
SUBTASK
resumes normal processing, but one or more requests for service may have been
rejected. The dialog user requesting service may or may not be informed about the completion or termination of the
requests. A dump is created. Message EQQX271E, when issued, informs the dialog user that the request has failed
due to a serious error in
SUBTASK
. If the subtask is GENERAL SERVICE, the dialog user must press “attention” to
break the request.
Problem determination: Review the dump dataset to determine what caused the problem.
User response: Inform the system programmer about the error and, (if the error can be reproduced), of the
sequence of dialog requests leading to the error.
System programmer response: Collect relevant information about the sequence of events leading to this error,
make the dump dataset and the message log available for inspection, and contact your IBM representative.
Copyright IBM Corp. 1991, 1998 105