EQQE000 - EQQE309

EQQE000I

TOTAL NUMBER OF EVENTS PROCESSED BY THE EVENT MANAGER TASK IS: NUMEV NUMBER OF EVENTS SINCE THE PREVIOUS MESSAGE IS: NEWEV EVENT MANAGER QUEUE LENGTH STATISTICS FOLLOW: TOTAL Q1 Q2 Q5 Q10 Q20 Q50 Q100 >100 CALLSQ1Q2Q3Q4 Q5Q6Q7Q8

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.

Once activated, this message is regularly issued by the event manager subtask, until it is deactivated. The interval between two messages is calculated as follows:
  • If STATIM is nonzero (in the initial parm or by modify command) the message is issued approximately every n minutes (where n is the STATIM value). If no events have been processed in an interval, then no messages will be issued for that interval.
  • Otherwise, if EVELIM is nonzero (in the initial parm or by modify command), the message is issued approximately every n events (where n is the EVELIM value).
  • Otherwise, the message is issued approximately every n events, where n is half the JTOPTS BACKUP keyword value (default BACKUP is 400).

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.

Normal HCL Workload Automation for Z processing continues.

None.

EQQE001E

ETT FAILED TO ADD ADID FOR TRIGGERING EVENT TRIG I/O ERROR READING AD DATA BASE

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.

The associated application was not added by ETT, but ETT processing continues normally.

Analyze the HCL Workload Automation for Z message log to determine the cause of the error, correct the error and retry. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference, "Problem analysis procedures" section, sub-section "Information needed for all problems".

Contact your system programmer.

Review previous messages in the HCL Workload Automation for Z message log data set to determine the cause of the error.

EQQE002E

ETT FAILED TO ADD ADID FOR TRIGGERING EVENT TRIG FIRST OPERATION NOT ON MVS CPU WS, JOBNAME CANNOT BE REPLACED

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.

The associated application was not added by ETT, but ETT processing continues normally.

Correct the ETT criteria table or the AD database, or both, or get the CPU workstation for z/OS systems into the control plan. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference, "Problem analysis procedures" section, sub-section "Information needed for all problems".

If the Job Name Replace option is used, check the application description (AD) database to make sure that the first operation in the application to be added is a z/OS CPU-operation. Or, check the ETT criteria table to make sure that the correct Job Name Replace option was specified. Or, check that the CPU workstation for z/OS systems is part of the control plan since it might have been added to the workstation database after a new control plan was created.

EQQE003E

ETT FAILED TO ADD ADID FOR TRIGGERING EVENT TRIG FIRST OPERATION HAS PREDECESSORS, JOBNAME CANNOT BE REPLACED

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.

The associated application was not added by ETT, but ETT processing continues normally.

Correct the ETT criteria table or the AD database, or both or get the CPU workstation for z/OS systems into the control plan. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference, "Problem analysis procedures" section, sub-section "Information needed for all problems".

Check the application description (AD) database to make sure that the first operation in the application to be added does not have any internal predecessor operations. Or, check the ETT criteria table to make sure that the correct Job Name Replace option was specified.

EQQE004I

CP ENQ LOCK STATISTICS SINCE PREVIOUS MESSAGE FOLLOW: NAME NEXCL NSHRD THELD TWAIT AHELD AWAIT

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.

Once activated, this messages is regularly issued by the event manager subtask, until it is deactivated. The interval between two messages is calculated as follows:
  • If STATIM is nonzero (in the initial parm or by modify command) the message is issued approximately every n minutes (where n is the STATIM value), if any events have been processed.
  • Otherwise, if EVELIM is nonzero (in the initial parm or by modify command), the message is issued approximately every n events (where n is the EVELIM value).
  • Otherwise, the message is issued approximately every n events, where n is half the JTOPTS BACKUP keyword value (default BACKUP is 400).

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.

The message consists of column headers that describe data indicating how often and in what way the current plan data set has been referenced. The data values are displayed in the message EQQE005I. The values for each heading are:
NAME
The name of the HCL Workload Automation for Z task for which data was gathered.
NEXCL
The number of times that the task acquired exclusive use of the current plan.
NSHRD
The number of times that the task acquired shared use of the current plan.
THELD
The total amount of time, in seconds, that the task was using the current plan.
TWAIT
The total amount of time, in seconds, that the task was waiting to use the current plan.
AHELD
The average amount of time, in seconds, that the task was using the current plan.
AWAIT
The average amount of time, in seconds, that the task was waiting to use the current plan.

Normal HCL Workload Automation for Z processing continues.

None.

EQQE005I

NAMENEXCLNSHRDTHELD TWAITAHELDAWAIT

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.

Normal HCL Workload Automation for Z processing continues.

None.

EQQE006I

EVENT MANAGER EVENT TYPE STATISTICS FOLLOW: TYPE NTOT NNEW TTOT TNEW TAVG NAVG NSUS

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.

Once activated, this message is regularly issued by the event manager subtask, until it is deactivated. The interval between two messages is calculated as follows:
  • If STATIM is nonzero (in the initial parm or by modify command) the message is issued approximately every n minutes (where n is the STATIM value), if any events have been processed.
  • Otherwise, if EVELIM is nonzero (in the initial parm or by modify command), the message is issued approximately every n events (where n is the EVELIM value).
  • Otherwise, the message is issued approximately every n events, where n is half the JTOPTS BACKUP keyword value (default BACKUP is 400).

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.

The values for each heading are:
TYPE
The event type for which data was gathered.
TTOT
The total number of events of this type.
NNEW
The number of events of this type since the last message.
TTOT
The total time, in seconds, used to process this event type.
TNEW
The total time, in seconds, used to process this event type since the last message.
TAVG
The average time, in seconds, used to process an event of this type.
NAVG
The average time, in seconds, used to process an event of this type since the last message.
NSUS
The number of times that the event manager could not immediately process an event of this type.
Valid values in the TYPE column are:
ALL
This line is a total line for all event types.
1
Reader events.
2
Job start events.
3S
Step end events.
3J
Job end events.
3P
Job on output queue events.
4
Data Set print events.
5
Job purge events.
USER
User generated event, EQQUSINT program or the OPSTAT command.
OTHR
Other events.
FT
Events related to scheduling end-to-end with fault tolerance capabilities.
ZCEN
Events related to scheduling end-to-end with z-centric capabilities.

Normal HCL Workload Automation for Z processing continues.

None.

EQQE007I

TYPENTOTNNEWTTOT TNEWTAVGNAVGNSUS

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.

Normal HCL Workload Automation for Z processing continues.

None.

EQQE008I

TYPE08 Q10Q100Q1000Q5000Q10000>10000 R1R2R3R4R5R6

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.

Once activated, this message is regularly issued by the event manager subtask, until it is deactivated. The interval between two messages is calculated as follows:
  • If STATIM is nonzero (in the initial parm or by modify command) the message is issued approximately every n minutes (where n is the STATIM value), if any events have been processed.
  • Otherwise, if EVELIM is nonzero (in the initial parm or by modify command), the message is issued approximately every n events (where n is the EVELIM value).
  • Otherwise, the message is issued approximately every n events, where n is half the JTOPTS BACKUP keyword value (default BACKUP is 400).

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.

Normal HCL Workload Automation for Z processing continues.

None.

EQQE009I

TYPE09VALUE09

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

The meanings of VALUE09 are as follows:
V1
Size of the ready list queue when the message is issued
V2
Number of operations whose status changed to ready (R, *, or A) since the last message
V3
Number of operations whose status changed to started since the last message
V4
Number of operations whose status changed to completed since the last message
V5
Number of times the WSA task was called to select a winner operation since the last message
V6
Number of times the JS VSAM was accessed to read JCL since the last message
V7
Number of times the JOBLIB PDS was accessed to read JCL since the last message
V8
Number of times the User Exit 001 was called since the last message
V9
Number of times the User Exit 002 was called since the last message

Normal HCL Workload Automation for Z processing continues.

None.

EQQE011E

ETT FAILED TO ADD ADID FOR TRIGGERING EVENT TRIG NO ACTIVE APPLICATION DESCRIPTION IN AD DATABASE

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.

The associated application was not added by ETT, but ETT processing continues normally.

Correct the ETT criteria table or the AD database.

Check the ETT criteria to make sure that the triggering event identifies an active application description.

EQQE012E

ETT FAILED TO ADD ADID FOR TRIGGERING EVENT TRIG UNABLE TO ALLOCATE NECESSARY STORAGE

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.

The associated application was not added by event-triggered tracking (ETT), but ETT processing continues normally.

Increase the region for the HCL Workload Automation for Z started task.

