EQQF000 - EQQF018
EQQF000E
DATA ROUTER TASK HAS IGNORED AN INVALID QUEUE ELEMENT: DQE.
A queue element did not contain the correct eye catcher or version number.
The data router task does not process the invalid element, but continues normal processing.
Save the HCL Workload Automation for Z message log and contact the Software Support.
Contact your system programmer.
EQQF001I
DATA ROUTER TASK INITIALIZATION IS COMPLETE.
The data router task has successfully completed initialization.
Data router task processing starts.
None.
EQQF002E
DATA ROUTER TASK INITIALIZATION FAILED.
The data router task could not acquire the resources required for normal operation.
Data router task processing is terminated.
Correct all errors and restart the data router task.
Contact your system programmer.
Review previous messages in the HCL Workload Automation for Z message log.
EQQF003E
MEMBER MEMBER IS DEFINED AS A DESTINATION IN ROUTOPTS BUT IS STARTED AS A STANDBY SYSTEM.
An XCF member has joined the same XCF group as the controller. This member was defined as a tracker in the ROUTOPTS but has been started as a HCL Workload Automation for Z standby subsystem.
HCL Workload Automation for Z does not recognize the joined standby member as a destination. No communication takes place between the controller and the standby member.
Restart the standby system as a tracker or update the controller ROUTOPTS statement.
Contact your system programmer.
Check the ROUTOPTS initialization statement and the initialization statement defined for the member.
EQQF004E
DATA ROUTER TASK ABENDED WHEN PROCESSING THE FOLLOWING QUEUE ELEMENT DQE.
An abend prevented the data router task from processing a queue element.
z/OS recovery/termination is requested to generate a dump. The data router task attempts to continue normal processing.
Save the message log and dump data sets and contact the Software Support.
Contact your system programmer.
Review the HCL Workload Automation for Z message log data set, the EQQDUMP data set, and the SYSMDUMP data set to determine the cause of the problem.
EQQF005E
DATA ROUTER TASK QUEUE POINTERS ARE DESTROYED, RTRQ IS LOST.
The data router task abended while processing elements on RTRQ because the queue chaining is invalid.
z/OS recovery/termination is requested to generate a dump. All elements on RTRQ are skipped, but the data router task attempts to continue normal processing.
Save the message log and dump data sets and contact the Software Support.
Review the HCL Workload Automation for Z message log data set, the EQQDUMP data set, and the SYSMDUMP data set to determine the cause of the problem.
EQQF006I
UNKNOWN XCF MEMBER MEMBER HAS JOINED THE GROUP. IT IS IGNORED.
A member that is not defined in ROUTOPTS has joined the XCF group.
The controller ignores the joined member. No workload or event communication between the controller and the tracker takes place.
Verify that the tracker system has been defined with an XCF member name that corresponds to the definition in ROUTOPTS. Add the member name to ROUTOPTS and restart the controller.
Check the XCFOPTS initialization statement of the HCL Workload Automation for Z tracker system and check the ROUTOPTS initialization statement of the controller.
EQQF007I
XCF MEMBER MEMBER HAS JOINED THE GROUP. THE DESTINATION WILL BE REPORTED ACTIVE.
A HCL Workload Automation for Z tracker system has joined the same XCF group as the controller. The member is defined as an XCF destination in the ROUTOPTS initialization statement.
The controller reports the destination as active. Work can be scheduled at workstations defining this destination.
None.
EQQF008I
XCF MEMBER MEMBER HAS JOINED THE GROUP AS STANDBY FOR THE CONTROLLER.
A HCL Workload Automation for Z standby subsystem has joined the same group as the controller.
Controller processing continues as normal.
None.
EQQF009I
ADAPTIVE PACING ON EVENT INFLOW MODE.
- ACTIVATED
- The data router has detected that the maximum number of queue elements on the event manager queue (MGRQ) were already in use when the data router task attempted to add incoming events to the MGRQ. The data router task has posted each locally attached event reader task and event writer task (when EWSEQNO(n)), to stop reading from the event data sets or adding to the DRTQ. The data router task has also built and sent a DQE request (type RTQ) to each remote (NCF, TCP/IP, and/or XCF) linked tracker, where the remote data router task posts each attached event reader task and event writer task (when EWSEQNO(n)), to stop reading from the event data sets or adding to the DRTQ.
- DEACTIVATED
- The data router task has detected that the event manager has processed all events on the event manager queue (MGRQ), so the data router task has posted each locally attached event reader task and event writer task (when EWSEQNO(n)), to start reading from the event data sets or adding to the DRTQ. The data router task has also built and sent a DQE request (type RTQ) to each remote (NCF, TCP/IP, and/or XCF) linked tracker, where the remote data router task posts each attached event reader task and event writer task (when EWSEQNO(n)), to start reading from the event data sets or adding to the DRTQ.
HCL Workload Automation for Z processing continues.
None. This message is for information only.
EQQF010I
INVALID RETURN CODE RETC FROM EQQUX009 IS IGNORED.
User exit EQQUX009 passed an invalid return code back to the data router task. The return code is ignored.
Normal processing continues. The return code is treated as return code 0.
Investigate why EQQUX009 returned an invalid return code.
Inform your system programmer.
EQQF011E
THE OPERATION INITIALIZATION EXIT USRX HAS ABENDED WHILE PROCESSING OPERATION OPN IN APPLICATION APPL WITH IA IA SCHEDULED ON WORKSTATION WSNAME. THE EXIT IS MARKED AS NOT USABLE.
The exit abended while processing. HCL Workload Automation for Z does not try to call it again unless the data router task is restarted. The exit is flagged as not executable.
The current operation status is set according to what is specified in the SUBFAILACTION JTOPTS parameter.
Correct all errors in the exit and restart the data router task.
EQQF012I
PROCESSING RETURN CODE RETC FROM EQQUX009.
User exit EQQUX009 passed a return code, RETC, that is not 0. The data router task processes the return codes and continues normal processing.
- 4
- The current operation status is set according to the value set in the SUBFAILACTION keyword of the JTOPTS initialization statement.
- 8
- The operation status is set according to the value set in the SUBFAILACTION keyword of the JTOPTS initialization statement. All workstations specifying the destination are set to offline status.
Investigate why EQQUX009 returned the return code.
Inform your system programmer.
EQQF013I
EXIT EQQUX009 IS NOT LOADED OR HAS BEEN DISABLED.
User exit EQQUX009 has not been loaded or has abended previously. The operations scheduled to run on a workstation that specifies a user-defined destination are routed.
The operation status is set according to the value specified in the SUBFAILACTION keyword of the JTOPTS initialization parameter.
Investigate why EQQUX009 is not loaded. If a previous abend caused the exit to be disabled, correct the error and stop/start the HCL Workload Automation for Z subsystem to get the exit reloaded.
Issue a WSSTAT command, or use the workstation dialog, to vary the destination workstations offline.
EQQF014E
THE EXTERNAL ROUTER QUEUE IS FULL. USER DESTINATION WILL BE SET TO OFFLINE STATUS.
The external router queue is full. HCL Workload Automation for Z sets the destination to offline status and sets the corresponding operation to the status specified in the SUBFAILACTION keyword of the JTOPTS initialization statement.
The current operation status is set according to what is specified in the SUBFAILACTION JTOPTS parameter.
Investigate why the EQQUX009 exit is not processing.
EQQF015I
XCF TYPE MEMBER MEMBER HAS LEFT THE GROUP. REASON: REASON.
The XCF link to TYPE with member name MEMBER has been disconnected. The REASON is either that the linked HCL Workload Automation for Z address space terminated or the entire scheduler system terminated.
The transmission of data (such as event records) through the XCF link is postponed. The transmission of data resumes when the XCF member rejoins the group.
This is a HCL Workload Automation for Z informational message.
- The TYPE indicated CONTROLLER and message EQQW070I was also issued when the controller was restarted, you should consider increasing the size of the tracker's event data set.
- The TYPE indicated TRACKER and message EQQZ035I was also issued when the tracker was restarted, you should consider increasing the size of the ECSA buffer (SYS1.PARMLIB(IEFSSNxx)).
Contact your system programmer.
If this message is not expected, review the message log (EQQMLOG) and the SYSLOG of the linked HCL Workload Automation for Z MEMBER to determine the cause of the outage.
EQQF016E
THE TCP/IP TASK QUEUE IS FULL. THE DESTINATION WILL BE SET TO OFFLINE STATUS.
The TCP/IP queue is full.
The scheduler sets the corresponding operation to the status specified in the SUBFAILACTION keyword of the JTOPTS initialization statement.
Try to find out why the TCP/IP task is not processing.
EQQF017E
THE HTTP CLIENT TASK QUEUE IS FULL. THE DESTINATION WILL BE SET TO OFFLINE STATUS.
The HTTP client task is full.
The scheduler sets the corresponding operation to the status specified in the SUBFAILACTION keyword of the JTOPTS initialization statement.
Try to find out why the HTTP client task is not processing.
EQQF018E
DATA ROUTER TASK HAS IGNORED THE FOLLOWING DQE ELEMENT BECAUSE IT CONTAINS THE INVALID DESTINATION DEST: DQE.
A queue element contained a destination not present in the destination table.
The data router task does not process the invalid element, but continues normal processing.
Save the HCL Workload Automation for Z message log and contact the Customer Support.
Check your ROUTOPTS statements for the missing destination.