EQQM399W EQQM403E
EQQM399W CM ACTION SPECIFIED FOR THIS JOB IS
OCHCNO
Explanation: The job to be rerun contains GDG datasets but catalog management action for the operation is none.
The absolute GDG value is missing therefore missing and the GDG dataset cannot be resolved.
System action: The JCL is presented to the user with the GDG dataset specification unchanged.
User response: Change the DD statement manually. When using steplevel restart for operations containing GDG
datasets the catalog management action should be set to D or Y (D is recommended).
EQQM400W THE OPERATION HAS NOT BEEN SELECTED FOR RESTART
Explanation: To use the row command just entered, the operation must have been selected previously for restart.
System action: None.
User response: Enter the S (select) row command to select the operation for restart, then enter one of the other
history row commands.
EQQM401W THE DB2 HISTORY DATABASE IS NOT AVAILABLE
Explanation: The database that holds the operation data for old occurrences is not available. Possible reasons are:
The database has been stopped or abended.
The table space holding the data has been closed.
|The name specified in the DB2SYSTEM keyword in not correct.
System action: DB2 diagnostic messages are written to the TME 10 OPC EQQMLOG dataset.
User response: Contact your system programmer.
System programmer response: Check the EQQMLOG dataset for DB2 messages and take the actions described in
DB2 documentation.
EQQM402W THE OPC/ESA SUBSYSTEM IS NOT CONNECTED TO A DB2 HISTORY DATABASE
Explanation: When processing the request, TME 10 OPC found that:
The DB2 system specified in the DB2SYS keyword in the OPCOPTS initialization statement could not be
connected or,
the OPERHISTORY keyword was not specified in the OPCOPTS statement.
System action: If TME 10 OPC tried to connect to a DB2 system, DB2 diagnostic messages are written to the
TME 10 OPC EQQMLOG dataset.
User response: Contact your system programmer.
System programmer response: Check the EQQMLOG for DB2 messages and take the actions described in DB2
documentation.
EQQM403E COULD NOT RETRIEVE REQUIRED DATA. DB2 RETURN CODE IS

DB2RC

Explanation: TME 10 OPC tried to access data in the DB2 history database but failed to do so. The resulting DB2
messages are written to the TME 10 OPC EQQMLOG dataset. The return code is the sqlcode returned by DB2.
System action: DB2 diagnostic messages are written to the EQQMLOG dataset.
User response: Contact your system programmer.
System programmer response: Check the EQQMLOG dataset for DB2 messages and take the action described in
the DB2 documentation.
Chapter 16. EQQMnnn Messages 201