Contact your system programmer.

Check the region size allocated to the HCL Workload Automation for Z started task.

EQQE013E

ETT FAILED TO ADD ADID FOR TRIGGERING EVENT TRIG ERROR DETECTED BY MODIFY CURRENT PLAN INTERFACE

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

The associated application was not added by event-triggered tracking (ETT), but ETT processing continues normally.

Save the message log data set containing these error messages and contact the Software Support.

Contact your system programmer.

Check the HCL Workload Automation for Z message log data for EQQMxxx messages (that is, the Modify Current Plan messages) preceding this message. These messages give the exact reason why the application could not be added.

EQQE014E

ETT FAILED TO ADD ADID FOR TRIGGERING EVENT TRIG AD DATABASE NOT OPEN

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

The associated application was not added by ETT, but ETT processing continues normally.

Save the message log data set containing these error messages and contact the Software Support. Analyze the HCL Workload Automation for Z message log data set containing these error messages to determine the cause of the error, correct the error and retry. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference, "Problem analysis procedures" section.

This is a HCL Workload Automation for Z internal error.

EQQE015W

ETT CANNOT TRACK JOB JOB EVEN THOUGH APPLICATION APPL HAS BEEN ADDED

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

The job that triggered the addition of application APPL is not tracked by HCL Workload Automation for Z. ETT processing continues.

Review the tracking options and correct if in error.

The track keyword of the job tracking option statement has most likely been defined so that no tracking should occur.

EQQE016I

ETT HAS SUCCESSFULLY ADDED ADID FOR TRIGGERING EVENT TRIG

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

Processing continues.

None.

EQQE017I

THE ETT FUNCTION IS ACTIVATED

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.

Processing continues.

None.

EQQE018I

THE ETT FUNCTION IS DEACTIVATED

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.

Processing continues.

None.

EQQE019I

JOBNAME(JOBNUM) WAS SUBMITTED OUTSIDE THE PRODUCTAND TRACK(OPCASUB) OR TRACK(JOBOPT) IS ACTIVE, BUT THE JOB WILL BE TRACKED ANYWAY BECAUSE IT BELONGS TO AN APPLICATION THAT WAS ADDED BY ETT

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 tracks the job because it belongs to an application that was added by ETT.

None.

EQQE020W

EXPANDED JCL USED IN LAST RUN BUT NO STEP NAME CHANGE TABLE FOUND FOR JOBNUM .

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.

Processing continues without using the step name table information.

Check EQQMLOG to see if some error occured causing missing step name table for that operation..

EQQE021E

THE EVENT MANAGER WAS UNABLE TO SET STATUS STATUS FOR JOBNAME(JOBNUM)

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

The status of the current operation remains unchanged. The event manager continues normally by processing the next event.

Correct all errors and, if necessary, restart HCL Workload Automation for Z.

If the current operation can be determined, set the correct status for this operation.

Review earlier messages in the HCL Workload Automation for Z message log to determine which operation is involved. The most likely cause of this error is an unsuccessful I/O operation against the current plan data set.

EQQE022E

EVENT MANAGER INITIALIZATION FAILED

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.

If this message is issued while the HCL Workload Automation for Z subsystem is being stopped, subsystem termination continues normally. Otherwise, message EQQZ045W is issued.

Review previous messages in the HCL Workload Automation for Z message log to determine the exact reason for this message.

EQQE023I

THE EVENT MANAGER ENDED NORMALLY

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.

Termination processing continues.

None.

EQQE024E

THE EVENT MANAGER TERMINATED BECAUSE OF UNRECOVERABLE ERRORS

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.

Message EQQZ045W is issued.

If the Event Manager should be activated, issue an operator modify command to start the Event Manager again.

Review earlier messages in the HCL Workload Automation for Z message log to determine the exact reason for this message.

EQQE025I

THE EVENT MANAGER HAS STARTED

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

HCL Workload Automation for Z processing continues.

None.

EQQE026I

APPLICATION APPL ENDED IN ERROR EC. OPER = OPERNUM, PRTY = PRI, IA = IA

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

Normal HCL Workload Automation for Z processing continues.

Perform error recovery actions for the specified operation.

EQQE027I

OPERATION OPERNUM, IN APPLICATION APPL, IA = ARRTIME IS LATE

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

Normal HCL Workload Automation for Z processing continues.

Investigate what is keeping the operation from starting and take appropriate actions to enable it to start.

EQQE028I

LONG DURATION FOR OPERATION OPERNUM, IN APPLICATION APPL, IA = ARRTIME, FOR JOB JOBNAME, WORK STATION WSID

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.

Normal HCL Workload Automation for Z processing continues.

Investigate why the operation has been active so long. If possible, take corrective action to speed up operation processing.

This message can help determine which operation is late. If the operation name (an optional field) was not specified, a blank value is displayed.

EQQE029E

TRACK (OPCASUB/JOBOPT) IS SPECIFIED, AND AS USER SUBMITTED JOBNAME(JOBNUM) OUTSIDE THE PRODUCT, IT WILL NOT BE TRACKED

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.

None.

Determine if the job was submitted outside of HCL Workload Automation for Z. See Customization and Tuning to set the parameters to track external jobs through the JTOPTS statement. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference, "Problem analysis procedures" section, sub-section "Information needed for all problems".

EQQE030I

USER USER CAUSED A NEW SPECIAL RESOURCE TO BE DEFINED. NAME OF NEW RESOURCE IS: RESOURCE

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.

Processing continues.

None.

EQQE031I

THE JOBNAME(JOBNUM) MATCHED THE NOERROR STATEMENT: VALUE

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

Processing continues.

None.

EQQE032I

ALL DEP INFO USER USR ISSUED QUERY ALL DEPS TYP NES LVL

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 request is processed.

None.

EQQE033E

ERRCODE MUST BE SPECIFIED IF STATUS = E

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

The event is not created. Processing ends if it was invoked by a current TSO command. If the command was invoked by the EQQEVPGM program, processing continues with the next statement.

To create the event, make the necessary corrections and issue the command again.

EQQE034W

NUMBER OF OPEN INTERVALS EXCEEDS MAXIMUM FOR WORKSTATION WS

The current plan record of workstation WS is exceeds 32 KB, which is the maximum allowed.
The request is rejected.
Decrease the number of open intervals.

EQQE036I

JOB JOBNAME(JNUM), OPERATION(OPERNUM), OPERATION TEXT(OPTEXT) ENDED IN ERROR EC. PRTY=PRI, APPL = APPL, WORK STATION = WSID, IA = IA, NRC

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.

Normal HCL Workload Automation for Z processing continues.

Perform error recovery actions for the current job.

EQQE037I

JOB JOBNAME(JNUM), OPERATION (OPERNUM) IN APPLICATION APPL, IS LATE, WORK STATION = WSID, IA = ARRTIME

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

Normal HCL Workload Automation for Z processing continues.

Investigate what is keeping the job from starting and take appropriate actions to enable it to start.

EQQE038I

LONG DURATION FOR JOB JOBNAME(JNUM), OPERATION (OPERNUM) IN APPLICATION APPL, WORK STATION = WSID, IA = ARRTIME

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.

Normal HCL Workload Automation for Z processing continues.

Investigate why the job has been active so long. If possible, take corrective action to speed up the processing of the job.

EQQE039I

LONG TIME ON INPUT QUEUE FOR JOB JOBNAME (JNUM), OPERATION (OPERNUM), APPL = APPL, WORK STATION = WSID, IA = ARRTIME

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.)

Normal HCL Workload Automation for Z processing continues.

For MVS jobs if the operation status is successful, verify in the message log that the link to the DESTINATION is active, the associated submit task is active, events are available on the associated EQQEVDS data set, and that an event reader funcion is active. In a shared DASD environment, also verify that no hardware reserves, or other contention are locking access to the data set.

Investigate what is keeping the job from starting and take appropriate actions to enable it to start. For FT-jobs it could be possible that the job is started on the agent but the workstation is unlinked.

EQQE040W

JOB JOBNAME(JOBNUM) CANNOT BE HANDLED. THE JOB MAY HAVE TO BE CANCELED

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.

HCL Workload Automation for Z assumes that the job is not a HCL Workload Automation for Z job and does not track the job. If the job has the status Hold because one of the following settings, it is released even if it is not an HCL Workload Automation for Z job::
  • HOLDJOB(YES)
  • HOLDJOB(USER) and TYPRUN=HOLD

Ensure that the JCL in the HCL Workload Automation for Z for the reported job contains only one job card, and that there are no extraneous characters after END OF JOB. If the submitted job has the same name of a job submitted externally or by another Z controller that submits on the same system, the job needs to be canceled. However, before canceling the job check if it has dependencies; in this case, update the plan with a new job.

