This message is issued if the EVENTS statistics are made active, either by specifying the STATMSG(EVENTS) keyword in the JTOPTS initialization statement or by issuing the modify command, /F subsys,EVESTA=ON.

This message shows the total number of events processed and how many events have been processed since the message was last issued or, if it is the first time it is issued, since the last time the event manager processed the events queue.

The message also contains information about how many events were waiting to be processed each time the queue processing routine was called. The value below the TOTAL heading gives the total number of times that the event queue was emptied. The values below the Qx headings give the number of times that the length of the queue was in a particular interval. For example, Q50 gives the number of times that the queue was between 21 and 50 events.

Event-triggered tracking (ETT) was triggered by an event, but could not add the associated application due to an I/O-error on the application description database.

Event-triggered tracking (ETT) was triggered by an event, but could not add the associated application since the first operation (that is, the operation with the lowest operation number) was not a CPU-operation or a non-z/OS CPU operation and ETT's Job Name Replace option was specified.

Event-triggered tracking (ETT) was triggered by an event, but could not add the associated application since the first operation (that is, the operation with the lowest operation number) had internal predecessor operations, and ETT's Job Name Replace option was specified.

This message is issued if the CP ENQ LOCK statistics are active. This can be done either by specifying the STATMSG(CPLOCK) keyword in the JTOPTS initialization statement or by using the modify command, /F subsys,CPQSTA=ON.

This message shows that HCL Workload Automation for Z tasks have referred to the current plan data since the last message was issued, or if it is the first time it is issued, since the last time the event manager processed the events queue.

This message is issued together with the message EQQE004I. See the explanation for EQQE004I for details about when it is issued.

The message contains information about the use of the current plan data set by one HCL Workload Automation for Z subtask. The descriptions of the column headings in the previous message, EQQE004I, also describe the variables in this message.

This message is issued if the EVENTS statistics are active. This can be done either by specifying the STATMSG(EVENTS) keyword in the JTOPTS initialization statement, or by using the modify command, /F subsys,EVESTA=ON.

This message consists of column headers that describe measured values that are displayed in the message EQQE007I that follows. The measured values contain information about the total number of events processed, how many have been processed since the message was last issued, or, if it is the first time it is issued, since the last time the event manager processed the events queue, and the elapsed time that the event manager needed to process the events.

This message is issued if STATMSG(EVENTS) has been specified in the JTOPTS initialization statement. The message contains information about how the event manager subtask processed one type of event. The descriptions of the column headings in the previous message, EQQE006I, also describe the variables in this message.

This message is issued if the WSA statistics are active. This can be done either by specifying the STATMSG(WSATASK) keyword in the JTOPTS initialization statement, or by using the modify command, /F subsys,WSASTA=ON.

This message shows some statistic information about the operations ready queue list and its handling by the WSA task since it was last issued, or, if it is the first time it is isuued, since the last time the event manager processed the events queue.

The set of variables (R1-R6) gives the number of times that the ready list was found to be within a specific range, each time the WSA task processed it to select a winner operation (one to be submitted). For example, R1=10 means that the ready queue list was found 10 times to contain n operations, where n< 10.

This message is issued together with message EQQE008I. See the explanation for EQQE008I for details about when it is used.

Event-triggered tracking (ETT) was triggered by an event but could not add the associated application because there was no active application description (AD) in the AD database.

HCL Workload Automation for Z was unable to allocate storage needed to build the tables required when adding an application (occurrence) to the current plan.

HCL Workload Automation for Z was unable to add the application because the modify current plan interface detected an error.

Event-triggered tracking (ETT) was triggered by an event but could not add the associated application since the application description database was not open.

Event-triggered tracking (ETT) was unable to track the specified job, even though the specified associated application was successfully added.

Event-triggered tracking (ETT) has detected a triggering event (TRIG) and has added the associated application (ADID) to the current plan.

The event-triggered tracking (ETT) function has been activated from the dialog or has been started during the controller start up process because ETT(YES) is specified on the JTOPTS initialization statement.

