EQQDF01 - EQQDF18
EQQDF01I
THE DB FILLER TASK HAS STARTED.
The DB filler task has successfully completed initialization.
The DB filler task processing continues.
None.
EQQDF02I
THE DB FILLER TASK HAS ENDED.
The DB filler task has ended.
Processing continues.
None.
EQQDF03E
THE DB FILLER TASK FAILED TO INITIALIZE THE C PROCESS.
An error occurred while attaching a task to run the C code as a z/OS executable program: an invocation to the BPX1ATM callable service failed.
The DB filler task initialization fails.
Contact Software Support for assistance.
EQQDF04I
CURRENT PLAN BULK DUMP HAS STARTED.
A current plan bulk dump has started.
None.
None.
EQQDF05I
CURRENT PLAN BULK DUMP HAS ENDED.
A current plan bulk dump has ended.
None.
None.
EQQDF06E
THE DB FILLER TASK HAS ENDED FINDING AN ERROR.
The DB filler task has ended without having been requested to terminate.
Review earlier messages in the message log to identify the cause of
the error, take corrective action, then issue the MODIFY command /F
procname,S=DBF to restart the DB filler task. If the error persists,
stop and restart the Z controller.
Review earlier messages in the message log to determine the reason for this message.
EQQDF07W
PERMANENT DATA ABOUT MIRRORING HAS BEEN RESET. RESTART DB FILLER TASK IF NEEDED.
The permanent information stored in the AD record about mirroring CP
data has been reset; the DB filler task has been stopped. If needed, restart the DB filler
by issuing the MODIFY command /F procname,S=DBF.
The DB filler task has stopped.
If needed, restart the DB filler by issuing the MODIFY command
/F procname,S=DBF.
EQQDF08E
DB FILLER TASK EXCEPTION: ERRMSG. CONTEXT: CONTEXT.
- DBFILLER
- The error message is self-explanatory.
- WEBSOCKET
- Refer to the WebSocket standard protocol.
- SOCKET
- Refer to the z/OS Communications Server: IP Sockets Application Programming Interface Guide and Reference manual.
- GSKIT
- Refer to the z/OS Cryptographic Services System SSL Programming manual.
The DB filler task stops.
Based on the error message, resolve the issue and restart the controller.
EQQDF09W
DB FILLER TASK EXCEPTION: ERRMSG. CONTEXT: CONTEXT.
- DBFILLER
- The error message is self-explanatory.
- WEBSOCKET
- Refer to the WebSocket standard protocol.
- SOCKET
- Refer to the z/OS Communications Server: IP Sockets Application Programming Interface Guide and Reference manual.
- GSKIT
- Refer to the z/OS Cryptographic Services System SSL Programming manual.
The DB filler task automatically attempts a recovery process.
Based on the error message, check if there is a connection problem that must be resolved.
EQQDF10I
DB FILLER TASK IS ATTEMPTING TO CONNECT TO THE FEDERATOR.
The DB filler task is attempting to connect with the Federator.
None.
EQQDF11I
DB FILLER TASK HAS SUCCESSFULLY CONNECTED TO THE FEDERATOR.
The DB filler task successfully connected with the Federator.
None.
EQQDF12I
DB FILLER TASK IS ACTIVE AND OPERATIONAL.
The DB filler task is up and running.
None.
EQQDF13W
DB FILLER TASK IS ACTIVE BUT IN RECOVERY MODE DUE TO AN ERROR.
The DB filler task is in recovery mode, because there are connection problems or there is not any current plan. If present, see messages EQQDF08E and EQQDF09W to learn the cause of the problem.
None.
EQQDF14E
DB FILLER TASK HAS IGNORED THE FOLLOWING QUEUE ELEMENT: DQE
The DB filler task received an invalid queue element. A queue element did not contain the correct eye catcher or version number.
Save the HCL Workload Automation for Z message log and contact the Software Support.
Contact your system programmer.
EQQDF15W
PERCENT % OF INTERNAL QUEUES OF DB FILLER IN USE (MAX CAPACITY IS MAXNUM)
The DB filler queues have reached the threshold indicated by the percentage PERCENT, meaning that they are close to or have reached their maximum capacity (MAXNUM).
For details, refer to message EQQDF16W.
EQQDF16W
MAX QUEUE SIZE (MAXNUM) REACHED IN DB FILLER INTERNAL QUEUES. A NEW BULK OR PARTIAL BULK MIGHT START.
The internal queues of the DB filler have reached their maximum size, which is MAXNUM. Updates to the current plan are not taken into account until the queues are processed. After the internal queues are processed, a new bulk or partial bulk processing cycle might start.
For details, refer to message EQQDF17I.
EQQDF17I
CURRENT PLAN PARTIAL BULK DUMP HAS STARTED.
A current plan partial bulk dump has started. This process includes only the records of the events that were discarded, either during a recovery procedure or because the internal queues reached their maximum size.
If this happens frequently, it might indicate that you have a very large CP or there are connection problems between the Z controller and Federator.
EQQDF18I
CURRENT PLAN PARTIAL BULK DUMP HAS ENDED.
A current plan partial bulk dump has ended.
None.