Determine if HCL Workload Automation for Z and non-HCL Workload Automation for Z jobs are using the same job names. Check that all jobs belonging to HCL Workload Automation for Z defined applications are defined in the current plan.

EQQE041W

THE EVENT MANAGER HAS IGNORED THE FOLLOWING USER DEFINED EVENT RECORD BECAUSE THE NEW STATUS IS NOT VALID FOR A FTW OPERATION: EXITREC

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 incorrect event record is returned to the free queue of the event manager without any further processing.

Determine if any user program generates events that change the status of an FTW operation.

EQQE042I

JOBNAME(JOBNUM) SUBMITTED OUTSIDE THE PRODUCT BUT WILL BE TRACKED ANYWAY

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.

HCL Workload Automation for Z accepts current job as a HCL Workload Automation for Z job and continues to track events for this job.

Determine if HCL Workload Automation for Z and non-HCL Workload Automation for Z jobs are using the same job names. If HCL Workload Automation for Z and non-HCL Workload Automation for Z jobs are using the same job names, take appropriate action to minimize such name conflicts. Inform HCL Workload Automation for Z application owners that rerunning applications or adding additional work to the job queue should be done using the HCL Workload Automation for Z Modify Current Plan dialog.

EQQE043E

JOB EVENT EVENT RECEIVED FOR JOBNAME(JOBNUM) IS NOT CONSISTENT WITH CURRENT OPC STATUS OF THIS JOB: STATUS

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 status of the operation is not changed. The Event Manager continues normal operation with the next queued event.

Use console messages in the z/OS SYSLOG data set, or records in an SMF log data set to determine what has happened to this job. If possible, try to locate the SYSMSG data set for this job.

EQQE044W

JOBNAME(JOBNUM) MAY HAVE BEEN STARTED OUT-OF-ORDER. IF REQUIRED, SET CORRECT STATUS MANUALLY

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 status of the operation is not changed. The Event Manager continues normal operation with the next queued event.

Determine if predecessors to the current operation have completed. If they have, change their status to complete, and change the status of the current operation to started. If they have not, the current job should be entered into hold status, and the job should be restarted. After predecessors have completed, the job should be released from hold.

Determine if the job was submitted outside of HCL Workload Automation for Z or if it was held and released manually. Inform all people concerned about the reason for this message and take appropriate action to make sure that operations are started only after all predecessors are complete.

EQQE045E

ERRORS OCCURRED READYING SUCCESSOR TO THE FOLLOWING OPERATION: APPLICATION = APPL, INPUT ARRIVAL = ARRTIME, OPERATION NUMBER = OPNUM THE FAILURE REASON WAS REASON. THE PROBLEM SUCCESSOR OPERATION: APPLICATION = SAPPL, INPUT ARRIVAL = SARRTIME, OPERATION NUMBER = SOPNUM

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 status is not changed for any of the successor operations. Processing continues.

Check each successor operation to see if all its predecessors are complete. If they are complete, change the status of the operation to ready using the MCP dialog.

Review earlier messages in the HCL Workload Automation for Z message log to determine the exact reason for this message. Some possible values for reason are:
R
A VSAM I/O error was encountered when reading the successor operation. See the message reporting the I/O error for more details.
N
The successor operation does not list the predecessor as a dependency.
W
The workstation name for the successor operation is not defined in the current plan.
C
The status of the successor operation is already complete.
M
Setting the status of the successor operation to Ready failed. Check the message log for further messages describing the error.

All of the reasons above indicate an internal product error. Save a copy of the active current plan, the job-tracking archive, and the active job-tracking log. Contact the Software Support.

EQQE046W

THE EVENT MANAGER WAS UNABLE TO RELEASE JOBNAME(JOBNUM) FROM HOLD

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

The hold status of the current job is not changed. The Event Manager continues normal operation with the next queued event.

Check that the job is still held by JES. If it is, enter an appropriate operator command to release the job from hold.

Check that JES is executing normally.

EQQE047W

JOBNAME(JOBNUM) COULD NOT BE RELEASED FROM HOLD BECAUSE THE SUBMIT/RELEASE DDNAME DDNAME COULD NOT BE LOCATED

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.

The hold status of the current job is not changed. The Event Manager continues normal operation with the next queued event.

Check that the job is still held by JES on the system where it is executing. If it is, enter an appropriate operator command to release the job from hold.

Determine if the EWTROPTS statement is in error and should be corrected or if a new current plan containing an additional workstation must be created.

EQQE048W

JOBNAME(JOBNUM) COULD NOT BE RELEASED FROM HOLD BECAUSE OF ERRORS ON THE SUBMIT/RELEASE FILE WITH DDNAME DDNAME

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.

The hold status of the current job is not changed. The Event Manager continues normal operation with the next queued event.

Check that the job is still held by JES on the system where it is executing. If it is, enter an appropriate operator command to release the job from hold.

Review earlier messages in the HCL Workload Automation for Z message log to determine the exact reason for this message.

EQQE049W

THE EVENT MANAGER HAS IGNORED THE FOLLOWING USER DEFINED EVENT RECORD BECAUSE NO MATCHING OPERATION COULD BE FOUND IN CURRENT PLAN: EXITREC

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.

The incorrect event record is returned to the Event Manager’s free queue without any further processing.

Determine if any user program generates events for an undefined application or for an undefined operation in a known application.

EQQE051W

THE EVENT MANAGER HAS IGNORED THE FOLLOWING USER DEFINED EVENT RECORD BECAUSE THE JOBNAME JOBNAME IS NOT RECOGNIZED: EXITREC

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.

The incorrect event record is returned to the Event Manager’s free queue without any further processing.

Determine if any user program generates events for an application or for an operation without specifying a job name.

EQQE050W

THE MANDATORY ACT OPERAND HAS NOT BEEN SPECIFIED IN THE JSUACT COMMAND

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).

The request is rejected.

Add the ACT operand with the desired value to the command.

EQQE052E

THE ISSUER OF THE JSUACT COMMAND HAS NOT THE REQUIRED UPDATE ACCESS AUTHORIZATION TO THE JSUB FIXED RESOURCE

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

The request is rejected

Enhance the RACF authorization of the user or ensure that the JSUACT command be issued by another user having the correct authorization.

EQQE053E

THE EVENT MANAGER HAS IGNORED THE FOLLOWING FTW EVENT RECORD BECAUSE NO MATCHING OCCURRENCE WAS FOUND IN THE CURRENT PLAN: EXITREC

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.

The incorrect event is returned to the Event Manager free queue without any further processing. This error might be a symptom that the HCL Workload Automation Symphony file and the HCL Workload Automation for Z Current Plan VSAM data sets are out of sync.

Check if in the Symphony file any occurrence is present that is not present in the Current Plan. Run Symphony Renew to produce a new Symphony file synchronized with the Current Plan.

EQQE054E

THE EVENT MANAGER HAS IGNORED THE FOLLOWING FTW EVENT RECORD BECAUSE IS NOT CONSISTENT WITH CURRENT STATUS OF THIS JOB: EXITREC

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 incorrect event is returned to the Event Manager free queue without any further processing. This error might be a symptom that the Symphony file and the scheduler Current Plan VSAM data sets are out of sync.

Check that no unsupported manual action has been performed directly from the HCL Workload Automation for Z agent. Run Symphony Renew to produce a new Symphony file synchronized with the Current Plan

EQQE055W

THE EVENT MANAGER HAS IGNORED THE FOLLOWING SUBMIT EVENT RECORD BECAUSE NO MATCHING OPERATION WAS FOUND IN THE CURRENT PLAN: EXITREC

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.

The Event Manager continues normal processing.

If you cannot determine the reason for this message, contact the Software Support.

Check if the current plan has changed significantly since the job defined in the event record was submitted. Check if the submit event is old, and was sent by a HCL Workload Automation for Z subsystem that has been inactive a long time.

EQQE056W

THE EVENT MANAGER HAS IGNORED THE FOLLOWING INVALID EVENT RECORD: EXITREC

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.

The incorrect event record is returned to the Event Manager’s free queue without any further processing.

Save the HCL Workload Automation for Z message log data set (EQQMLOG) containing this message and contact the Software Support.

Note the job name and job number in the exit record. If necessary, set the correct status for this job manually.

EQQE057W

A NOT VALID QUEUE ENTRY HAS CAUSED THE SCHEDULER TO IGNORE THIS EVENT: EVENT HEADER: EVNTHDR EVENT RECORD: EXITREC

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.