The event-triggered tracking (ETT) function has been deactivated due to a dialog request or because the event manager subtask has been requested to terminate.

Event-triggered tracking (ETT) has a job on its list of jobs to be tracked, but the specified job has not been submitted by HCL Workload Automation for Z.

HCL Workload Automation for Z Controller was checking the NOERROR table for an operation having the expanded jcl used for the last run: in this case a step name table (DCLCPR44) should exist to map the original step names and the new step names, but no table was found.

The event manager was unable to change the status of an operation in the current plan.

The event manager could not acquire all resources required for normal operation. The most likely cause of this error is that the subsystem is being stopped but the normal mode manager subtask has not started. It is also possible that the JCL repository data set could not be opened.

This message is issued if the HCL Workload Automation for Z subsystem is being stopped and Event Manager initialization has completed successfully. The message is also issued if the Event Manager has been requested to stop by an operator modify command.

This message is issued if a serious error that prevents normal operation by the Event Manager has been encountered after Event Manager initialization has completed.

Event Manager initialization has completed successfully and the Event Manager is about to start processing.

This message is issued when an operation on a general type workstation has ended in error and the ALERTS initialization statement specifies TYPE(ERROROPER).

This message is issued when a ready operation on a general type workstation has reached its latest start time but has not yet started.

This message is issued when a started operation on a general type workstation has been active longer than its estimated duration multiplied by the feedback limit, divided by 100. For example, if the feedback limit is 200 and the estimated duration is ten minutes, the message is issued if the operation has been active longer than twenty minutes.

The values indicated in this message help you determine the late operation. If you did not specify a job name, a blank value is displayed.

The job is not one that HCL Workload Automation for Z has submitted although it is known to HCL Workload Automation for Z as one that should be tracked. However, because someone submitted the job outside of HCL Workload Automation for Z’s control, the job is not tracked.

The request to create the new resource came from: an SRSTAT command, EQQEVPGM using SRSTAT as input, the EQQUSINS subroutine, the EQQUSIN subroutine, or from the data set triggering function.

The job error code matched the NOERROR definition indicated in the message.

An ALL DEP request was performed from EQQSOPGD panel, the message shows the user ID that originated the request, the TYPE OF SELECTION, the NUMBER OF NESTINGS and the NESTING DETAILS.

The current OPSTAT event definition statement does not define any error code. This information is required if you are setting the error status.

This message is issued when an operation on a computer or printer workstation has ended in error and the ALERTS initialization statement specifies TYPE(ERROROPER). The variable NRC indicates the numeric return code for an end-to-end job. In case the job ends in error, the variable NRC is set to E2E RC = xxxxxxxxxxx. In case the job fails, or the message concerns an MVS job, the variable NRC is set to NO E2E RC.

This message is issued when a job has reached its latest start time but has not yet started.

This message is issued when a job has been active longer than its estimated duration multiplied by the feedback limit, divided by 100. For example, if the feedback limit is 200 and the estimated duration is ten minutes, the message is issued if the job has been active longer than twenty minutes. The feedback limit specified on the JTOPTS initialization statement is used in the calculation.

If the ALERTS initialization statement specifies DURATION, this message is issued when a job or started task has been started by the controller but after 10 minutes has not started to operate yet (for MVS jobs no A2/B2 event has been processed), for FT-jobs the extended status is waiting for submission i.e. no event signaling that the job is started on the agent has been processed.)

HCL Workload Automation for Z job tracking has encountered an add job to JES queue event (A1/B1) for a job whose job name matches job names defined in the current plan. However, none of the operations with this job name has a status that is consistent with an add job to JES queue event; for example, the A1/B1 event was received but the operation has the status Complete or Error. This message indicates that jobs with HCL Workload Automation for Z job names are being submitted by non-HCL Workload Automation for Z functions or by another Z controller.

An invalid user-defined event record has been found in the event manager work queue. The operation specified in the event is a fault-tolerant workstation operation and the new specified status is not valid. As a rule, only C and S are accepted. The S value is not allowed if the operation is running or if it has a recovery job that is running.

