EQQPH00I EQQPH06E
Chapter 19. EQQPnnn Messages
EQQPH00I SERVER TASK HAS STARTED
Explanation: The Server task has started successfully. This task is started by the Server Started task. It is started
by the TME 10 OPC subsystem if APPC(YES) is specified in the OPCOPTS initialization statement.
System action: TME 10 OPC continues processing.
EQQPH01I SERVER TASK ENDED
Explanation: The Server task has been requested to stop and is ending normally.
System action: TME 10 OPC continues processing.
EQQPH02E SERVER
NAME
IS ALREADY ACTIVE, IT CANNOT START AGAIN
Explanation: An operator START command has been entered for an TME 10 OPC server that is already active.
System action: The second attempt to invoke the server will terminate.
System programmer response: If you want to restart the TME 10 OPC server, first stop it, and then issue the
START command.
EQQPH03I AN ELEMENT ON THE APPC/MVS QUEUE IS OF UNRECOGNIZED TYPE:
ELEM
Explanation: TME 10 OPC receives APPC/MVS requests, for example Allocate requests, on the APPC/MVS queue.
The queue element presented in the message is not supported by the server task.
System action: The queue element is deleted from the APPC/MVS queue. It causes no further action.
System programmer response: The message variable
ELEM
gives dignostics which is expecially useful if there are
other indications on an error in the TME 10 OPC server APPC/MVS communication.
EQQPH05E BUFFER CONTAINS WRONG AMOUNT OF INPUT DATA, OR WRONG VALUES
Explanation: The communication routines of the TME 10 OPC server APPC/MVS receives data for processing by
the server. The buffer of data is validated and does not pass the validation.
System action: The server deallocates the APPC/MVS conversation. The contact between the TME 10 OPC
dialog, or program interface application, and the TME 10 OPC subsystem is thereby broken. The partner of the
APPC/MVS conversation, a dialog user or a program interface application, is informed about the error by message
EQQPH14E and an error return code. An TME 10 OPC dialog user gets message EQQPH14 displayed at the next
terminal action. A program interface application gets message EQQPH14E written to the message log of the program
interface job, and the EQQYCOM call ends with return code 8.
User response: Follow the actions described for message EQQPH14E. If the problem reoccurs, report the error to
your IBM representative.
EQQPH06E A SERVER SUBTASK ABENDED. THE SUBTASK WAS CREATED FOR PROCESSING APPC/MVS
ALLOCATE DATA:

FMH5 FMH52

Explanation: The TME 10 OPC server has created a subtask for processing requests from a remote dialog user or
a program interface application. The subtask has abended.
System action: The server deallocates the APPC/MVS conversation. The contact between the TME 10 OPC
dialog, or program interface application, and the TME 10 OPC subsystem is thereby broken. The partner of the
APPC/MVS conversation, a dialog user or a program interface application, is informed about the error by message
EQQPH14E and an error return code. An TME 10 OPC dialog user gets message EQQPH14 displayed at the next
terminal action. A program interface application gets message EQQPH14E written to the message log of the program
interface job, and the EQQYCOM call ends with return code 8.
User response: Perform the actions described for message EQQPH14E. If the problem reoccurs, report the error to
your IBM representative.
Copyright IBM Corp. 1991, 1998 231