The incorrect event record is returned to the Event Manager’s free queue without any further processing.

Save the HCL Workload Automation for Z message log data set containing this message and contact the Software Support.

EQQE058W

THE EVENT MANAGER HAS IGNORED THE FOLLOWING USER DEFINED EVENT RECORD BECAUSE THE WORK STATION NAME WSNAME IS NOT RECOGNIZED: EXITREC

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.

The incorrect event record is returned to the Event Manager’s free queue without any further processing.

Determine if any user program generates events for an undefined workstation or if a new current plan containing an additional workstation must be created.

EQQE059W

THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE WORK STATION WSNAME IS NOT AN AUTOMATICALLY REPORTING WORK STATION: EXITREC

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 incorrect event record is returned to the Event Manager’s free queue without any further processing.

Determine if the user program generating the event should reference some other workstation or if the attributes of the current workstation should be changed.

EQQE061E

THE INPUT DATA SET, DDNAME = SYSIN, COULD NOT BE OPENED

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 ends.

Check that the SYSIN DD statement is present and that it is correctly coded. After making corrections, resubmit the EQQEVPGM batch job.

EQQE062E

EQQEVPGM INITIALIZATION FAILED

The EQQEVPGM program found one or more errors during initialization.

The EQQEVPGM program ends.

Review the message log data set for error messages. Remove the cause of each error and resubmit the EQQEVPGM batch job.

EQQE063I

EQQEVPGM ENDED NORMALLY

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

The EQQEVPGM program ends.

None.

EQQE064E

EQQEVPGM TERMINATED BECAUSE OF UNRECOVERABLE ERRORS

A severe error occurred during execution of the EQQEVPGM program.

The EQQEVPGM program ends.

Review the message log data set and the SYSUDUMP data set to determine the cause of the error. After making corrections, resubmit the EQQEVPGM batch job. If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference, Chapter 3 "Problem analysis procedures".

EQQE065I

THE EQQEVPGM PROGRAM HAS STARTED

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

EQQEVPGM processing continues normally.

None.

EQQE066E

SUBSYS IS NOT A VALID SUBSYSTEM NAME. NO EVENT IS CREATED

The SUBSYS keyword contains an invalid subsystem name.

The event is not created. The EQQEVPGM program continues processing the next event creation statement.

If the event should be created, make the necessary corrections and resubmit the EQQEVPGM batch job.

EQQE067E

A SUBSYSTEM REQUEST ERROR (R15 = R15) OCCURRED. NO EVENT IS CREATED

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

The event is not created. The EQQEVPGM program continues processing the next event creation statement.

If R15 is 4, the SUBSYS keyword does not define a HCL Workload Automation for Z subsystem. If R15 is 8, the SUBSYS keyword either does not define a HCL Workload Automation for Z subsystem or it defines a HCL Workload Automation for Z subsystem that has not been properly installed. Make the necessary corrections and resubmit the EQQEVPGM batch job. If R15 is 12, 16 or 20, search the IBM Support database for a solution at Support.

EQQE068E

A SUBSYSTEM ERROR (SSOBRETN = RETN) OCCURRED. NO EVENT IS CREATED

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

The event is not created. The EQQEVPGM program continues processing the next event creation statement.

If the problem persists, search the IBM Support database for a solution at Support. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference, Chapter 3, "Problem analysis procedures".

EQQE069E

ERRORS ENCOUNTERED IN EVENT DEFINITION STATEMENTS. ONE OR MORE EVENTS HAVE NOT BEEN CREATED

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

The EQQEVPGM program ends.

If the events should be created, make the necessary corrections and resubmit the EQQEVPGM batch job.

EQQE070E

THE SPECIAL RESOURCE NAME GIVEN IS TOO LONG. MAXIMUM SIZE IS 44 CHARACTERS

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

The event is not created. The EQQEVPGM program continues processing the next event creation statement.

If the event should be created, make the necessary corrections and resubmit the EQQEVPGM batch job.

EQQE071E

A SPECIAL RESOURCE NAME IS REQUIRED ON THE SRSTAT STATEMENT

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

The event is not created. The EQQEVPGM program continues processing the next event creation statement.

If the event should be created, make the necessary corrections and resubmit the EQQEVPGM batch job.

EQQE072E

YOU ARE NOT AUTHORIZED TO UPDATE SPECIAL RESOURCES FOR SUBSYSTEM SUBSYS

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.

If you specified SUBSYSTEM(MSTR) in the command, no event is created for this subsystem. However, EQQEVPGM tries to create an event for the next active HCL Workload Automation for Z subsystem in this z/OS system. If you are authorized to update one or more of the HCL Workload Automation for Z subsystems, the statement return code is set to 4. Otherwise, it is set to 8. After scanning all active HCL Workload Automation for Z subsystems, EQQEVPGM continues processing the next event creation statement.

If you specified a unique HCL Workload Automation for Z subsystem name instead of MSTR, no event is created for the subsystem specified. The statement return code is set to 8. The EQQEVPGM program continues processing the next event creation statement.

Contact your security administrator.

EQQE073E

YOU ARE NOT AUTHORIZED TO UPDATE THE CURRENT PLAN FOR SUBSYSTEM SUBSYS

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.

If you specified SUBSYSTEM(MSTR) in the command, no event is created for this subsystem. However, EQQEVPGM tries to create an event for the next active HCL Workload Automation for Z subsystem in this z/OS system. If you are authorized to update one or more of the HCL Workload Automation for Z subsystems, the statement return code is set to 4. Otherwise, it is set to 8. After scanning all active HCL Workload Automation for Z subsystems, EQQEVPGM continues processing the next event creation statement.

If you specified a unique HCL Workload Automation for Z subsystem name instead of MSTR, no event is created for the subsystem specified. The statement return code is set to 8. The EQQEVPGM program continues processing the next event creation statement.

Contact your security administrator.

EQQE074E

THE EVENT CREATION DATE SPECIFIED BY THE EVDATE KEYWORD IS NOT VALID

The EVDATE keyword contains an invalid date. The date must be specified in the format YYMMDD where:
YY
Is year and must specified as 72 to 99 for years 1972 to 1999 or 00 to 71 for years 2000 to 2071.
MM
Is the month number and must be in the range 01 to 12.
DD
Is the day number and must be in the range 01 to 31.

The event is not created. The EQQEVPGM program continues processing the next statement.

If the event should be created, correct the EVDATE keyword and resubmit the EQQEVPGM batch job.

EQQE075E

THE EVENT CREATION TIME SPECIFIED BY THE EVTIME KEYWORD IS NOT VALID

The EVTIME keyword contains an invalid time-of-day value. The time must be specified in the format HHMMSS, where:
HH
Is a two-digit hour number. It must be in the range 00–23.
MM
Is a two-digit minute number. It must be in the range 00–59.
SS
Is a two-digit second number. It must be in the range 00–59.

The event is not created. The EQQEVPGM program continues processing the next statement.

If the event should be created, make the necessary corrections and resubmit the EQQEVPGM batch job.

EQQE076E

THE INPUT ARRIVAL TIME SPECIFIED BY THE IA KEYWORD IS NOT VALID

The IA keyword contains an invalid input arrival value. The value must be specified in the format YYMMDDHHMM where:
YYMMDD
Is the input arrival date:
YY
Is the year. It must in the range 72–99 for years 1972 through 1999 or 00–71 for years 2000 through 2071.
MM
Is the month number. It must be in the range 01–12.
DD
Is the day number. It must be in the range 01–31.
HHMM
Is the input arrival time:
HH
Is the hour. It must be in the range 00–23.
MM
Is the minute. It must be in the range 00–59.

The event is not created. The EQQEVPGM program continues processing the next statement.

To create the event, correct the IA keyword and resubmit the EQQEVPGM batch job.

EQQE077E

WORK STATION NAME, APPLICATION DESCRIPTION OR JOB NAME MUST BE SPECIFIED

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

The event is not created. Processing ends if it was invoked by a current TSO command. If the command was invoked by the EQQEVPGM program, processing continues with the next statement.

To create the event, make the necessary corrections and issue the command again.

EQQE078E

THE EVENT DURATION TIME SPECIFIED BY THE DURATION KEYWORD IS NOT VALID

The DURATION keyword contains an invalid duration value. Event duration must be specified in the format HHMM, where:
HH
Is a two-digit hour number. It must be in the range 00–99.
MM
Is a two-digit minute number. It must be in the range 00–59.

The event is not created. The EQQEVPGM program continues processing the next statement.

To create the event, make the necessary corrections and resubmit the EQQEVPGM batch job.

EQQE079E

KEYWORD KEY HAS AN INVALID VALUE

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.