The Event Manager has encountered an event for a job whose job name matches an operation defined in the current plan. However, HCL Workload Automation for Z did not submit this job. This message indicates that jobs with HCL Workload Automation for Z job names are being submitted by non-HCL Workload Automation for Z functions.

The Event Manager has received an event for a job on an automatically reporting computer workstation that conflicts with the information already collected for this operation. For example, a job complete event can only occur for a job that has started to execute.

The Event Manager has received a job start event for an operation on an automatically reporting computer workstation. However, this operation has predecessor operations that have not yet been reported complete.

The scheduler changed the status of an operation to Complete but encountered errors when attempting to set the status to Ready for a successor of the complete operation.

The Event Manager was unable to communicate successfully with JES while trying to release a job from hold.

A job that was held by a HCL Workload Automation for Z job tracking exit could not be released from hold because the add job to JES queue event was read by an event reader where the RELDDNAME keyword on the ERDROPTS statement defines a ddname that is not defined as a submit/release ddname for any workstation defined in the current plan.

A job that was held by a HCL Workload Automation for Z job tracking exit could not be released from hold because an error occurred while writing the release command to a submit/release data set.

An invalid user-defined event record has been found on the Event Manager’s work queue. No operation in the current plan data set could be found that matches the operation defined by the event record.

An invalid user-defined event record has been found on the Event Manager’s work queue. No job name has been given, but it is required.

There is no default for the ACT operand, which therefore must be specified (to be sure that a so important function as the job submission is not activated or deactivated incidentally).

It is required that the person who issues the JSUACT command has the proper RACF® authorization.

An invalid event record originated from a fault-tolerant workstation has been found on the Event Manager work queue. No occurrence in the current plan data set could be found that matches the occurrence token defined by the event record.

An invalid event record originated from a fault-tolerant workstation has been found on the Event Manager work queue. The operation that the event record refers to is in a status that is not compatible with the event record.

The Event Manager’s work queue contains an incorrect submit event. No operation in the current plan data set matches the operation defined by the event record. This submit event record is created for work being scheduled on one of the systems in this controller product configuration by another controller having the same name.

An invalid event record has been found on the Event Manager’s work queue. The most likely error is that the last 4 bytes of the record do not contain the HCL Workload Automation for Z character string EQQ1. It is also possible that the first 3 characters of the job number field do not contain the character string JOB.

An invalid event queue entry has been found on the Event Manager’s work queue. The Event Manager could not determine the origin of the event. Each event must come from one of sixteen possible event data sets on each HCL Workload Automation for Z node. In the current event queue entry, either the event data set number or the HCL Workload Automation for Z node number is not valid.

An invalid user-defined event record has been found on the Event Manager’s work queue. The workstation name in the current event record does not match any workstation definition in the current plan data set.

An invalid user-defined event record has been found on the Event Manager’s work queue. Workstations referenced by user-defined event records must be automatically reporting workstations. The current workstation does not have this attribute.

The EQQEVPGM program could not open the data set referenced by the SYSIN DD statement, the statement was not defined correctly, or no SYSIN DD statement was present.

The EQQEVPGM program found one or more errors during initialization.

The EQQEVPGM program has finished processing. No errors were found during execution.

A severe error occurred during execution of the EQQEVPGM program.

The EQQEVPGM program has been correctly initialized and is about to start generating events.

The SUBSYS keyword contains an invalid subsystem name.

An error occurred when attempting to send an event to a HCL Workload Automation for Z subsystem.

An error occurred when attempting to send an event to a HCL Workload Automation for Z subsystem.

The EQQEVPGM program found one or more incorrectly coded event definition statements.

The special resource name defined by the SRSTAT event definition statement is too long.

The current SRSTAT event definition statement does not define any special resource name. This name is required.

In order to change a special resource for a HCL Workload Automation for Z subsystem, update authority to the SR resource is necessary. You do not have this authority.

In order to create an operation or workstation event for a HCL Workload Automation for Z subsystem, update authority to the RL resource is necessary. You do not have this authority.

The current OPSTAT or WSSTAT event definition statement does not define any workstation name, application description, or job name. This information is required.

The only valid values for CREATE, AVAIL, and the new availability value of LIFESPAN are either YES, NO, and RESET or abbreviations of YES, NO, and RESET.

This message is issued when a HCL Workload Automation for Z TSO command has failed due to an error when communicating with the HCL Workload Automation for Z subsystem.

This message is issued when a HCL Workload Automation for Z TSO command has failed due to an error when communicating with the HCL Workload Automation for Z subsystem.

A HCL Workload Automation for Z TSO command or EQQEVPGM has failed because the HCL Workload Automation for Z subsystem SUBSYS has not been initialized. HCL Workload Automation for Z subsystems are initialized during a z/OS IPL.

This message is issued when a HCL Workload Automation for Z TSO command has failed because the subsystem that was referenced is not a HCL Workload Automation for Z subsystem.

An SRSTAT request to update a special resource specified for subsystem SUBSYS failed because the user making the request was not authorized to update the resource.

The value specified for the resource data set keyword—RESDS was not valid. The keyword value must be specified as CP or JS.

The resource data set keyword—RESDS was not specified.

In order to request a backup of a HCL Workload Automation for Z resource data set, update authority to the BKP fixed resource is required. You do not have this authority.

An OPSTAT requests to update an operation in subsystem SUBSYS failed because the user making the request was not authorized to update the SUBRES subresource.

A WSSTAT request to update the status of workstation WSNAME in subsystem SUBSYS failed because the user making the request was not authorized to update the RL.WSSTAT subresource.

The current WSSTAT statement does not define a workstation name (WSNAME) or a destination ID (DESTINATION). At lease one of WSNAME or DESTINATION must be specified. Both can be specified.

An invalid user-defined event record has been found on the Event Manager's work queue. An OPSTAT event definition statement defined an OPCTOKEN value that is not consistent with some or all of the values specified in the ADID, IA, JOBNAME, AND OPNUM keywords. The operation cannot be identified by the scheduler.

An invalid user-defined event record has been found on the Event Manager's work queue. An OPSTAT event definition statement specified a new status of SQ or SS, but the current operation status is not started (S), ready (R), or arriving (A).

An invalid user-defined event record has been found on the Event Manager's work queue. An event generated by WSSTAT or EQQUSINW specified a workstation that is not a computer, or WTO workstation.

An invalid user-defined event record has been found on the Event Manager's work queue. An WSSTAT event definition statement specified a workstation that did not match the destination specified in the event.

An invalid user-defined event record has been found on the Event Manager's work queue. An WSSTAT event definition statement specified a destination which was not specified in the ROUTOPTS initialization statement.

The current WSSTAT event definition statement does not define any status. This keyword is required.

An invalid user-defined event record has been found on the Event Manager's work queue. An OPSTAT event definition statement defined a TOKEN value that does not match any operation in the current plan. The operation cannot be identified by the scheduler.

An invalid user-defined event record has been found on the Event Manager's work queue. An OPSTAT event definition statement specifies a new status Q for an operation which has a current status SS. This is not allowed.

An invalid user-defined event record has been found on the Event Manager's work queue. A WSSTAT event definition statement specified an alternative workstation that did not exist.

A WSSTAT event definition statement specified an alternative workstation that was the same as the current workstation.

The only valid values for the QUANTITY and DEVIATION keywords are KEEP, RESET or a numeric value.

This message indicates that handshake processing, the frequency for which is determined by the PULSE keyword of the ROUTOPTS statement, has terminated for the indicated Tracker system. When handshake processing is in use, each connected Tracker system sends an identification (ID) event to the controller at the specified interval. If the controller detects that a Tracker system has missed two consecutive PULSE intervals, this message is issued. SUBS is the name of the Tracker (the subsystem name for z/OS tracker). DEST is the destination for this system, as defined in the ROUTOPTS statement.