The event is not created. Processing ends for current SRSTAT command. If SRSTAT is invoked by the EQQEVPGM program, processing continues with the next statement.

To create the event, make the necessary corrections and issue the SRSTAT command again.

EQQE080E

THE EQQMINOX PROGRAM ABENDED WITH ABEND CODE ABEND

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.

Check the HCL Workload Automation for Z message log to determine the cause of the error. If the failing command contains an error, correct it and retry. If you do not find any information, for the information to collect, see the Diagnosis Guide and Reference, "Problem analysis procedures" section, sub-section "Information needed for all problems". If the problem persists, search the IBM Support database for a solution at Support.

Contact your systems programmer.

If necessary, generate a dump by allocating a SYSxDUMP data set to the TSO user's address space, or by defining a slip trap, and issue the failing command again.

EQQE081E

R15 RETURN CODE R15 WAS RETURNED BY THE TSO SERVICE FACILITY. RETURN CODE RC, REASON CODE RSN WERE ALSO RETURNED

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.

The HCL Workload Automation for Z service requested has not been executed.

If the failing command contains an error, correct it and retry. If the error cannot be corrected, see the z/OS TSO manuals and look for the return code and the reason code to identify the cause of the error.

Contact your systems programmer.

EQQE082E

THE SUBSYSTEM SUBSYS IS NOT INITIALIZED. NO EVENT IS CREATED

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.

No event is created.

If the HCL Workload Automation for Z subsystem should be initialized the EQQINIT2 program must be executed successfully. Ensure EQQINIT2 is located in a library in the LNKLSTnn concatenation and IPL the z/OS system.

If the command referred to the wrong subsystem correct the input, and retry the command.

Check the system log for error messages issued during IPL that identify why the HCL Workload Automation for Z subsystem was not initialized.

EQQE083E

SUBSYSTEM SUBSYS IS NOT A PRODUCT SYSTEM. NO EVENT IS CREATED

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.

None.

Correct the command and retry.

EQQE084E

YOU ARE NOT AUTHORIZED TO UPDATE THE SPECIAL RESOURCE SPECIFIED FOR SUBSYSTEM SUBSYS

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 request is rejected.

Contact your security administrator if access is required.

EQQE085E

RESDS IS NOT A VALID RESOURCE DATASET NAME, NO EVENT IS CREATED

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

The request is ignored.

Correct the input and resubmit the request.

EQQE086E

THE RESDS KEYWORD MUST BE SPECIFIED

The resource data set keyword—RESDS was not specified.

The request is ignored.

Supply the RESDS keyword and a valid value and resubmit the request.

EQQE087E

YOU ARE NOT AUTHORIZED TO REQUEST A BACKUP OF THE RESDS RESOURCE DATASET SPECIFIED FOR SUBSYSTEM SUBSYS

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.

The request is ignored.

If authority is required contact your security administrator.

EQQE088E

YOU ARE NOT AUTHORIZED TO UPDATE THE OPERATION, SUBRES CHECK FAILED AT SUBSYSTEM SUBSYS

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.

The request is rejected.

If authority is required contact your security administrator.

EQQE089E

YOU ARE NOT AUTHORIZED TO UPDATE STATUS OF WORKSTATION WSNAME FOR SUBSYSTEM SUBSYS

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 request is rejected.

If authority is required contact your security administrator.

EQQE090E

EITHER WORKSTATION NAME OR DESTINATION MUST BE SPECIFIED

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.

The event is not created. The EQQEVPGM program continues processing any further event creation statements.

If the event should be created, make the necessary corrections and issue the command again or resubmit the EQQEVPGM batch job.

EQQE091E

THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE THE OPCTOKEN VALUE IS NOT CONSISTENT WITH THE VALUE(S) SPECIFIED IN THE ADID, IA, JOBNAME AND/OR OPNUM KEYWORDS: EXITREC

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.

The incorrect event record is returned to the Event Manager's free queue without any further processing.

If a new event should be created, make the necessary corrections and issue the command again or resubmit the EQQEVPGM batch job.

EQQE092E

THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE THE CURRENT OPERATION STATUS IS NOT STARTED, READY OR ARRIVING: EXITREC

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).

The incorrect event record is returned to the Event Manager's free queue without any further processing. The operation status is not changed.

If a new event should be created, make the necessary corrections and issue the command again or resubmit the EQQEVPGM batch job.

EQQE093E

THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE THE WORKSTATION WSNAME IS NOT A COMPUTER OR WTO WORKSTATION: EXITREC

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.

The incorrect event record is returned to the Event Manager's free queue without any further processing. The workstation status is not changed.

If a new event should be created, make the necessary corrections and issue the command again or resubmit the EQQEVPGM batch job.

EQQE094E

THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE THE WORKSTATION WSNAME DOES NOT MATCH THE DESTINATION DEST: EXITREC

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.

The incorrect event record is returned to the Event Manager's free queue without any further processing. The workstation status is not changed.

If a new event should be created, make the necessary corrections and issue the command again or resubmit the EQQEVPGM batch job.

EQQE095E

THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE THE DESTINATION DEST IS NOT SPECIFIED IN THE ROUTOPTS INITIALIZATION STATEMENT: EXITREC

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 incorrect event record is returned to the Event Manager's free queue without any further processing. The workstation status is not changed.

If a new event should be created, make the necessary corrections and issue the command again or resubmit the EQQEVPGM batch job.

EQQE096E

THE STATUS KEYWORD MUST BE SPECIFIED

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

The event is not created. The EQQEVPGM program continues processing the next event creation statement.

If the event should be created, make the necessary corrections and resubmit the EQQEVPGM batch job.

EQQE097E

THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE THE SPECIFIED TOKEN VALUE DOES NOT MATCH ANY OPERATION IN THE CURRENT PLAN: EXITREC

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.

The incorrect event record is returned to the Event Manager's free queue without any further processing.

If a new event should be created, make the necessary corrections and issue the command again or resubmit the EQQEVPGM batch job.

EQQE098E

THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE THE CURRENT OPERATION STATUS IS SS: EXITREC

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.

The incorrect event record is returned to the Event Manager's free queue without any further processing. The workstation status is not changed.

If a new event should be created, make the necessary corrections and issue the command again or resubmit the EQQEVPGM batch job.

EQQE099E

THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE THE ALTERNATE WORKSTATION WSNAME DOES NOT EXIST: EXITREC

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.

The incorrect event record is returned to the Event Manager's free queue without any further processing. The workstation status is not changed.

If a new event should be created, make the necessary corrections and issue the command again or resubmit the EQQEVPGM batch job.

EQQE100E

THE CURRENT WORKSTATION WSNAME CANNOT BE USED AS ALTERNATE TO ITSELF. REROUTE IS NOT IN EFFECT FOR THE WORKSTATION

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

Reroute is not in effect for the actual workstation. The workstation status is changed.

Insert the correct value in the WSNAME field of the WSSTAT command. See Managing the Workload.

EQQE101E

KEYWORD KEY HAS AN INVALID VALUE

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

The event is not created. Processing ends for current SRSTAT command. If SRSTAT is invoked by the EQQEVPGM program, processing continues with the next event creation statement.

If the event should be created, make the necessary corrections and issue the SRSTAT command again.

EQQE102W

PULSE LOST FROM TRACKER SUBS AT DESTINATION DEST

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.

If the destination DEST is defined using shared DASD (submit/release) data set communication, this destination is forced Offline by the controller. For other communication methods, no action is taken.

Check that the destination is active. If it is, check that the event writer at the destination is active.

EQQE103W

TRACKER SUBS AT DESTINATION DEST LOST THE FUNC

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.

No action is taken by the controller.

Check the message log for the indicated Tracker address space and take appropriate actions to restart the failed subtask.

EQQE104E

KEYWORD KEYW MISSING. IT IS REQUIRED FOR SUBRESOURCE SUBRES CHECKING AT SUBSYSTEM SUBSYS

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.

No event is created for the subsystem identified in the message text. If SUBSYSTEM(MSTR) was specified in the input, the request is directed to the next scheduler subsystem. If event creation failed for one or more subsystems, return code 4 is set. If it failed for all subsystems or for a subsystem specifically identified in the input, return code 8 is set.

Add the keyword and resubmit the EQQEVPGM job for the failing subsystem.

EQQE105W

DATA STORE FUNCTIONALITY IS ACTIVE ON CONTROLLER BUT NOT ON TRACKER

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.

None.

Check that the EQQSSCMx level of code is correct.

Contact your system programmer.

EQQE107I