This message is issued for reporting purposes on the controller message log, EQQMLOG, when the ROUTOPTS PULSE processing is active for Tracker systems on HCL Workload Automation for Z release 3 level or higher. The message indicates that the FUNC subtask in the SUBS subsystem on the z/OS system represented in HCL Workload Automation for Z by the DEST destination has abnormally terminated.

Authority checking for subresource SUBRES is specified in the AUTHDEF statement for subsystem SUBSYS. A valid subresource name cannot be built for protection of the operation when keyword KEYW is omitted. When EQQEVPGM processes a TSO command, for example, OPINFO, OPSTAT, JSUACT or WSSTAT, it checks the authority of the requestor analyzing the contents of AUTHDEF statements of the scheduler. To do this check it also necessary that a certain keyword KEYW should be specified in the previous TSO statement.

The controller is running with DSTTASK(YES), that is, SYSOUT retrieval is done via the Data Store, but a minimum of one tracker is running in an environment where the Data Store is not active.

An invalid event record originated from a fault-tolerant workstation has been found on the Event Manager work queue. No operation in the current plan data set could be found that matches the operation defined by the event record.

An invalid event record originated from a fault-tolerant workstation has been found on the Event Manager work queue. No workstation in the current plan data set could be found that matches the workstation defined by the event record.

An event record, originating from a fault-tolerant workstation, indicates that an operation started before predecessors are completed or resources allocated. This error is probably produced by dependencies added after the job was started on the agent.

An event record, originating from a fault-tolerant workstation, reports a status transition that is not compatible with the actual operation status. This error is probably produced by setting the status of running jobs manually or by operations already set out of sequence.

An event record, originating from a WSSTAT command, tried to set a status of a fault-tolerant workstation to Failed, which is not compatible with the actual workstation type.

The submission of operation OPERATION in occurrence APPL with Input Arrival ARRTIME failed while the engine was sending the script for the operation to the distributed agent.

An event record, originating from a WSSTAT command, tried to set alternate workstation for a fault-tolerant workstation. This is not compatible with the actual workstation type.

An event record, originating from a WSSTAT command, tried to concurrently use the STATUS, CMD and MANAGES keywords. This is not possible. You can only use one of the three.

An event record, originating from a WSSTAT command, used keyword CMD (command) to set STATUS or LINK, when the workstation is not a fault-tolerant workstation.

An event record, originating from a WSSTAT command, used the MANAGES keyword to change the domain, when the workstation is not a fault-tolerant workstation.

An invalid event record coming from a fault-tolerant workstation was found in the work queue of the Event Manager. No recovery information could be found in the current plan record 24 that matches the operation defined by the event record.

An event record for changing the workstation status, tried to assign a fault-tolerant workstation as alternate workstation and to reroute operations with the REROUTE value.

The keyword TYPE on command JSUACT contains a wrong value. The possible values are H for Host, F for FTW and B for both environments.

The request requires an operation in error status with error code OSEQ to change status. There are restrictions as to how this can be done when the operation has uncompleted predecessors.

HCL Workload Automation for Z submitted an operation with a system automation command and received a message back from system automation. The operation is identified by the owning application ID, operation input arrival date and time, and operation number.

The user has requested a bulk discovery when the monitoring task is not active.

The user has requested a new bulk discovery while a bulk discovery is currently running.

The user has requested a bulk discovery but a planning activity is currently in progress.

At job-end time, the indicated step dependency is not evaluated yet, because the event writer did not receive the step-end event.

A WSSTAT command was issued to set a workstation as offline, but the alternate workstation specified is not a HCL Workload Automation Agent workstation.

This situation occurs only when the latest start time is postponed by a DP batch extend or replan.

The Controller (Event Manager task) ignored the event identified by EXITREC because it was related to a virtual workstation, but the tracker that originated the event does not support virtual workstations, so that not all the needed information were provided. The event EXITREC is an IJ0 event sent by tracker to controller after a workstation synchronize request or submission request found out of sequence. When the workstation is virtual, the name of the workstation is insufficient because the event must also contain the tracker destination.