SUCCESSFUL HWA-WLM PROMOTION FOR ADID WSID OPNUM IA: IA JOB: JOBNAME(JOBNUM) IN SERVICE CLASS WLMCLASS

The job identified by:
Application name
ADID
Workstation
WSID
Operation number
OPNUM
Job name
JOBNAME
Job number
JOBNUM
Input arrival
IA
was successfully promoted to the WLM service class WLMCLASS.

The job was successfully promoted and its processing continues.

None.

EQQE108E

THE EVENT MANAGER HAS IGNORED THE FOLLOWING FTW EVENT RECORD BECAUSE NO MATCHING OPERATION COULD BE FOUND IN CURRENT PLAN: EXITREC

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.

The incorrect event is returned to the Event Manager free queue without any further processing. This error might be a symptom that the Symphony file and the scheduler Current Plan VSAM data sets are out of sync.

Check if in the Symphony file any operation is present that is not present in the Current Plan. Run Symphony Renew to produce a new Symphony File synchronized with the Current Plan.

EQQE109E

THE EVENT MANAGER HAS IGNORED THE FOLLOWING FTW EVENT RECORD BECAUSE THE WORK STATION NAME WSNAME IS NOT RECOGNIZED: EXITREC

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.

The incorrect event is returned to the Event Manager free queue without any further processing. This error might be a symptom that the Symphony file and the scheduler Current Plan VSAM data sets are out of sync.

Check if in the Symphony file any operation is present that is not present in the Current Plan. Run Symphony Renew to produce a new Symphony File synchronized with the Current Plan.

EQQE110W

THE EVENT MANAGER WAS UNABLE TO SET STATUS STATUS FOR OPERATION OPERNUM, IN APPLICATION APPL, IA=ARRTIME. THE OPERATION IS SET INTO OUT OF SEQUENCE STATUS

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.

The operation is set in Error status with error code OSEQ (Out Of Sequence).

Check the status of the job on the agent and, when the predecessors are completed, manually set the operation to the correct status.

EQQE111W

THE EVENT MANAGER WAS UNABLE TO SET STATUS STATUS FOR OPERATION OPERNUM, IN APPLICATION APPL, IA=ARRTIME. THE EVENT IS DISCARDED

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.

The event is discarded and the operation status is left as it is before.

Check the status of the job on the agent and, when the predecessors are completed, manually set the operation to the correct status.

EQQE112E

THE EVENT MANAGER WAS UNABLE TO SET STATUS STATUS FOR THE FAULT-TOLERANT WORKSTATION WSNAME

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 event is discarded and the workstation status is left as it was before.

Insert the correct value in the WSNAME field of the WSSTAT command. See Managing the Workload.

EQQE113W

AN ERROR HAS OCCURRED SENDING THE SCRIPT TO THE DISTRIBUTED AGENT FOR OPERATION OPERATION, IN APPLICATION APPL, IA=ARRTIME. THE OPERATION STATUS IS RESET TO READY

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.

The Workstation Analyzer task retries the job submission for a maximum of 10 times over a 5 minute period.

Check the controller and the server MLOG for the error causing the failure.

If the error persists, contact your system programmer.

EQQE114E

THE EVENT MANAGER WAS UNABLE TO SET AN ALTERNATE WORKSTATION FOR THE FAULT-TOLERANT WORKSTATION WSNAME.

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.

The request is discarded.

Insert the correct value in the WSNAME field of the WSSTAT command. See Managing the Workload.

EQQE115E

KEYWORDS STATUS, CMD AND MANAGES MUST BE MUTUALLY EXCLUSIVE

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.

The request is discarded.

Rerun the WSSTAT command specifying the correct keywords. Refer to Managing the workload.

EQQE116E

WSNAME IS NOT A FAULT-TOLERANT WORKSTATION. THE COMMAND KEYWORD IS INCORRECT

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.

The request is rejected.

Rerun the WSSTAT command specifying the correct keywords. Refer to Managing the workload.

EQQE117E

WSNAME IS NOT A FAULT-TOLERANT WORKSTATION. THE MANAGES KEYWORD IS INCORRECT

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.

The request is rejected.

Rerun the WSSTAT command specifying the correct keywords. Refer to Managing the workload.

EQQE118E

THE EVENT MANAGER HAS IGNORED THE FOLLOWING FTW EVENT RECORD BECAUSE IT WAS UNABLE TO RETRIEVE RECOVERY INFORMATION: EXITREC

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.

The incorrect event is returned to the Event Manager free queue without any further processing. This error may be a symptom that the Symphony file and the scheduler Current Plan VSAM data sets are out of sync.

Check the Symphony file for an operation that is not present in the current plan. Run Symphony Renew to produce a new Symphony File and to synchronize it with the current plan.

EQQE119E

THE FOLLOWING USER DEFINED EVENT RECORD CANNOT BE USED BECAUSE THE ALTERNATE WORKSTATION WSNAME IS A FAULT-TOLERANT WORKSTATION.

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 request is discarded.

Rerun the WSSTAT command specifying the correct keywords. Refer to Managing the workload.

EQQE120W

WRONG TYPE OPERAND WAS SPECIFIED IN THE JSUACT COMMAND POSSIBLE VALUES ARE H=HOST/F=FTW/B=BOTH

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 is rejected.

Insert the right value.

EQQE122E

UNSUPPORTED STATUS CHANGE OF OSEQ OPERATION WITH UNCOMPLETED PREDECESSOR(S)

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.

The request is rejected.

The OSEQ operation can be reset to the proper status, waiting, by using the operation restart request from the ended-in-error list panel. The modify occurrence request can also be used. The operation can be deleted or the occurrence can be deleted or set to waiting. An occurrence rerun or a change of the operation status is not accepted until all predecessors have been completed or the dependencies have been deleted.

EQQE123I

A SYSTEM AUTOMATION MESSAGE WILL FOLLOW RELATED TO OPERATION: APPL: APPLID IA: IA OPERATION: OPNO

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 message received from System Automation follows in the log only if MLOG is one of the destinations specified in the AUTOMATIONMSG parameter of the OPCOPTS statement.

Check the message content and correct the reason of the error. Issue a system automation operation again.

EQQE124W

THE MONITORING TASK IS NOT RUNNING: THE BULKDISC USER EVENT RECORD IS IGNORED

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

The user request is ignored.

Start the monitoring task. To initiate the bulk discovery run the TSO BULKDISC command again.

EQQE125W

A BULK DISCOVERY IS ALREADY RUNNING. THE BULKDISC USER EVENT RECORD IS IGNORED

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

The user request is ignored.

Wait for the previous bulk discovery to end. Submit the bulk discovery again

EQQE126W

THE BULKDISC USER EVENT RECORD IS IGNORED. PLANNING ACTIVITY IS IN PROGRESS.

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

The user request is ignored.

Wait for the planning activity to end. Submit the bulk discovery again.

EQQE127W

MISSING STEP END EVENT FOR OPERATION APPLID1 IA1 OPNO1 JOB NAME JOBN1. CONDITION DEPENDENCY SIMP IN CONDITION COND DEFINED ON OPERATION APPLID2 IA2 OPNO2 WILL REMAIN UNDEFINED.

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

The scheduler cannot evaluate the indicated condition.

Possible causes are:
  • The EWTROPTS initialization statement, for the tracker event-writer task, does not specify either the SDEPFILTER or STEPEVENTS(ALL) parameter. One of them is necessary to activate the step-end event generation.
  • The SDEPFILTER string value does not match the JOB card programmer name value or a subset of it, according to the specified start position.
  • The step name specified in the dependency definition does not correspond to a step in the JCL that actually run.

EQQE128E

WSSTAT COULD NOT SET AN ALTERNATE WORK STATION FOR WSNAME. THE ALTERNATE WORK STATION MUST BE OF THE SAME TYPE.

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

The command is ignored.

Issue the command again by specifying a HCL Workload Automation Agent agent as the alternate workstation.

EQQE130I

OPERATION ADID WSID OPNUM JOBNAME IA: IA LATEST START TIME: LOUT IS A CRITICAL JOB AND NEXT TO BE LATE: MOVED TO READY URGENT QUEUE

The operation identified by:
Application name
ADID
Workstation
WSID
Operation number
OPNUM
Job name (if applicable)
JOBNAME
Input arrival
IA
is reaching its latest start time LOUT in about 2 minutes, but has not started yet.

HCL Workload Automation for Z moves the operation to the queue used for operations with priority 9, to speed up its starting.

Check if there is any reason that prevents the operation from starting, for example the availability of a special resource.

EQQE131I

OPERATION ADID WSID OPNUM JOBNAME IA: IA LATEST START TIME: LOUT IS A CRITICAL JOB NO MORE LATE: REMOVED FROM READY URGENT QUEUE

The operation identified by:
Application name
ADID
Workstation
WSID
Operation number
OPNUM
Job name (if applicable)
JOBNAME
Input arrival
IA
was previously promoted to the ready urgent queue, but its starting is no longer late. The operation is therefore moved back to the ordinary queue.

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

HCL Workload Automation for Z moves the operation to the ordinary queue.

Check if the latest start time modified by the DP batch is really what you want.

EQQE132E

UNSUCCESSFUL HWA-WLM PROMOTION FOR ADID WSID OPNUM IA: IA JOB: JOBNAME(JOBNUM) IN SERVICE CLASS WLMCLASS. SERVICE CLASS WLMCLASS IS NOT DEFINED IN THE ACTIVE WORKLOAD MANAGER POLICY

The job identified by:
Application name
ADID
Workstation
WSID
Operation number
OPNUM
Job name
JOBNAME
Job number
JOBNUM
Input arrival
IA
cannot be promoted to the WLM service class WLMCLASS, because the class is not defined in the active workload manager policy.

The job is not promoted to the specified WLM service class.

Correct the service class definition or modify the current plan to specify for the operation a WLM service class that is defined in the workload manager policy.

EQQE133E

UNSUCCESSFUL HWA-WLM PROMOTION FOR ADID WSID OPNUM IA: IA JOB: JOBNAME(JOBNUM) IN SERVICE CLASS WLMCLASS. WLM MACRO INVOKED: WLMMACRO. RETURN CODE: WLMRC REASON CODE: WLMRSN

The job identified by:
Application name
ADID
Workstation
WSID
Operation number
OPNUM
Job name
JOBNAME
Job number
JOBNUM
Input arrival
IA
cannot be promoted to the WLM service class WLMCLASS. The following information is provided to find the reason for the unsuccessful promotion:
WLM macro invoked
WLMMACRO
Return code
WLMRC
Reason code
WLMRSN

The job is not promoted to the specified WLM service class.

Based on the information provided by this message, refer to the WLM documentation to find the reason for the unsuccessful promotion of the job.

EQQE136W

THE EVENT MANAGER HAS IGNORED THE FOLLOWING EVENT BECAUSE THE WORKSTATION WSID IS VIRTUAL AND TRACKER DOES NOT SUPPORT IT: EXITREC

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 virtual workstation WSID will have the destination associated to the tracker that generated the event not synchronized. That destination will not be available for submissions.

Check that all the destinations belonging to the virtual workstation WSID are associated to trackers.

None.

EQQE137I

STATUS OF OPERATION ADID OPNUM IA IA HAS BEEN SET TO INTERRUPTED DUE TO OFFLINE WORKSTATION.

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.

Processing continues.

None.

EQQE138I

STATUS OF OPERATION ADID OPNUM IA IA HAS NOT BEEN RESET BY ERRRES DUE TO CONDITIONAL SUCCESSORS IN STATUS C,S,E,X.

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.

Processing continues.

None.

EQQE139W

THE EVENT MANAGER WAS UNABLE TO PROCESS THE FOLLOWING BIND REQUEST: EXITREC. REASON: REASON.

The Event Manager was unable to process a bind request. The reason indicates the cause of the problem:
1
Error adding a data queue element to an internal queue.
2
Error accessing VSAM data set.

The event record is returned to the Event Manager’s free queue without any further processing.

For problems related to data queue elements or accessing VSAM data set, refer to the specific messages in the log.

EQQE141W

UNEXPECTED RC OCCURRED FOR OPERATION: ADID APPL, IA ARRTIME, OPNO OPNUM, WS WSN, JOBNAME JOBNM, JOBID JOBID, DEST DEST WHEN SET TO STATUS ST.

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 is flagged as Unexpected RC and the status of the conditions of its conditional successors is set to Undefined.

Verify the following:
  • Make sure you correctly typed condition definitions.
  • If the operation result was expected, make sure that a successor is defined for that result.
  • If the operation result was not expected, fix the error that caused that result.
Then rerun the occurrence or manually operate appropriately to let the successors start.

EQQE142W

UNEXPECTED RC OCCURRED FOR OPERATION: ADIDAPPL, IA ARRTIME, OPNO OPNUM, WS WSN, JOBNAME JOBNM, JOBID JOBID, DEST DEST WHEN CHECKING END OF STEP: SNAM PNAM.

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.

The operation is flagged as Unexpected RC and the status of the conditions of its conditional successors is set to Undefined.

Verify the following:
  • Make sure you correctly typed condition definitions.
  • If the operation result was expected, make sure that a successor is defined for that result.
  • If the operation result was not expected, fix the error that caused that result.
Then rerun the occurrence or manually operate appropriately to let the successors start.

EQQE143E

THE EVENT MANAGER WAS UNABLE TO OPEN THE DDNAME DATA SET. THE HTTPOPTS OUTPUTCOLLECTOR VALUE IS FORCED TO NO.

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 communication with the output collector is interrupted. Joblogs for jobs that run on z-centric and dynamic agents are not collected or written to JES by the output collector.

Check the controller MLOG and analyze the previous messages that explains why the data set cannot be opened. Solve the problem and restart the controller.

EQQE144E

ERROR OCCURRED WHILE NOTIFYING THE OUTPUT COLLECTOR TO GET THE JOBLOG FOR OPERATION OPERNUM, IN APPLICATION APPL, IA=ARRTIME. THE FAILURE REASON IS: REASON.

An error occurred while notifying the output collector to get the joblog for the operation. REASON indicates the failure type; possible reasons are:
  • The EQQOUCEV event data set is full.
  • An error occurred while enqueueing or dequeueing a logical resource
  • An error occurred while reading or updating the EQQOUCEV event data set header.
  • An error occurred while reading or updating the EQQOUCEV event data set record.

The event manager task continues its processing, but any event sent to the output collector will be lost if additional z-centric jobs are run before the problem is corrected.

Check the system log for messages indicating more details about the cause of the problem.

EQQE145W

THE DDNAME EVENT DATA SET USE HAS EXCEEDED THE THRESHOLD VALUE. PERCENT % OF THE DATA SET IN USE.

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

The event manager task continues its processing, but any event sent to the output collector will be lost if additional z-centric jobs are run before the problem is corrected.

Check the system log and the output collector EQQMLOG for any messages identifying the problem. If there are no message, this means that the data set is to small, allocate a larger data set. Stop and restart the controller and the output collector.

The DDNAME data set is too small or the output collector cannot process events for a problem.

EQQE146W

THE DDNAME EVENT DATA SET IS FULL.

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

The event manager task continues its processing, but any event sent to the output collector will be lost if additional z-centric jobs are run before the problem is corrected.

Check the system log and output collector EQQMLOG for any messages identifying the problem. If there are no message, this means that the data set is to small, allocate a larger data set. Stop and restart the controller and the output collector.

The DDNAME data set is too small or the output collector cannot process events for a problem.

EQQE147I

SUSPENDED EXECUTION EVENT ARRIVED FOR OPERATION: ADID IA OPER.

The scheduler controller has received an event from AS/400 agents about a job whose execution was suspended due to the AS/400 agent prompt functionality. The operation extended status is set to Suspended Execution.
Processing continues.
None.

EQQE150W

JOB JOBNAME, APPLICATION APPL, IA ARRTIME, OPNO OPNUM HAS NOT YET STARTED (NOT STARTED ALERT).

See message text.

Processing continues.

None. This is an alert message.

EQQE151W

JOB JOBNAME, APPLICATION APPL, IA ARRTIME, OPNO OPNUM HAS NOT YET STARTED (NOT STARTED ACTION).

See message text.

Processing continues.

None. This is an alert message.

EQQE152W

JOB JOBNAME, APPLICATION APPL, IA ARRTIME, OPNO OPNUM HAS NOT YET COMPLETED (DEADLINE ACTION).

See message text.

Processing continues.

None. This is an alert message.

EQQE153W

JOB JOBNAME, APPLICATION APPL, IA ARRTIME, OPNO OPNUM WAS ACTION BECAUSE NOT YET STARTED (NOT STARTED ACTION).

See message text.

Processing continues.

None. This is an alert message.

EQQE154W

JOB JOBNAME, APPLICATION APPL, IA ARRTIME OPNO OPNUM WAS ACTION BECAUSE NOT YET COMPLETED (DEADLINE ACTION).

See message text.

Processing continues.

None. This is an alert message.

EQQE155W

JOB JOBNAME, APPLICATION APPL, IA ARRTIME OPNO OPNUM WAS NOPED BECAUSE STATUS STATUS COULD NOT BE CHANGED (DEADLINE ACTION).