The scheduler changed from started to interrupted the status of the indicated operation. The reason is that this operation has conditional successors already completed, started, ended in error, or suppressed by condition.

The scheduler did not reset to arriving the indicated operation, even if the related error code matches a value specified through the ERRRES parameter in the JTOPTS statement. The reason is that this operation has conditional successors already completed, started, ended in error, or suppressed by condition.

The operation specified in the message was marked with the Unexpected RC flag because its status ST does not match any of those specified in the conditions of its conditional successors. This means that no possible path for progression exists. The status settings that can cause this message are E (Error) and C (Complete).

The operation specified in the message was marked with the Unexpected RC flag because its return code or status ST does not match those specified in step level conditional dependency associated to the indicated operation's step. This means that no possible path for progression can exist.

You set the HTTPOPTS OUTPUTCOLLECTOR keyword to YES to collect the joblog for jobs that run on z-centric and dynamic agents and write it to JES. When this feature is active, the event manager writes in the DDNAME data set an event for each joblog that must be collected by the output collector. An error occurred opening the data set so the event manager cannot use the data set to communicate with the output collector.

The DDNAME data set use has reached the percentage indicated by the value of PERCENT. Some events might be lost.

The DDNAME data set is full. Some events might be lost.

See message text.

See message text.

See message text.

See message text.

See message text.

See message text.

See message text.

See message text, where ACTION can be Set to Error or Completed.

See message text.

See message text.

The job submit activate/deactivate command has been ignored because the controller normal mode manager (NMM) task has terminated.

The job submit activate command has been ignored because the job submit function is already active and enabled for service.

The job submit deactivate command has been ignored because the job submit function is already inactive and disabled for service.

The job submit activate command has been accepted and executed.

The job submit deactivate command has been accepted and executed.

You tried to submit an activate or deactivate job submission on FTW with TSO command JSUACT when end-to-end feature is not active.

A time discrepancy equal to or less than a minute has been detected in the reader queue time (JMRENTRY) stored in JMR block, therefore the events for the job do not match.

In workstation WSNAME, the number of jobs indicated in this message exceeded the long time on input queue because they were started but not run (A2 event not received). This number of jobs exceeds the value set in JTOPTS(MAXSTNUM), therefore this message is issued.

On the indicated system, the system time was changed. HCL Workload Automation for Z generated an event to change its GMT offset through the tracker.

The Event Manager has received an event for a restart and cleanup process that does not match the token used in the original dialog request.

The Event Manager has received an event for a restart and cleanup process for which no matching DOA can be found.

The ENV parameter specifies if the scheduling environment is unavailable at the JESplex level only or throughout the entire sysplex. SID reports the sysplex identification number where this event occurred.

The ENV parameter specifies if the scheduling environment is unavailable at the JESplex level only or throughout the entire sysplex. SID reports the sysplex identification number where this event occurred.

The ENV parameter specifies if the scheduling environment is unavailable at the JESplex level only or throughout the entire Sysplex. SID reports the Sysplex identification number where this event occurred.

A WLM Service Definition has been successfully installed on the Sysplex identified by SID (it is the value specified in OPCOPTS SYSPLEXID tracker parameter).

A WLM VARY POLICY command has been successfully completed on the sysplex identified by SID (it is the value specified in OPCOPTS SYSPLEXID tracker parameter).

Avoid using special resources with the maximum limit function active and scheduling environment, because retrying an operation waiting for the scheduling environment increases the usage counter each time the operation becomes Ready again. The scheduling environment availability check is done by the tracker, so the operation changes status from Ready to Started and from Started to Ready again if the scheduling environment is not available.

The Event Manager has received an event for a restart and cleanup process, but no matching DOA can be found because the operation results completed.

The Event Manager has partially updated the deadline. A complete update was not possible, because the value would have been 00.00 in the same day as IA, while allowed values for deadline are 00.01-24.00. The value has been set to 00.01.

See message text.

See message text.