See message text.

Processing continues.

None. This is an alert message.

EQQE156W

JOB JOBNAME, APPLICATION APPL, IA ARRTIME OPNO OPNUM WAS NOPED BECAUSE STATUS STATUS COULD NOT BE CHANGED (NOT STARTED ACTION).

See message text.

Processing continues.

None. This is an alert message.

EQQE157W

JOB JOBNAME, APPLICATION APPL, IA ARRTIME OPNO OPNUM COULD NOT BE ACTION BECAUSE STATUS STATUS COULD NOT BE CHANGED (DEADLINE ACTION). ACTION IS POSTPONED.

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

Processing continues.

None. This is an alert message.

EQQE158W

JOB JOBNAME, APPLICATION APPL, IA ARRTIME OPNO OPNUM COULD NOT BE ACTION BECAUSE STATUS STATUS COULD NOT BE CHANGED (NOT STARTED ACTION). POST.

See message text, where:
ACTION
Can be either Set to Error or Completed.
POST
Can be either Action is postponed or No action to be postponed.

Processing continues.

None. This is an alert message.

EQQE159W

JOB JOBNAME, APPLICATION APPL, IA ARRTIME OPNO OPNUM COULD NOT BE NOPED BECAUSE STATUS STARTED DOES NOT ALLOW THIS ACTION.

See message text.

Processing continues.

None. This is an alert message.

EQQE170W

JOB JOBNAME, APPLICATION APPL, IA ARRTIME OPNO OPNUM COULD NOT BE ACTION BECAUSE OF CONDITIONAL SUCCESSORS TYPE.

See message text.

Processing continues.

None. This is an alert message.

EQQE200W

JSUACT REQUEST IGNORED. SUBTASK HAS TERMINATED.

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

The request is rejected.

Review the message log for messages that could explain why NMM is unavailable.

EQQE201W

SUBMIT FUNCTION ALREADY ACTIVE FOR ENV

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

The request is ignored.

None.

EQQE202W

SUBMIT FUNCTION ALREADY INACTIVE FOR ENV

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

The request is rejected.

None.

EQQE203I

SUBMIT FUNCTION ACTIVATED FOR HOST, Z-CENTRIC, DYNAMIC AND REMOTE ENGINE WORKSTATIONS

The job submit activate command has been accepted and executed.

None.

None.

EQQE204I

SUBMIT FUNCTION INACTIVATED FOR HOST, Z-CENTRIC, DYNAMIC AND REMOTE ENGINE WORKSTATIONS

The job submit deactivate command has been accepted and executed.

None.

None.

EQQE205E

ENV JOB SUBMISSION REQUEST REJECTED, E2E FEATURE NOT ACTIVE

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

The request is ignored.

Start the end-to-end feature before running the command

EQQE206W

TIME DISCREPANCY (DISCR HUNDREDTHS OF A SECOND) IN EVENTS FOR APPLID IA OPNUM JOBNAME (JOBID)

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.

Processing of the job terminates with error code CCUN.

Because the error is caused by a discrepancy in JMRENTRY but all the events are present for the job, you can manually complete the operation.

EQQE207I

MAXSTNUM VALUE = VALUE EXCEEDED LONG TIME ON INPUT QUEUE FOR NUMBER JOBS ON WORKSTATION = WSNAME. CHECK EQQE039I MESSAGES FOR DETAILS.

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.

Processing continues.

Review all the messages EQQE039I that were issued, to identify the affected jobs and follow the instructions provided.

EQQE210I

HWA UPDATED THE GMT OFFSET ON SYSTEM SYSID

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 tracker generates the event and modifies the GMT offset, if the difference in the GMT offset is at least of 1 minute. The controller, if the event was created in its own system, updates its GMT offset and issues message EQQE210I into its MLOG. If the event was created in a system different from the system where the controller runs, the controller issues message EQQE210I but does not update its GMT offset.

None.

EQQE300E

FOLLOWING EVENT HAS BEEN IGNORED BECAUSE REQUEST TOKEN DID NOT MATCH EXITRC

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 continues normal operation with the next queued event.

Save the message log containing this message and the JT files with the event, then search the IBM Support database for a solution at Support.

EQQE301E

FOLLOWING EVENT HAS BEEN IGNORED BECAUSE DOA OPERATION BLOCK WAS NOT FOUND EXITREC

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

The Event Manager continues normal operation with the next queued event.

Save the message log containing this message and the JT files with the event. Search the IBM Support database for a solution at Support.

EQQE302I

APPL: APPLID IA: IA WS: CPU OPNUM: OPNO JOB: JOBNAME IS WAITING FOR SCHEDULING ENVIRONMENT: SCHED NOT AVAILABLE IN ENV SID=SYSPLEXID

The job identified by:
Application name
APPLID
Input arrival
IA time
Workstation
CPU
Operation number
OPNUM
Job name
JOBNAME
could not be submitted because the associated scheduling environment SCHED is not available.

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 job is now in the READY status and in the WAITING FOR SE extended status. It remains ineligible for submission until the scheduling environment is again available.

Make the scheduling environment available so that the job can be submitted again.

EQQE303W

APPL: APPLID IA: IA WS: CPU OPNUM: OPNO JOB: JOBNAME SET TO ERROR: SCHEDULING ENVIRONMENT SCHED NOT AVAILABLE IN ENV SID=SYSPLEXID AND OPERATION COMES FROM RC PATH.

The job identified by:
Application name
APPLID
Input arrival
IA time
Workstation
CPU
Operation number
OPNUM
Job name
JOBNAME
could not be submitted because the associated scheduling environment SCHED is not available. The job is now in error with error code SERC.

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 job is set to Error with code SERC. It was not set to the READY status because it comes from Restart and Clean Up paths and the original customized JCL is no longer available.

Make the scheduling environment available so that the job can be submitted again.

EQQE304W

APPL: APPLID IA: IA WS: CPU OPNUM: OPNO JOB: JOBNAME SET TO ERROR: SCHEDULING ENVIRONMENT SCHED IS NOT DEFINED IN ENV SID=SYSPLEXID

The job identified by:
Application name
APPLID
Input arrival
IA time
Workstation
CPU
Operation number
OPNUM
Job name
JOBNAME
could not be submitted because the associated scheduling environment SCHED was not defined to WLM.

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 job is set to Error with code SEUN.

Check whether the scheduling environment is defined incorrectly in the JCL or in the CP operation record, or if the WLM definition is missing. Fix the error so that the job can be submitted.

EQQE305I

WLM SERVICE DEFINITION WAS SUCCESSFULLY INSTALLED IN SYSPLEX SID

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

None.

None.

EQQE306I

WLM VARY POLICY WAS SUCCESSFULLY EXECUTED IN SYSPLEX SID

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).

All operations in waiting status, but waiting for a Scheduling Environment belonging to the specified sysplex, are resubmitted.

None.

EQQE307W

APPL: APPLID IA: IA WS: WSID OPNUM: OPNUM JOB: JOBNAME HAS AT LEAST ONE SPECIAL RESOURCE WITH MAXLIMIT GREATER THAN 0 THIS IS NOT COMPATIBLE WITH WAITING FOR SE STATUS.

This message is preceded by message EQQE302I. It is issued when the operation identified by:
Application name
APPLID
Input arrival
IA time
Workstation
WSID
Operation number
OPNUM
Job name
JOBNAME
is set to Ready, waiting for scheduling environment, and at least one special resource with maximum limit greater than 0 is associated with it.

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.

Processing continues.

Identify the special resources associated with the operation that have the maximum limit function active. For these special resources, ensure that the global availability status is the one you want (the maximum limit might have been reached before the expected time).

EQQE308I

THE FOLLOWING EVENT HAS BEEN IGNORED BECAUSE OPERATION IS COMPLETED: EXITREC.

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 continues normal processing with the next event in queue.

None.

EQQE309I

A PARTIAL DEADLINE UPDATE HAS OCCURRED IN AD DATABASE FOR APPLID OPNUM.

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.

The Event Manager continues normal processing with the next event in queue.

None.

EQQE901I

JOBNAME(JOBNUM) SUBMITTED OUTSIDE HWA BUT WILL BE TRACKED ANYWAY. AD ADID IA IA OP OPNUM WS WSID ST OPST OCST OCCST TX TXT

See message text.

None.

None.

EQQE903I

JOBNAME(JOBNUM) SUBMITTED OUTSIDE HWA AND WILL NOT BE TRACKED BECAUSE AD ADID IA IA OP OPNUM WS WSID ST OPST OCST OCCST TX TXT

See message text.

None.

None.