EQQW000 - EQQW902

EQQW000E

NO AUTHORITY TO ACCESS THE WORK STATION DESCRIPTION

You have attempted to access the workstation description database, but you are not authorized to access it. Or, you do not have access authority to at least one of the following HCL Workload Automation for Z resources that are used together with the workstation description database: the application description database, the calendar database, or the operator instruction database.

The request is rejected and the system waits for you to respond.

Ask the security administrator to provide you the appropriate permissions to perform the required action. Retry the operation.

EQQW001E

NO AUTHORITY TO UPDATE THE WORK STATION DESCRIPTION

You have attempted to update the workstation description database, but you are not authorized to update it. Or, you do not have access authority to at least one of the following HCL Workload Automation for Z resources that are used together with the workstation description database: the application description database, the calendar database, or the operator instruction database.

The request is rejected and the system waits for you to respond.

Ask the security administrator to provide you the appropriate permissions to perform the required action. Retry the operation.

EQQW002I

WORK STATION DESCRIPTION HAS BEEN UPDATED

The workstation description record has been updated and added to the workstation description database.

None.

None.

EQQW003I

WORK STATION DESCRIPTION HAS BEEN DELETED

The workstation description record has been deleted from the workstation description database.

None.

None.

EQQW004I

WORK STATION DESCRIPTION HAS BEEN CREATED

The workstation description record has been created and added to the workstation description database.

None.

None.

EQQW005E

DESCRIPTION BEING UPDATED BY USER USER, TRY LATER

You cannot update a workstation description that is being updated by another user.

The system waits for you to respond.

Try again later.

EQQW006E

DUPLICATE NAME - WORK STATION DESCRIPTION CANNOT BE CREATED

You have attempted to create a workstation description with a name that already exists in the workstation description database.

The system waits for you to respond.

Use another name for the workstation description.

EQQW007E

UNABLE TO READ WORK STATION DESCRIPTION RECORD

The workstation description record could not be read because either it may have been deleted by another user or an error in the workstation description database meant that it could not be read.

The system waits for you to respond.

Verify that the workstation description was not deleted or that it was correctly defined in the database. If the error persists, contact your system programmer.

EQQW008E

INCORRECT ENTRY, ENTER C OR N.

You entered a not valid value in the parallel server or resource usage field.

The request is rejected.

Correct your input. Valid values are C or N.

EQQW009E

INCORRECT ENTRY, ENTER P OR N.

You entered a not valid value in the server usage field.

The request is rejected.

Correct your input. Valid values are P or N.

EQQW010W

THE JCC INCIDENT FILE IS NOT AVAILABLE. ERROR CODE = ERRCODE

The job completion checker (JCC) incident log data set cannot be used. Valid values for the error code ERRCODE are:
001
No incident log data set name was defined in the JCCOPTS statement.
004
The incident log data set could not be allocated.
005
An unrecoverable error occurred writing to the incident work file.
006
The incident log data set could not be unallocated.
008
The incident log data set could not be opened.
009
The incident log work data set could not be opened.
012
An unrecoverable I/O error occurred whilst writing to the incident log or the incident work data set.

The JCC continues processing without creating any incident records.

Correct all errors and restart the JCC.

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

EQQW011I

THE EVENT WRITER ENDED NORMALLY

The intialization of the event writer has completed and the event writer has been requested to stop execution.

HCL Workload Automation for Z processing continues.

None.

EQQW012E

THE EVENT WRITER TERMINATED BECAUSE OF UNRECOVERABLE ERRORS

The initialization of the event writer has completed, but a severe error caused the event writer to stop execution.

The event writer terminates execution. Message EQQZ045W is issued.

Correct all errors and restart the event writer.

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

EQQW013E

DISK SPACE WAS EXHAUSTED ON JCC INCIDENT FILE, DDNAME = DDNAME

An end-of-volume error has been detected while writing to the incident log data set (ddname EQQINCFI) or the incident work data set (ddname EQQINCWK).

If the incident log data set is full, the job completion checker (JCC) continues logging to the incident work data set. If the incident work data set is full, the JCC issues message EQQW010W and stops writing incident log records.

If the incident log data set is full, either allocate a larger data set or release space in the current data set. If the incident work data set is full, make sure that the JCC can allocate the incident log data set. Empty the work data set by copying its contents to the incident log. Restart the JCC to continue incident logging.

EQQW014E

THE JCC TASK ABENDED WHILE PROCESSING THE FOLLOWING EXIT RECORD: EXITREC

An abend prevented the job completion checker (JCC) from processing all SYSOUT data sets for a batch job.

z/OS recovery/termination is requested to generate a dump. The JCC attempts to continue normal operation with the next ending job. The current job is put on the ended-in-error list with an error code of JCCE.

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

Review the SYSLOG data set, the HCL Workload Automation for Z message log data set, and the dump data set to determine the cause of the error.

EQQW015E

THE JOB COMPLETION CHECKER COULD NOT FIND ANY SYSOUT DATA SETS FOR JOB JOBNAME(JOBNUM). REPEATED RETRIES HAVE FAILED

The job completion checker (JCC) has tried to retrieve the SYSOUT data sets for a batch job but no data sets have been returned by the JES.

No more attempts to retrieve SYSOUT data sets are made for the current job. The JCC attempts to continue normal operation with the next ending job. The current job is put on the ended-in-error list with an error code of JCCE.

Determine the current status of the job. If necessary, set the correct status for the job manually.

If necessary, correct any incorrectly specified operands in the JCCOPTS statement and restart the JCC.

In a JES3 system, check that the JCC SYSOUT classes are defined as external writer classes to JES3. For both JES2 and JES3, ensure that the CHKCLASS sysout classes used are not being processed by a sysout archival product or JES offload. If using data store, ensure the classes are different from the ones specified in DSTCLASS keyword of RCLOPTS parameter.

EQQW016E

AN UNRECOVERABLE I/O ERROR OCCURRED. SYNAD MESSAGE FOLLOWS: SYNMSG

An I/O error occurred when the event writer was updating the event data set.

The event writer attempts to continue processing.

Correct all errors and, if necessary, restart the event writer.

The SYNAD routine collects information such as jobname, stepname, unit address, device type, ddname, operation, error description, and access method. The SYNADAF macro is used to extract this information. For a detailed description of the layout refer to the appropriate documentation for the MVS/DFP product installed on this system.

EQQW017E

THE EVENT WRITER WAS UNABLE TO OPEN THE EVENT DATA SET

The event writer could not open its output data set, ddname EQQEVDS.

The event writer issues message EQQW062E and is terminated.

If necessary, restart the event writer.

Check that ddname EQQEVDS is correctly specified and that the HCL Workload Automation for Z started task is authorized to open the data set for update.

EQQW018E

SYSOUT CLASS CLASS IS ALREADY BEING PROCESSED BY ANOTHER JCC TASK

A Job Completion Checker (JCC) task has been requested to process SYSOUT data sets in a SYSOUT class which is already being processed by another JCC task on the same MVS system. The SYSOUT class can only be processed by one JCC task at a time.

The initialization of the JCC is terminated.

Check the value of JCCOPTS and CHKCLASS of all HCL Workload Automation for Z subsystem started on the system. Correct the error and restart and restart the JCC task or the HCL Workload Automation for Z subsystem.

The JCC task uses the classes defined by the JCCOPTS CHKCLASS parameter. Check that on the same spool are not defined more JCC's using the same CHKCLASS values.

EQQW019E

A SEVERE ERROR IN THE JCC TASK HAS CAUSED ONE OR MORE EVENTS TO BE LOST

An abend in the job completion checker (JCC) queue processing routine prevented the JCC from processing all queued jobs.

z/OS recovery/termination is requested to generate a dump. The JCC attempts to continue processing.

Check the ready list for the computer workstation that is serviced by the abending JCC task. Check that all operations that have the started status are in fact executing. If necessary, set the correct status for jobs that are listed as started, but have completed execution.

Review the SYSLOG data set, the HCL Workload Automation for Z message log data set, and the dump data set to determine the cause of the error.

EQQW021E

THE EVENT WRITER OUTPUT DATA SET IS TOO SMALL

The event writer requires that the event data set is large enough to contain a minimum of 100 events. The data set defined by the ddname EQQEVDS does not fulfill this requirement.

The event writer processing is terminated. Message EQQW062E is issued.

Allocate a larger event data set. If necessary, restart HCL Workload Automation for Z to pick up the new event data set.

EQQW022I

THE JOB COMPLETION CHECKER ENDED NORMALLY

The initialization of the job completion checker (JCC) has completed and the JCC has been requested to stop execution.

HCL Workload Automation for Z continues processing.

None.

EQQW023E

UNEXPECTED SUBSYSTEM REQUEST RETURN CODES FOR JOB JOBNAME(JOBNUM) REQUEST TYPE: TYPE, R15: R15, SSOBRETN: SSOBRETN

An error occurred when the job completion checker (JCC) was retrieving information from the JES about job JOBNAME. The information request is either a status request (request type = CS) or a process SYSOUT request (request type = SO). R15 and SSOBRETN are return codes from JES. JCC issues this message because there is no code to handle this combination of return codes.

An incident record is written to the JCC incident log and the job is flagged as having encountered a JCC error.

Set the correct status for the job manually and, if necessary, delete or requeue SYSOUT data sets for the job.

EQQW024E

THE EVENT WRITER ABENDED WHILE PROCESSING THE FOLLOWING EXIT RECORD: EXITREC

An abend prevented the event writer from writing an event record to the event data set.

z/OS recovery/termination is requested to generate a dump. The event writer attempts to continue normal operation with the next queued event.

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

Review the SYSLOG data set, the HCL Workload Automation for Z message log data set, and the dump data set to determine the cause of the error.

EQQW025W

THE EVENT WRITER HAS IGNORED THE FOLLOWING INVALID EXIT RECORD: EXITREC

An invalid event record EXITREC has been found by the event writer. The most likely reason is that the last four bytes of the record do not contain the HCL Workload Automation for Z character string EQQ3. It is also possible that the first three characters of the job ID field do not contain the character string JOB.

If the last four bytes of the record contain the character string ERA2, an abend has occurred during the event creation, and the event contains the following information:
EXRJOBN
Name of the abending CSECT
EXRJOBID
Compile date of the abending CSECT
EXRCREAT
Compile time of the abending CSECT
EXRRDATE+1
Abend code (from SDWACMPC)
EXRRTIME
Offset in CSECT at which the abend occurred
If the last four bytes of the record contain the character string ERU2, the event creation has been called by an unsupported exit, and the event contains the following information:
EXRJOBN
Name of the unsupported exit.
Refer to the Diagnosis Guide and Reference for details of the EXR control block.

The event writer terminates processing of the event, but continues normal processing. If the invalid event was of the ERA2 or ERU2 type (see previous explanations), the events are created only if a minimum of five minutes have passed since the last creation of the same type.

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

If the message is issued for all events (in which case the event data set is empty), check that the EQQSSCMx module and the event writer are at the same release level.

EQQW026I

THE JOB COMPLETION CHECKER STARTED

The initialization of the job completion checker (JCC) has completed and the JCC is about to start processing.

HCL Workload Automation for Z processing continues.

None.

EQQW027E

THE JOB COMPLETION CHECKER TERMINATED DUE TO UNRECOVERABLE ERRORS

An abend has occurred in the job cpmpletion checker (JCC) task that is not related to the processing of any specific job.

z/OS recovery/termination is requested to generate a dump. The JCC processing is terminated.

Correct all errors and restart the JCC.

Review the SYSLOG data set, the HCL Workload Automation for Z message log data set, and the dump data set to determine the cause of the error.

EQQW028E

JOB COMPLETION CHECKER INITIALIZATION FAILED

The job completion checker (JCC) could not acquire all resources required for normal operation. The most likely reason is that either the JCC message library could not be opened or the library is incorrectly defined. It is also possible that there was an error in the JCCOPTS statement.

The JCC processing is terminated. Message EQQZ045W is issued.

Correct all errors and restart the JCC.

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

EQQW029E

JCC FOUND INVALID NUMERICS BETWEEN COLUMNS BCOL AND ECOL IN MEMBER MEMBER IN THE EQQJCLIB MESSAGE TABLE FILE. INCORRECT RECORD FOLLOWS: MSGREC

A message table record contains invalid information and cannot be used.

The job completion checker (JCC) does not use the incorrect message library member. If the member name is EQQGJCCT, message EQQW063E is issued. In all other cases, the JCC continues processing.

Correct the message table definition error and replace member MEMBER in the EQQJCLIB message table data set.

EQQW030I

A DISK DATA SET WILL BE FORMATTED, DDNAME = DDNAME

HCL Workload Automation for Z has started to format an event data set or a submit/release data set for the ddname DDNAME.

HCL Workload Automation for Z continues processing.

None.

EQQW031E

JCC ALLOCATION OF A SYSOUT DATA SET FAILED FOR JOBNAME(JOBNUM) DYNAMIC ALLOCATION ERROR CODE: RETC, INFORMATION REASON CODE: RSNC

The job completion checker (JCC) could not allocate a SYSOUT data set for the job JOBNAME(JOBNUM). The dynamic allocation error and information reason codes are given in hexadecimal.

An incident record is written to the JCC incident log and the job is flagged as having encountered a JCC error. The JCC stops processing the current job.

Check that the correct status is set for the job. If necessary, set the status manually.

Look up the meaning of the dynamic allocation error and information reason codes, and take appropriate action.

Use the DYNALLOC return code and reason code to determine the cause of the error. For more information, refer to the appropriate DYNALLOC documentation for the currently active z/OS system.

EQQW032E

THE JOB COMPLETION CHECKER LIBRARY, DDNAME EQQJCLIB, COULD NOT BE OPENED

The job completion checker (JCC) could not open a required input data set, ddname EQQJCLIB.

The JCC processing is terminated. Message EQQW028E is issued.

If necessary, restart the JCC.

Check that EQQJCLIB is correctly defined and that the HCL Workload Automation for Z started task is authorized to open the data set.

EQQW033W

JOB JOBNAME(JOBNUM) WILL NOT BE RELEASED. REPEATED RETRIES HAVE FAILED

The event writer has received a release command on a submit/release data set and was not able to release job JOBNAME(JOBNUM) from hold status.

No more attempts to release the job are made. The event writer continues processing.

Determine the current status of the job. If necessary, release the job manually.

EQQW034E

LRECL FOR THE JOB COMPLETION CHECKER LIBRARY, DDNAME EQQJCLIB, IS NOT VALID

The job completion checker (JCC) cannot use the message table library data set because its logical record length is not 80 bytes.

The JCC processing is terminated. Message EQQW028E is issued.

Check that EQQJCLIB is correctly defined. Correct all errors and restart the JCC.

EQQW035E

JCC UNALLOCATION OF A SYSOUT DATA SET FAILED FOR JOBNAME(JOBNUM) DYNAMIC ALLOCATION ERROR CODE: RETC, INFORMATION REASON CODE: RSNC

An error occurred when the job completion checker (JCC) was deallocating a SYSOUT data set for the job JOBNAME(JOBNUM). The dynamic allocation error and information reason codes are given in hexadecimal.

An incident record is written to the JCC incident log and the job is flagged as having encountered a JCC error. The JCC stops processing the job.

Check that the correct status is set for the job. If necessary, set the status manually.

Use the DYNALLOC return code and reason code to determine the cause of the error. For more information, refer to the appropriate DYNALLOC documentation for the currently active z/OS system.

EQQW036E

JCC OPEN OF A SYSOUT DATA SET FAILED FOR JOBNAME(JOBNUM) DDNAME: DDNAME, DSNAME: DSNAME

An error occurred when the joc completion checker (JCC) was trying to open a SYSOUT data set for the job JOBNAME(JOBNUM).

An incident record is written to the JCC incident log and the job is flagged as having encountered a JCC error. The JCC stops processing the job.

Check that the correct status is set for the job. If necessary, set the status manually.

Determine the reason for the JCC open failure. Correct all errors.

EQQW037E

JCC ABEND CODE ABCODE OPENING A SYSOUT DATA SET FOR JOBNAME(JOBNUM) DDNAME: DDNAME, DSNAME: DSNAME

A serious error occurred when the job completion checker (JCC) was trying to open a SYSOUT data set for the job JOBNAME(JOBNUM).

An incident record is written to the JCC incident log and the job is flagged as having encountered a JCC error. The JCC stops processing the job.

Check that the correct status is set for the job. If necessary, set the status manually.

Determine the reason for the abend. Correct all errors.

EQQW038I

A DISK DATA SET HAS BEEN FORMATTED, DDNAME = DDNAME

HCL Workload Automation for Z has finished formatting an event data set or a submit/release data set for the ddname DDNAME.

HCL Workload Automation for Z continues processing.

None.

EQQW039E

JCC FOUND BAD HEXADECIMAL VALUE BETWEEN COLUMNS BCOL AND ECOL IN MEMBER MEMBER IN THE EQQJCLIB MESSAGE TABLE FILE. INCORRECT RECORD FOLLOWS: MSGREC

A message table record contains invalid information and cannot be used.

The job completion checker (JCC) does not use the incorrect message library member. If the member name is EQQGJCCT, message EQQW063E is issued. In all other cases, the JCC continues processing.

Correct the message table definition error and replace member MEMBER in the EQQJCLIB message table data set.

EQQW040W

JOB JOBNAME(JOBNUM) WILL NOT BE RELEASED. RELEASE RECORD IS TOO OLD

The event writer found a release request in a submit/release data set that could not be executed. The reason is that the request was older than the limit defined to the event writer by the SKIPTIME and SKIPDATE keywords in the EWTROPTS statement.

The event writer continues reading the submit/release data set.

If necessary, set the correct status for the job manually.

EQQW041W

JCL BATCH WITH FIRST JOB JOBNAME WILL NOT BE SUBMITTED BECAUSE SUBMIT RECORD IS TOO OLD

The event writer found job submit records in a submit/release data set that could not be processed. The reason is that the records were older than the limit defined to the event writer by the SKIPTIME and SKIPDATE keywords in the EWTROPTS statement.

The event writer continues reading the submit/release data set.

If necessary, resubmit the job.

EQQW042W

JCL BATCH WITH FIRST JOB JOBNAME WILL NOT BE SUBMITTED BECAUSE THE EVENT WRITER DID NOT RECEIVE ALL SUBMIT RECORDS

The event writer found job submit records in a submit/release data set that could not be processed because some submit records were missing.

The event writer continues reading the submit/release data set.

If necessary, resubmit the job.

Check that only one HCL Workload Automation for Z subsystem is updating this submit/release data set.

EQQW043E

THE EVENT WRITER WAS UNABLE TO OPEN THE SUBMIT/RELEASE DATA SET

The event writer could not open its input data set, ddname EQQSUDS.

The event writer issues message EQQW062E and is terminated.

If necessary, restart the event writer.

Check that ddname EQQSUDS is correctly defined and that the HCL Workload Automation for Z started task is authorized to open the data set.

EQQW044E

UNEXPECTED ERROR SUBMITTING JOB JOBNAME TO THE JES INTERNAL READER

An error occurred when submitting the job JOBNAME to the JES.

HCL Workload Automation for Z continues processing.

If necessary, submit the job manually.

EQQW045W

JCL BATCH WITH FIRST JOB JOBNAME WILL NOT BE SUBMITTED BECAUSE SUBMIT RECORDS WERE RECEIVED IN INCORRECT ORDER BY THE EVENT WRITER

The event writer found job submit records in a submit/release data set that could not be processed because the records were not in sequence.

The event writer continues reading the submit/release data set.

If necessary, resubmit the job JOBNAME.

Check that only one HCL Workload Automation for Z subsystem is updating this submit/release data set.

EQQW046E

SEQUENCE NUMBER SEQNO IS ALREADY IN USE BY AN EVENT READER SUBTASK

At initialization of the event writer, an event reader was already started with the sequence number specified in the EWSEQNO keyword of EWTROPTS.

The number specified in the EWSEQNO keyword of EWTROPTS must be unique within the HCL Workload Automation for Z subsystem.

The initialization of the event writer fails. The event writer task is terminated.

Review the ERSEQNO keyword of the ERDROPTS initialization statements to get a sequence number that is unused. Update the EWSEQNO keyword with a unique sequence number and use the HCL Workload Automation for Z Modify command to restart the event writer task.

EQQW047W

SUBMIT/RELEASE RECORDS WERE LOST BECAUSE THE SUBMIT/RELEASE DATA SET BECAME FILLED WITH UNPROCESSED RECORDS

The event writer could not process records in a submit/release data set as fast as the sending HCL Workload Automation for Z subsystem was generating them.

The event writer tries to reposition on the oldest record in the data set.

Determine if any held jobs should be released and, if so, release them manually. Resubmit all missing jobs.

Allocate a larger submit/release data set and restart the event writer.

EQQW048E

THE EVENT FILTERING EXIT, EQQUX004, ABENDED AND HAS BEEN DISABLED

An abend in the event filtering exit prevented the event writer from writing an event record to the event data set.

z/OS recovery/termination is requested to generate a dump. The event writer attempts to continue normal operation with the next queued event, but the event filtering exit is not called again.

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

Correct all errors and restart the event writer.

Review the SYSLOG data set, the HCL Workload Automation for Z message log data set, and the dump data set to determine the cause of the error.

EQQW049E

UNABLE TO FORMAT DATA SET WITH DDNAME DDNAME BECAUSE THE DATA SET IS NOT A SINGLE EXTENT, DISK RESIDENT, DATA SET

HCL Workload Automation for Z was unable to format an event data set or a submit/release data set for the ddname DDNAME. A data set to be formatted must be a disk resident, single extent data set.

The HCL Workload Automation for Z function that uses the data set fails to initialize correctly.

None.

Correct the HCL Workload Automation for Z started task procedure and restart HCL Workload Automation for Z.

EQQW051E

JOB JOBNAME COULD NOT BE SUBMITTED. REASON: AUTHORITY FOR RUSER USER, SUPPLIED BY USER EXIT EQQUX001, COULD NOT BE DETERMINED

A user ID was supplied by the submit exit, EQQUX001, and the job was then sent using the submit/release data set to the DRVP macro. The buffer pool was successfully built.

The job is not submitted and HCL Workload Automation for Z continues normal processing.

Make sure that the supplied user ID is defined to the external security manager.

EQQW052E

THE EVENT DATASET, DDNAME DDNAME, LRECL BLKSZ IS INVALIDLY DEFINED. DATASET IS NOT USABLE

The event data set referenced by ddname DDNAME has been allocated with an invalid logical record length.

The initialization of the event writer fails.

Stop HCL Workload Automation for Z, reallocate the data set and restart HCL Workload Automation for Z.

An event data set must have a logical record length (LRECL) not less than 100 and not greater than 32000. Check that the LRECL is within the supported range.

EQQW053E

THE SYSOUT ARCHIVING EXIT, EQQUX005, ABENDED AND HAS BEEN DISABLED

The sysout archiving exit, EQQUX005, abended while processing a job's SYSOUT data set. HCL Workload Automation for Z has disabled the exit for this type of function for the remainder of the HCL Workload Automation for Z session.

z/OS recovery/termination is requested to generate a dump. The exit is not called again for this particular function, but HCL Workload Automation for Z continues processing.

Correct the error and, if necessary, restart the job completion checker (JCC) task using the modify commands or restart the Tivoli OPC tracker.

Review the SYSLOG data set, the HCL Workload Automation for Z message log, and the dump data set to determine the cause of the error.

EQQW056W

JOBNAME JOBNUM HAS NO HELD SYSOUT IN CLASS CLASS

The CATMCLAS keyword specifies the SYSOUT class CLASS, but job JOBNAME with job ID JOBNUM created output that is not held in this class.

The job is tracked as normal, but the job log cannot be sent to the controller.

Make sure that the CATMCLAS keyword specifies only held SYSOUT classes.

If the job-log output for the job is a held SYSOUT class, make sure the most current EQQSSCMx lmod is active (see the SSCMNAME parameter).

EQQW058W

JES CLASS CLASS WAS DEFINED BOTH FOR JCC AND DATASTORE PROCESSING: STRUCTURE JOBLOG DATA FOR DATASTORE MAY BE LOST.

The same class has been defined in the CHKCLASS keyword in the JCCOPTS statement and in the DSTCLASS keyword in the RCLOPTS statement.

The job is tracked as normal, but the joblog data for datastore may be lost.

Change CHKCLASS keyword for DSTCLASS keyword to avoid the risk of losing the joblog data.

Refer to the explanation of the DSTCLASS keyword in Customization and Tuning.

EQQW059E

WRONG HEADER IN END-TO-END EVENTS DATASET, DDNAME = DDNAME

The End-to-End events data set specified by DDNAME has a wrong header.

The controller initialization fails.

Specify the correct data set in the DDNAME and restart the controller.

EQQW060E

SUBMIT/RELEASE SKIP LIMIT DATE OR TIME SKIPLIM IS NOT VALID

Initialization of the event writer failed because an operand of the SKIPDATE or SKIPTIME keyword in the EWTROPTS statement was incorrectly specified.

The event writer processing is terminated.

Correct the operand in the EWTROPTS statement and restart the event writer.

None.

EQQW061W

THE EVENT FILTERING EXIT LOAD MODULE, MODULE, COULD NOT BE LOADED

The event writer could not locate the event filtering exit load module, EQQUX004.

The event filtering exit is not used by the event writer.

If the event filtering exit is meant to be used, make sure that the EQQUX004 load module is present in a library that can be reached by HCL Workload Automation for Z. Correct all errors and, if necessary, restart the event writer.

None.

EQQW062E

EVENT WRITER INITIALIZATION FAILED

The event writer could not acquire all resources required for normal operation. The most likely reason is that the event data set or a submit/release data set could not be opened. It is also possible that there was an error in the EWTROPTS statement.

The event writer processing is terminated. Message EQQZ045W is issued.

Correct all errors and restart the event writer.

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

EQQW063E

THE JOB COMPLETION CHECKER WAS UNABLE TO BUILD THE GENERAL MESSAGE TABLE

An error occurred while processing the general message table for the job completion checker (JCC). The general message table is defined by member EQQGJCCT in the library defined by the EQQJCLIB DD statement.

The initialization of the JCC fails.

Correct all errors and restart the JCC.

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

EQQW064E

THE JOB COMPLETION CHECKER WAS UNABLE TO BUILD THE JOB MESSAGE TABLE FOR JOB JOBNAME(JOBNUM)

An error occurred while processing the message table for the specified job in the job completion checker (JCC). The job message table is defined by member JOBNAME in the library defined by the EQQJCLIB DD statement.

An incident record is written to the JCC incident log and the job is flagged as having encountered a JCC error.

Set the correct status for the job manually and, if necessary, delete or requeue SYSOUT data sets for the job.

Correct all errors in the job message table.

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

EQQW065I

EVENT WRITER STARTED

The initialization of the event writer has completed and the event writer is now about to start processing.

HCL Workload Automation for Z continues processing.

None.

EQQW066E

JCC WAS UNABLE TO ALLOCATE STORAGE TO PROCESS MEMBER MEMBER OF EQQJCLIB

An error occurred when allocating storage for a job message table.

Message EQQW064E is issued.

Stop HCL Workload Automation for Z and restart it in a larger region.

None.

EQQW067E

A SEVERE ERROR IN THE EVENT WRITER HAS CAUSED LOSS OF CSA EVENT BUFFERS

An abend in the queue processing routine of the event writer prevented the event writer from returning all event buffers to the free chain.

z/OS recovery/termination is requested to generate a dump. The event writer attempts to continue processing.

None.

Review the SYSLOG data set, the HCL Workload Automation for Z message log data set, and the dump data set to determine the cause of the error.

EQQW068E

JCC WAS UNABLE TO FIND MEMBER MEMBER IN EQQJCLIB MESSAGE TABLE FILE

The general message table member MEMBER of the job completion checker (JCC) could not be found in the library defined by the EQQJCLIB DD statement.

Message EQQW063E is issued.

Create a general message table member for the JCC and add it to the EQQJCLIB library.

EQQW069E

MEMBER MEMBER IN EQQJCLIB MESSAGE TABLE FILE IS EMPTY

The general message table member MEMBER of the job completion checker (JCC) exists in the library defined by the EQQJCLIB DD statement, but there are no records in the member.

If the member name is EQQGJCCT, message EQQW063E is issued. If not, the JCC continues processing.

If necessary, add the correct message table member to the EQQJCLIB library.

EQQW070I

THE EW CANNOT REPOSITION AT RESTART POSITION: CYCREC

An event writer is started in event reader mode (with an EWSEQNO). The event writer cannot position on the event data set with the event data set position that it has received. The restart position was probably overwritten when the event data set wrapped around.

The event writer continues normal processing.

The event data set may be too small. Make sure that it is large enough to hold all the generated events when the connection between the controller and the tracker with the started event writer is down.

EQQW071I

UNKNOWN RECORD TYPE SKIPPED BECAUSE IT IS TOO OLD

The event writer encountered an unknown record type when skipping records of the submit/release data set that are too old.

The record is skipped.

None.

EQQW072E

EVENT WRITER SEQUENCE NUMBER, EWSEQNO, MUST BE 1 TO 16

An invalid sequence number was found in the EWSEQNO keyword of the initialization statement for an event writer.

HCL Workload Automation for Z initialization is terminated.

Change the sequence number to a number within the range 1 to 16 that is not already used by an event reader task in the same address space.

EQQW073E

IT IS NOT VALID TO START AN EVENT WRITER IN EVENT READER MODE WITH THIS TYPE OF HOST CONNECTION

The HCL Workload Automation for Z configuration does not support starting an event writer in event reader mode. When the event writer is started with the EWSEQNO, it tries to pass events directly to the controller. EWSEQNO can only be used in these circumstances:
  • The event writer is started in the same address space as the controller.
  • XCF connections. The event writer is started at a tracker system connected to the controller using XCF communication links.
  • SNA connections. The event writer is started at a tracker system connected to the controller using VTAM.

The initialization of the event writer is terminated.

Remove the EWSEQNO keyword from the EWTROPTS initialization statement.

EQQW074E

THE SUBMIT/RELEASE DATA SET WITH DDNAME = DDNAME IS TOO SMALL

The submit/release data set must be large enough to contain 100 records.

The workstation analyzer processing stops. Message EQQW502E is issued.

Stop HCL Workload Automation for Z, allocate a larger submit/release data set, and restart HCL Workload Automation for Z.

None.

EQQW075W

THE HEADER RECORD IN FILE DDNAME IS INCOMPATIBLE WITH THE DEVICE TYPE

The information in the header record does not match the calculated records per tracks value. Normally this is caused by moving the data set to a different device type.

Note: This message may be issued if you have reallocated the data set using a method that does not put an end of file at the beginning of the data set. It can then be ignored.

The data set is reformatted.

None.

EQQW076W

NO CONTROLLER PULSE. EVENT WRITER WILL STOP PULSE DETECTION

There are two situations that can cause this message to be issued:
  1. When handshake processing is in use, each connected tracker system sends an identification (ID) event to the controller at the specified interval defined by the ROUTOPTS PULSE keyword, and the controller responds to the tracker system. This message is issued if the tracker detects that the controller has not responded to two consecutive ID events. In the case of a SHARED-DASD-connected tracker, this indicates that either there is a problem in the controller address space or the communication vehicle has failed.
  2. When a tracker is started in a separate address space and is not receiving work from the controller, the tracker waits for two default intervals (2 x 10 minutes) and issues this message.

The event writer task stops sending handshake events.

In the case of a SHARED-DASD-connected tracker, verify if the Scheduler controller address space is active and check the message log data set for error messages or communication failures. If required, restart the controller. For any other configuration where the connection between tracker and controller is NCF or XCF, or where the tracker issuing this message has a blank destination ID, the message can be ignored.

EQQW077E

THE SUBMIT/RELEASE DATASET IS NOT INITIALIZED

A HCL Workload Automation for Z tracker system tried to update the submit/release data set, ddname EQQSUDS, but the data set is not initialized by the controller. This message is issued only when starting with a new submit/release data set.

The initialization of the event writer fails and the task is terminated.

Stop the tracker and start the controller so as to initialize the submit/release data set.

EQQW079W

JBNAM WILL NOT BE SUBMITTED TO WLM FOR PROMOTION. WLM REQUEST IS TOO OLD

The event writer found a record for WLM job promotion in the submit/release data set that could not be executed. The reason is that the request is older than the limit defined to the event writer by the SKIPTIME and SKIPDATE keywords in the EWTROPTS statement.

The event writer continues reading the submit/release data set.

EQQW081W

THE ROUTINE TO SEND EVENTS TO FTW COULD NOT BE LOADED

The scheduler could not locate the subsystem routine used to send events to an FTW (fault-tolerant workstation).

The scheduler ABENDs.

Ensure that the EQQZTWE load module is present in the scheduler library.

The scheduler could not be installed correctly.

EQQW082E

THE END-TO-END TASK WAS UNABLE TO OPEN AN END-TO-END DATA SET

The end-to-end task could not open one of its event data sets (end-to-end input/output queue).

The subtasks of the end-to-end task issues message EQQW083I and terminates.

If necessary, restart the subtasks of the end-to-end task.

Check that DDNAME EQQTWSIN/EQQTWSOU is correctly specified and that the scheduler started task is authorized to open the data set for update.

EQQW083I

SSNAME EQQTWSIN/EQQTWSOU ERRCODE ERROR: ERRMSG

An error occurred in the TWS enabler event data sets:
SSNAME
is the name of the scheduler subsystem
ERRCODE
is the code of the error.
ERRMSG
the cause of the error.

The subtask of the end-to-end task issues a message terminated. Problem determination: Check that EQQTWSIN/EQQTWSOU is correctly specified, the task is authorized to open the data set for update and the data sets are correctly allocated.

Check the status of the TWS enabler data sets. If necessary, restart the subtask of the end-to-end task.

Check that EQQTWSIN/EQQTWSOU is correctly specified, the task is authorized to open the data set for update and the data sets are correctly allocated.

EQQW084E

THE EVENT DATASET, DDNAME DDNAME, LRECL BLKSZ IS INVALID. THE DATASET CANNOT BE USED. VALID RANGE IS FROM 160 TO 32000.

The data set referenced by DDNAME DDNAME has been allocated with an invalid logical record length. The minimum record length allowed is 160 and the maximum is 32000.

If the message is issued for an end-to-end event data set (EQQTWSOU and EQQTWSIN), the subtask of the end-to-end task issues the message EQQW083I and terminates. If the message is issued for the output collector event data set (EQQOUCEV), the event manager issues the message EQQE143E and joblogs for jobs that run on z-centric and dynamic agents are not collected or written to JES.

Reallocate the data set and, if the message is issued for
  • An end-to-end event data set, restart the subtask of the end-to-end task.
  • The output collector event data set, restart the controller.

The data set must have a logical record length (LRECL) in the range 160 to 32000. Check that the LRECL is within the supported range.

EQQW085E

THE EVENT DATASET, DDNAME DDNAME, IS TOO SMALL

The data set referenced by DDNAME DDNAME must be allocated to contain at least 1000 events. The data set does not meet this requirement.

If the message is issued for an end-to-end event data set (EQQTWSOU and EQQTWSIN), the subtask of the end-to-end task issues the message EQQW083I and terminates. If the message is issued for the output collector event data set (EQQOUCEV), the event manager issues the message EQQE143E and joblogs for jobs that run on the z-centric and dynamic agents are not collected or written to JES.

Reallocate the data set and, if the message is issued for
  • An end-to-end event data set, restart the subtask of the end-to-end task.
  • The output collector event data set, restart the controller.

EQQW086E

ERROR IN TASK SUBTASK OF END-TO-END ENABLER TASK, IN MODULE MODULE DURING A FUNCTION FUNCTION (ERROR CODE = ERRCODE)

An error occured in the subtask of the end-to-end TASK in module MODULE performing the FUNCTION function. The error code is ERRCODE

The subtask of the end-to-end task continue the processing.

If the error code is different from zero, save the message log data set (EQQMLOG) containing this error message and contact the Software Support.

EQQW087E

THE END-TO-END TASK WAS UNABLE TO OPEN AN EVENTS DATA SET

The end-to-end task could not open one of its event data sets (end-to-end input/output queue).

The subtask of the end-to-end task terminates.

If necessary, restart the subtask of the end-to-end task.

Check that DDNAME EQQTWSIN/EQQTWSOU is correctly specified and that the scheduler started task is authorized to open the data set for update.

EQQW088W

THE END-TO-END QUETYPE QUEUE UTILIZATION HAS EXCEEDED THRESHOLD VALUE PERCENT % OF END-TO-END QUETYPE QUEUE IN USE

The END-TO-END QUETYPE queue is used for PERCENT %. This could be dangerous for the events loss.

The subtasks of the end-to-end task continue processing.

Start the end-to-end server and the end-to-end task. lf the problem persists, the QUETYPE queue (DDNAME EQQTWSIN/EQQTWSOU) might be too small and should be increased. If so, stop the end-to-end server and the end-to-end task, reallocate the QUETYPE queue and restart the server and the TWS enabler.

Check that the end-to-end server and the subtasks of the end-to-end task (sender and receiver task) are running correctly. If so, the QUETYPE queue (DDNAME EQQTWSIN/EQQTWSOU) might be too small.

EQQW089W

THE END-TO-END QUETYPE QUEUE IS FULL. 100% OF TWS QUETYPE QUEUE IN USE

The END-TO-ENDQUETYPE queue is 100% full. This could cause event loss.

The subtasks of the end-to-end task continue processing.

Start the end-to-end server and the end-to-end task. lf the problem persist then the QUETYPE queue (DDNAME EQQTWSIN/EQQTWSOU) might be too small and should be increased. If so,stop the end-to-end server and the end-to-end task, reallocate the QUETYPE queue and restart server and the TWS enabler.

Check that the end-to-end server and the subtasks of the end-to-end task (sender and receiver task) are running correctly. If so, the QUETYPE queue (DDNAME EQQTWSIN/EQQTWSOU) could be too small.

EQQW090I

THE NEW SYMPHONY FILE HAS BEEN SUCCESSFULLY SWITCHED

The Translator process has successfully switched the new Symphony File.

The new Symphony file is sent to fault-tolerant workstations and used for scheduling on distributed agents.

None.

EQQW091E

THE NEW SYMPHONY FILE CANNOT BE SWITCHED

The Translator was unable to switch the new Symphony file.

The Translator waits until a new Symphony is available. Scheduling on distributed agents does not start.

Check the MLOG server to see which error is preventing the Translator process from using the new Symphony. Correct the problems and run Symphony Renew to create a new Symphony.

EQQW092E

ERROR SENDING SCRIPT FOR OPERATION OP1NUM IN OCCURRENCE OCCNAME WITH OCCURRENCE TOKEN APP1TOK

The submission of operation OP1NUM in occurrence OCCNAME failed. The operation has a centralized script and an error occurred while sending the script: The sender task was unable to write the script in the EQQTWSCS data set.

The task tries to submit the job again.

Refer to messages EQQW093, EQQW094, or EQQW095 for a possible cause of the error and correct it.

EQQW093E

EQQTWSCS OPENING FAILED

The task is unable to open the PDSE specified by ddname EQQTWSCS.

The task continues its own processing, but the submission of jobs with centralized scripts is jeopardized.

Check that ddname EQQTWSCS is correctly defined.

EQQW094E

EQQTWSCS INVALID RECORD LENGTH

The task is unable to open the PDSE specified by ddname EQQTWSCS because of an incorrect record length.

The task continues its own processing, but the submission of jobs with centralized scripts is jeopardized.

Check that ddname EQQTWSCS is correctly defined and that the specified data set is allocated as described in the installation guide.

EQQW095E

ERROR IN MACRO STOW: RC=RETCODE, RSN=RSNCODE

An error occurred while sending a script to an agent for an operation that uses a centralized script; this message always follows message EQQW092E. The sender task caused an error while writing in the EQQTWSCS data set. The return code and the reason code of the macro STOW are reported.

The task tries to submit the job again.

Refer to the DFSMS Macro Instructions for Data Sets manual to find the cause of the error and correct it.

EQQW096E

A COMPLETE SYNCHRONIZATION BETWEEN END-TO-END RECEIVER AND EVENT MANAGER IS NOT POSSIBLE. NUMLOSTEVENTS HAVE BEEN LOST

When initializing, the Event Manager asks the End-to-End Receiver for synchronization. The events already sent by End-to-End Receiver to Event Manager, but unprocessed by it, should be sent again to the Event Manager. If events to be re-sent are no more present in EQQTWSIN data set, a complete synchronization is not possible, and numlost events are lost.

The End-to-End Receiver continues synchronizing with the Event Manager, reprocessing the events still present in the EQQTWSIN data set.

Check inside the controller MLOG for possible EQQE110W and EQQE111W messages.

EQQW097I

END-TO-END RECEIVER STARTED SYNCHRONIZATION WITH THE EVENT MANAGER. NUM EVENTS IN EQQTWSIN WILL BE REPROCESSED

When initializing, the Event Manager asks the End-to-End Receiver for synchronization. num events already sent by the Receiver to the Event manage,r but unprocessed by it, will be sent again. If Event Manager and End-to-End Receiver are synchronized, zero events will be reprocessed.

The End-to-End Receiver starts reprocessing num events.

None.

EQQW098I

END-TO-END RECEIVER FINISHED SYNCHRONIZATION WITH THE EVENT MANAGER

When initializing, the Event Manager asked the End-to-End Receiver for synchronization. Now the End-to-End receiver has finished synchronizing with the Event Manager.

The End-to-End Receiver continues with its normal processing.

None.

EQQW099I

END-TO-END RECEIVER ACTION WAITING FOR THE EVENT MANAGER TO BECOME ACTIVE

End-to-End Receiver must read events from the EQQTWSIN data set only if the Event Manager is active. If the action is STARTED, the Event Manager is no more active and so the End-to-End Receiver is in a waiting status until it receives a stop request, or the Event Manager is active again. If the action is STOPPED, the Event Manager has become active, so the End-to-End Receiver can continue with its normal processing.

None.

None.

EQQW100E

WORK STATION NAME IS NOT DEFINED OR IT IS INVALID

Data entry error; see Data entry errors.

You entered an incorrect value. The first character must be an alphabetic character.

EQQW101E

WORK STATION TYPE IS NOT DEFINED OR IT IS INVALID

Data entry error; see Data entry errors.

You entered an incorrect value. Valid workstation types are: G for general, C for computer, and P for printer workstation.

EQQW102E

WORK STATION REPORTING ATTRIBUTE INVALID OR NOT DEFINED

Data entry error; see Data entry errors.

You entered an incorrect value. Valid workstation reporting attributes are:
A
Automatic. Reporting is done by a user program for both start and completion of an operation, for example, a computer workstation.
S
Manual start and completion. The workstation operator reports when work is started and when it is completed, for example, a data entry workstation.
C
Manual completion only. The workstation operator reports only when work is completed, for example, a login workstation.
N
Nonreporting. The workstation does not report on work.

EQQW103E

WORK STATION SYSOUT ROUTING INVALID OR NOT DEFINED

Data entry error; see Data entry errors.

You entered an incorrect value. Specify a correct value and proceed with the operation.

EQQW104E

CONTROL ON PARALLEL SERVERS INVALID OR NOT DEFINED

Data entry error; see Data entry errors.

You entered an incorrect value. The valid input for control on parallel servers is: C for control, P for planning, B for both planning and control, or N for none.

EQQW105E

JOB INTERRUPTION ATTRIBUTE INVALID OR NOT DEFINED

Data entry error; see Data entry errors.

You entered an incorrect value. Valid job interruption attributes are Y for yes and N for no.

EQQW106E

JOB SETUP ATTRIBUTE IS NOT DEFINED OR IT IS INVALID

Data entry error; see Data entry errors.

You entered an incorrect value. Valid job setup attributes are Y for yes and N for no.

EQQW107E

DESTINATION IS NOT DEFINED OR IT IS INVALID

Data entry error; see Data entry errors.

You entered an incorrect value. You can specify a destination only for a computer workstation. Enter a valid destination.

EQQW108E

VALID WORK STATION TYPES ARE WSYPG, WSTYPC, WSTYPP, WSTYPR

Data entry error; see Data entry errors.

You entered an incorrect value. Valid workstation types are: WSTYPG is the national language character for 'G' (general workstation), WSTYPC is for 'C' (computer workstation), and WSTYPP is for 'P' (printer workstation), WSTYPR is for 'R' (remote engine workstation) .

EQQW109E

GENERAL OR PRINTER REQUIRED FOR JOB SPLITTABLE

Data entry error; see Data entry errors.

You entered an incorrect value. You can split only a job on a general or printer workstation. You cannot split a job on a computer workstation.

EQQW110E

JOB SETUP ALLOWED ONLY IF WORK STATION TYPE IS GENERAL

Data entry error; see Data entry errors.

You entered an incorrect value. Job setup is allowed if the workstation type is general, but not if the workstation type is computer or printer.

EQQW111E

WORK STATION RESOURCE NAME INVALID OR NOT DEFINED

Data entry error; see Data entry errors.

You entered an incorrect value. Enter a valid workstation name.

EQQW112E

A PLANNING ATTRIBUTE IS REQUIRED, SPECIFY EITHER Y OR N

Data entry error; see Data entry errors.

You did not enter a required value. Specify either Y or N and proceed with the operation.

EQQW113E

A CONTROL ATTRIBUTE IS REQUIRED, SPECIFY EITHER Y OR N

Data entry error; see Data entry errors.

You did not enter a required value. Specify either Y or N and proceed with the operation.

EQQW114E

WORK STATION OPEN INTERVAL INVALID OR NOT DEFINED

Data entry error; see Data entry errors.

You entered an incorrect value. Enter a valid workstation open interval and proceed with the operation.

EQQW115E

VALID ATTRIBUTES ARE OWSDATTA, OWSDATTS, OWSDATTC, OWSDATTN

Data entry error; see Data entry errors.

You entered an incorrect value. Valid values are: OWSDATTA is the national language character for 'A' (automatic workstation reporting), OWSDATTS is for 'S' (manual start/stop), OWSDATTC is for 'C' (completion only), and OWSDATTN is for 'N' (nonreporting).

EQQW116E

COMPUTER OR REMOTE ENGINE MUST BE SPECIFIED IF DESTINATION DEFINED

Data entry error; see Data entry errors.

You did not enter a required value. Specify the required value and proceed with the operation.

EQQW117E

WORK STATION NAME IS NOT DEFINED OR IT IS INVALID

Data entry error; see Data entry errors.

You entered an incorrect value. Specify a correct value and proceed with the operation.

EQQW118E

NO DESCRIPTION IS ALLOWED WHEN STATUS IS STANDARD

Data entry error; see Data entry errors.

You entered an incorrect value. Only days that have status closed or defined can have an entry in the description field.

EQQW119E

IF AUTOMATION IS YES, GENERAL AND AUTOMATIC MUST BE ALSO SPECIFIED

If Automation is Yes, the workstation must be of type General and Automatic reporting.

You did not specify a required value. Specify a workstation of type General and Automatic reporting.

EQQW120E

ENGINE TYPE MUST BE Z OR D

Data entry error; see Data entry errors.

You entered an incorrect value. Specify Z or D and proceed with the operation.

EQQW122E

AUTOMATIC MUST BE SPECIFIED IF DESTINATION DEFINED

Data entry error; see Data entry errors.

EQQW123E

CORRECT VALUES ARE OCHRENZ OR OCHREND

Data entry error; see Data entry errors.

EQQW124E

REMOTE ENGINES CANNOT USE RESOURCES AT PLANNING AND CONTROL

The resources for a remote engine workstation are not allowed and they must not be used either for planning or control.

None

In the ISPF panel to set the proper values automatically for the remote engine workstation, press the PF3 key or the END command. If the error occurred in batch, correct the data and submit the job again.

EQQW125E

REMOTE ENGINE TYPE IS NOT DEFINED OR IT IS INVALID

Data entry error; see Data entry errors.

EQQW126E

SERVER USAGE MUST BE N FOR REMOTE ENGINE WORKSTATIONS

Data entry error; see Data entry errors.

EQQW200E

THE STANDARD DAY IS NOT DEFINED OR IS INVALID

Data entry error; see Data entry errors.

You did not define correctly the standard day. A minimum of one open interval must be defined for the standard day. You cannot define the standard day as closed.

EQQW201E

THE OPEN INTERVAL TABLE CONTAINS DUPLICATE ENTRIES

Data entry error; see Data entry errors.

EQQW202E

DAY OR DATE IS NOT DEFINED OR IT IS INVALID

Data entry error; see Data entry errors.

EQQW203E

OPEN INTERVAL FOR STANDARD DAY IS INVALID OR NOT DEFINED

Data entry error; see Data entry errors.

EQQW204E

INTERVALS OVERLAP IN THE OPEN INTERVAL TABLE

Data entry error; see Data entry errors.

EQQW205E

OPEN INTERVAL END TIME MUST BE LATER THAN THE START TIME

Data entry error; see Data entry errors.

EQQW206E

OPEN INTERVAL START OR END TIME INVALID OR NOT DEFINED

Data entry error; see Data entry errors.

EQQW207E

CAPACITY OF PARALLEL SERVERS INVALID OR NOT DEFINED

Data entry error; see Data entry errors.

EQQW208E

RESOURCE CAPACITY IS NOT DEFINED OR IT IS INVALID

Data entry error; see Data entry errors.

EQQW209E

THE STANDARD DAY CANNOT BE CLOSED

Data entry error; see Data entry errors.

EQQW210E

ALTERNATE WS IS NOT ALLOWED FOR THE SELECTED WORKSTATION TYPE

You can specify an alternative workstation only for computer workstations, general workstations with the WTO attribute set, and distributed remote engine workstations.

The database is not updated. All changes are ignored.

None.

EQQW211E

THE ALTERNATE WS MUST BE OF THE SAME TYPE

You specified an alternative workstation that is not defined in the workstation description database as a computer type workstation.

The database is not updated. All changes are ignored.

Specify the name of a computer type workstation or alter the attributes of the workstation in the workstation description database.

EQQW212E

THE ALTERNATE WS IS NOT FOUND IN THE WS DATA BASE

The alternative workstation that you specified is not defined in the workstation description database.

The database is not updated. All changes are ignored.

Specify the name of an existing computer type workstation or add the workstation that you specified to the workstation description database.

EQQW213E

THE CURRENT WS CANNOT BE ALTERNATE TO ITSELF

The alternative workstation cannot be the current workstation.

The status of the workstation does not change.

Change the name of the alternative workstation.

EQQW214E

NODE ADDRESS CANNOT BE SET IF ACCESS METHOD NAME IS BLANK

If the access method name is blank, the node address cannot be set. To specify a node address value, first set the access method name.

Processing continues. HCL Workload Automation for Z waits for your next input.

Set the access method name and set the node address.

EQQW215E

PORT NUMBER CANNOT BE SET IF NODE ADDRESS IS BLANK

If the node address is blank, the port number cannot be set. To specify a port number value, first set the node address.

Processing continues. HCL Workload Automation for Z waits for your next input.

Set the node address and set the port number.

EQQW216E

ACCESS METHOD CAN BE SET ONLY FOR NON-VIRTUAL WS, COMPUTER TYPE

You specifed an access method name. Access method is supported only for non-virtual computer workstations.

Processing continues. HCL Workload Automation for Z waits for your next input.

Specify a valid workstation type and set the VIRTUAL option to N.

EQQW217E

PORT NUMBER MUST BE NUMERIC AND IN THE RANGE 0-65535

You specified a port number value that was not numeric or was greater than 65535. The port number must be a numeric value in the range 0–65535.

Access-method-specific data is not saved.

Specify a valid port number.

EQQW218E

D COMMAND IS ALLOWED ONLY FOR VIRTUAL WORKSTATIONS

You specified the destination command on a workstation whose virtual flag is set to N. The destination command is only allowed for virtual work stations.

The request is rejected.

Specify a valid command.

EQQW219E

THE DESTINATION TABLE CONTAINS DUPLICATE DESTINATIONS

Data entry error; see Data entry errors.

The destination you specified already exists. Specify a different destination.

EQQW300I

ALL CLOSED WORK STATIONS HAVE BEEN UPDATED

All workstations closed has been updated.

None.

None.

EQQW301E

SOME DATES MAY NOT HAVE BEEN UPDATED

Due to a failure in the subsystem, some dates may not have been updated as specified.

The system waits for you to respond.

Review the HCL Workload Automation for Z message log for I/O errors that immediately precede this message. Correct all errors and restart HCL Workload Automation for Z.

Exit from the Modify All Work Stations Closed panel. On the Work Station dialog, reenter option 4, MODIFY CLOSED to determine which dates were updated and which were not. Enter the necessary changes and retry. If the error persists, contact your system programmer.

EQQW302E

ALL WORK STATION CLOSED ISPF TABLE ERROR. NOTHING UPDATED

An ISPF table contains duplicate entries.

The changes are not saved.

Make sure that the supplied panel is being used.

Contact your system programmer to make sure that the supplied panel is used.

EQQW303E

ANOTHER USER IS UPDATING ALL WS CLOSED, TRY LATER

You cannot update the all-work-station-closed database because another user is currently updating it.

The system waits for you to respond.

Try again later.

EQQW304E

A VALID DATE MUST BE ENTERED AS CLOSE DATE

Data entry error; see Data entry errors.

Specify a valid data for the close date and retry the operation.

EQQW306E

BOTH CLOSED-FROM AND CLOSED-TO TIME MUST BE ENTERED

Data entry error; see Data entry errors.

Specify both the closed-from date and the closed-to date.

EQQW307E

SPECIFIED FROM-TIME LATER THAN TO-TIME

Data entry error; see Data entry errors.

Specify a to-time that is later than the from-time.

EQQW308E

DUPLICATE WORK STATION CLOSED DATES EXIST IN TABLE

Data entry error; see Data entry errors.

Remove the duplicated value and retry the operation.

EQQW309I

ALL WORK STATION CLOSED INFO MISSING, NO ACCESS TO DATA BASE

Information about whether or not all workstations are closed for this date could not be retrieved because you do not have access to the all-work-station-closed database.

None.

None.

EQQW400E

WTO OPTION ONLY ALLOWED IF WORK STATION TYPE IS GENERAL

Data entry error; see Data entry errors.

You cannot specify the write-to-operator (WTO) option for this workstation type. The write-to-operator (WTO) option is allowed if the workstation type is general, but not if the workstation type is computer or printer.

EQQW401E

THE WTO OPTION IS MUTUALLY EXCLUSIVE WITH THE SPECIFIED OPTION

Data entry error; see Data entry errors.

You cannot specify the write-to-operator (WTO) option if the workstation option is job setup, task or splittable.

EQQW402E

STARTED TASK OPTION ONLY ALLOWED IF WORK STATION TYPE IS CPU

Data entry error; see Data entry errors.

Started task (STC) option is allowed if the workstation type is computer, but not if the workstation type is general or printer.

You cannot specify the started task (STC) option if the workstation type is general or printer. Specify it if the workstation type is computer.

EQQW403E

THE STC OPTION IS MUTUALLY EXCLUSIVE WITH THE SPECIFIED OPTION

Data entry error; see Data entry errors.

Started task (STC) option is not allowed if the workstation option is job setup, write-to-operator (WTO), or splittable.

You cannot specify the started task (STC) option if the workstation option is job setup, write-to-operator (WTO), or splittable.

EQQW404E

THIS DESTINATION REPRESENTS A HWA/A V1R2 NEC SYSTEM

In the ROUTOPTS statement, the specified destination is defined as HWA/A Version 1 Release 2 NEC system. Any work that should be transmitted to such a system must be handled by NJE.

The workstation description is not updated.

If HCL Workload Automation for Z should initiate work at this destination, start a HCL Workload Automation for Z tracker. Change the ROUTOPTS statement to reflect the new system type.

EQQW405E

THIS DESTINATION IS NOT DEFINED

The specified destination is not defined to HCL Workload Automation for Z in the ROUTOPTS initialization statement.

The workstation description is not updated.

In the ROUTOPTS initialization statement, define all HCL Workload Automation for Z tracker systems that are connected to the controller.

Verify that the destination is correctly specified.

EQQW406E

STARTED TASK OPTION INVALID OR NOT DEFINED

Data entry error; see Data entry errors.

You can specify Y (yes) or N (no) for the started task option.

EQQW407E

WTO OPTION INVALID OR NOT DEFINED

Data entry error; see Data entry errors.

You can specify Y (yes) or N (no) for the WTO option.

EQQW408E

FOR FTW, CONTROL, AND PLANNING ON SERVER MUST HAVE THE VALUE N

When a fault-tolerant workstation is defined, no control and planning on parallel server must be done. The valid value is N.

The record is not created.

Specify N for the FTW option.

EQQW409E

AUTOMATION OPTION NOT VALID OR NOT DEFINED

Automation option not valid or not defined.

Valid values for the option are Y and N. Specify one of the valid value.

EQQW410E

AUTOMATION OPTION ALLOWED ONLY IF WORK STATION TYPE IS GENERAL

The Automation option is allowed only if workstation type is General.

You can specify the Automation option only if the workstation type is General.

EQQW411E

AUTOMATION OPTION ALLOWED ONLY IF WORK STATION IS AUTOMATIC REPORTING

The Automation option is allowed only if workstation type is Automatic.

You can specify the Automation option only if the workstation is Automatic.

EQQW412E

AUTOMATION OPT MUTUALLY EXCLUSIVE WITH JOB, STC, AND WTO WS OPTS

The Automation option is mutually exclusive with the workstation options JOB, STC, and WTO.

EQQW413E

WAIT OPTION INCORRECT OR NOT DEFINED

Data entry error; see Data entry errors.

You specified an incorrect value. Specify Y (yes) or N (no).

EQQW414E

WAIT OPTION ALLOWED ONLY FOR GENERAL NON REPORTING WORK STATIONS

Data entry error; see Data entry errors.

The Wait option is allowed only if workstation type is general and work station attribute is non reporting.

EQQW415E

WAIT OPTION NOT ALLOWED WITH JOB SETUP, SPLITTABLE OR WTO OPTIONS

Data entry error; see Data entry errors.

The Wait option is not allowed if the workstation option is job setup, splittable, or WTO.

EQQW416E

VIRTUAL OPTION INCORRECT OR NOT DEFINED

Data entry error; see Data entry errors.

The option can be Y (yes) or N (no).

EQQW418E

DESTINATION FIELD CANNOT BE SPECIFIED IF VIRTUAL FLAG IS Y

You specified a value for destination field. You cannot specify a destination field for virtual workstations.

Processing continues. HCL Workload Automation for Z waits for your next input.

Remove the destination field or change the VIRTUAL option to N.

EQQW419E

COMMAND NOT ALLOWED FOR VIRTUAL WORK STATIONS

The commands A, R, and M are not allowed for virtual workstations because the related information must be specified at destination level only after using the D command.

The request is rejected.

Specify a valid command.

EQQW420E

MAIN DESTINATION MUST BE BLANK FOR VIRTUAL WORKSTATION

You specified a value for destination field. You cannot specify a destination field for virtual workstations.

The request is rejected.

Remove the destination field or change the VIRTUAL option to N.

EQQW421E

AT LEAST ONE DESTINATION IS NEEDED FOR VIRTUAL WORKSTATION

You are defining a workstation with the VIRTUAL option set to Y, therefore you must specify also a destination list.

The request is rejected.

Define a destination list or change the VIRTUAL option to N.

EQQW424E

VIRTUAL WORKSTATION CANNOT BE MODIFIED

A user program requested to replace the common data of a workstation in the database, changing the current virtual attribute.

The request is rejected.

If you want to redefine the virtual attribute for the workstation, you must delete the current definition and insert a new workstation definition.

EQQW425E

OPTION NOT ALLOWED FOR VIRTUAL WORKSTATIONS

You cannot specify this option for virtual workstations.

The request is rejected.

Reset the specified option or change the VIRTUAL option to N.

EQQW426E

VIRTUAL WORKSTATIONS MUST HAVE AT LEAST ONE DESTINATION

You are defining a workstation with the VIRTUAL option set to Y, therefore you must specify also a destination list.

The request is rejected.

Define a destination list or change the VIRTUAL option to N.

EQQW427E

DESTINATION DEST IS NOT DEFINED

The specified destination is not defined in the ROUTOPTS initialization statement.

The workstation description is not updated.

In the ROUTOPTS initialization statement, define all HCL Workload Automation for Z tracker systems that are connected to the controller.

Verify that the destination is correctly specified.

EQQW428E

ALTERNATE DEFINITION NOT APPLICABLE TO VIRTUAL WORKSTATIONS

You specified a virtual workstation as alternate workstation. The alternate workstation concept is not applicable to virtual workstations, either at workstation level or at single destination level.

The workstation description is not updated.

Specify a non-virtual workstation as alternate workstation.

EQQW429E

DESTINATION DEST IS DUPLICATED

The specified destination is duplicated.

The workstation description is not updated.

Remove the duplicate destination.

EQQW430E

Z-CENTRIC AGENT OPTION INCORRECT OR NOT DEFINED

Data entry error; see Data entry errors.

You specified an incorrect value. Specify Y (yes) or N (no).

EQQW500E

THE JCL LIBRARY, DDNAME EQQJBLIB, COULD NOT BE OPENED

HCL Workload Automation for Z could not open the JCL library (ddname EQQJBLIB) to read a member.

If the failure occurred during job submission the operation extended status is set to error.

Check that the ddname EQQJBLIB is correctly specified and that the task started by HCL Workload Automation for Z is authorized to open the data set for input. When the error is corrected, stop HCL Workload Automation for Z and restart it.

Contact your system programmer.

Review the preceding messages in the HCL Workload Automation for Z message log for a message describing an error on the EQQJBLIB file.

EQQW501E

LOGICAL RECORD SIZE FOR THE JCL LIBRARY, DDNAME EQQJBLIB, IS NOT VALID

HCL Workload Automation for Z could not read the JCL library (ddname EQQJBLIB) because the logical record length is not 80 bytes.

If the failure occurred during job submission the operation extended status is set to error.

Check that the ddname EQQJBLIB is correctly specified. When the error is corrected, stop HCL Workload Automation for Z and restart it.

Contact your system programmer.

Check the definition of the EQQJBLIB DD statement.

EQQW502E

WORK STATION ANALYZER INITIALIZATION FAILED

The workstation analyzer could not acquire all the resources required for normal operation. The most likely reason is that the subsystem is being stopped, but the normal mode manager task has not started. It is also possible that a submit/release data set or the EQQJBLIB data set could not be opened.

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

Correct all errors and restart the workstation analyzer.

Review earlier messages in the HCL Workload Automation for Z message log to determine the exact cause of the error.

EQQW503I

THE WORK STATION ANALYZER ENDED NORMALLY

The HCL Workload Automation for Z subsystem is being stopped and initialization of the workstation analyzer has completed successfully or a request has been made by an operator modify command to stop the workstation analyzer.

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

None.

EQQW505I

THE WORK STATION ANALYZER TASK HAS STARTED

The initialization of the workstation analyzer has completed and the workstation analyzer is about to start processing.

HCL Workload Automation for Z continues processing.

None.

EQQW506E

THE SCHEDULER COULD NOT ALLOCATE STORAGE TO PROCESS EQQJBLIB MEMBER MEMBER

The workstation analyzer was attempting to build a record in the VSAM data set that was to be inserted in the JCL repository data set, but it was unable to do so because of insufficient virtual storage.

The operation remains in ready status. The workstation analyzer is unable to submit the job to JES.

Stop HCL Workload Automation for Z and restart in a larger region.

Submit the job manually.

EQQW507W

THE SCHEDULER COULD NOT SAVE JOB MEMBER IN THE JS DATASET FOR APPL. APPL

An error occurred when the workstation analyzer was trying to update the JCL repository data set.

The job is submitted to JES, but the JCL repository data set would not be correctly updated.

Correct all errors and restart the workstation analyzer.

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

EQQW508W

EQQUX013 PREVENTED JOB TAILORING FOR JOB MEMBER IN APPL APPL DESPITE THE OPERATION HAS CLEANUP TYPE DIFFERENT FROM NONE

The scheduler has been requested by the EQQUX013 user exit not to tailor a job with the //TIVDSTxx OUTPUT statements, even though for the corresponding operation the cleanup type is set to a value different from None.

The job is submitted without being tailored with the //TIVDSTxx OUTPUT statements required for the restart and cleanup processing.

Check if the cleanup type specified at operation level can be changed to None, or the EQQUX013 source requires to be modified.

EQQW510E

WS ANALYZER WAS UNABLE TO READ OR UPDATE CURRENT PLAN JNT RECORD FOR: JOB = JOBNAME, APPLICATION = APPL, INPUT ARRIVAL = ARRTIME

The workstation analyzer encountered a VSAM error when reading or updating the current plan data set.

The workstation analyzer continues normal processing with the next ready operation.

Correct all errors and restart the workstation analyzer.

Review earlier messages in the HCL Workload Automation for Z message log and the SYSLOG data sets to determine the exact cause of this error.

EQQW511E

WS ANALYZER WAS UNABLE TO RELEASE JOB JOBNAME(JOBNUM) FROM HOLD

The workstation analyzer was unable to communicate successfully with JES while trying to release job JOBNAME(JOBNUM) from hold.

The hold status of the current job is not changed. The workstation analyzer continues normal processing.

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.

EQQW512E

WS ANALYZER WAS UNABLE TO READ OR UPDATE CURRENT PLAN OPERATION RECORD WITH KEY (HEXADECIMAL): F0F3OPRINDEX

The workstation analyzer encountered a VSAM error when reading or updating the current plan data set.

The workstation analyzer continues normal processing with the next ready operation.

Correct all errors and restart the workstation analyzer.

Review earlier messages in the HCL Workload Automation for Z message log and the SYSLOG data sets to determine the exact cause of this error.

EQQW513E

THE SUBMIT/RELEASE DATA SET WITH DDNAME = DDNAME COULD NOT BE OPENED

The workstation analyzer could not open a submit/release data set with the indicated ddname. The ddname is defined as a submit/release data set ddname in one of the computer workstations in the current plan data set.

The workstation analyzer issues message EQQW502E and is terminated.

Correct all errors and restart the workstation analyzer.

Check that the ddname is correctly specified and that the HCL Workload Automation for Z started task is authorized to open the data set for update.

EQQW514W

TOO MANY SUBMIT/RELEASE DATA SETS DEFINED. DDNAME = DDNAME IS IGNORED

More than 16 ddnames for the submit/release data set are defined in the current plan data set.

Only the first 16 submit/release ddnames found are used by the workstation analyzer.

Correct all errors and, if necessary, restart the workstation analyzer.

Check that all computer workstations have been correctly specified.

EQQW515W

THE SUBMIT USER EXIT MODULE, EQQUX001, COULD NOT BE LOADED

HCL Workload Automation for Z could not locate the job submit exit load module, EQQUX001.

The job submit exit is not used by the workstation analyzer.

If the job submit exit is meant to be used, make sure that the EQQUX001 load module is present in a library that can be reached by HCL Workload Automation for Z. Restart the workstation analyzer.

EQQW516E

THE EQQUX002 EXIT COULD NOT OPEN AN INPUT DATA SET TO READ JOB MEMBER

The joblib I/O exit was called and gave a return code indicating that it could not open one of its input data sets.

The job is not submitted by the workstation analyzer as intended. The operation remains in ready status.

Correct all errors and restart the workstation analyzer.

If necessary, submit the job manually.

Check that all DD statements needed by the EQQUX002 exit have been correctly specified and that the HCL Workload Automation for Z started task is authorized to open the data set for input.

EQQW517E

INSUFFICIENT STORAGE TO PROCESS JOB MEMBER FOR EQQUX002 EXIT

The workstation analyzer was building a record in the VSAM data set to be inserted in the JCL repository data set, but it was unable to do so because of insufficient virtual storage.

The operation remains in ready status. The workstation analyzer is unable to submit the job to JES.

Stop HCL Workload Automation for Z and restart it in a larger region.

Submit the job manually.

EQQW518E

THE EQQUX002 EXIT COULD NOT FIND JOB MEMBER IN ANY INPUT DATA SET

The workstation analyzer was attempting to submit a job to JES for a ready operation on a computer workstation. However, no JCL for this operation is saved in the JCL repository data set, and the joblib I/O exit could not find the job in any input data set.

The operation remains in ready status. HCL Workload Automation for Z assumes that some other function submits the job to JES.

Correct all errors and restart the workstation analyzer.

If necessary, submit the job manually.

Check that all DD statements needed by the EQQUX002 exit have been correctly specified and that all required members are specified.

EQQW519W

THE EQQUX002 EXIT DID NOT RETURN ANY DATA FOR JOB MEMBER

The joblib I/O exit was called to retrieve a job to be submitted, but the exit did not return any data.

The job is not submitted by the workstation analyzer as intended. The operation remains in ready status.

Correct all errors and restart the workstation analyzer.

If necessary, submit the job manually.

Check that the joblib I/O exit has been correctly installed and that it works properly.

EQQW520E

THE EQQUX002 EXIT RETURNED THE FOLLOWING I/O ERROR MESSAGE FOR JOB MEMBER: PLUSMSG

The joblib I/O exit was called to retrieve a job to be submitted, but the exit gave a return code indicating that an I/O error had occurred on an input data set.

The job is not submitted by the workstation analyzer as intended. The operation remains in ready status.

Correct all errors and restart the workstation analyzer.

If necessary, submit the job manually.

Check that the joblib I/O exit can access all required input data sets and that it works properly.

EQQW521E

THE JOBLIB I/O USER EXIT MODULE, EQQUX002, COULD NOT BE LOADED

HCL Workload Automation for Z could not locate the joblib I/O exit load module, EQQUX002.

The joblib I/O exit is not used by the workstation analyzer.

If the joblib I/O exit is meant to be used, make sure that the EQQUX002 load module is present in a library that can be reached by HCL Workload Automation for Z. Restart the workstation analyzer.

If necessary, submit the job manually.

EQQW522E

JOB MEMBER RETURNED BY THE EQQUX002 EXIT EXCEEDS MAXIMUM SUPPORTED SIZE

The joblib I/O exit was called to retrieve a job to be submitted, but the returned job exceeds the maximum supported size, which is 608 KB (kilobytes) of data.

The job is not submitted by the workstation analyzer as intended. The operation remains in ready status.

Correct all errors and restart the workstation analyzer.

If necessary, submit the job manually.

Check that the joblib I/O exit has been correctly installed and that it works correctly.

EQQW523E

JOB MEMBER IN APPLICATION APPL IS TOO LARGE TO BE SAVED ON THE JS DATA SET

A job that is about to be submitted to JES is too large to be saved in the JCL repository data set.

The job is submitted, but the JCL repository data is not updated.

If necessary, allocate a new JCL repository data set with a larger maximum record size. Refer to Customization and Tuning for instructions.

Use the IDCAMS LISTCAT function to determine the maximum size of records in the data set defined by the EQQJSxDS DD statement. Use dialog option 6.6 to determine the current JCL repository.

EQQW524E

JOB MEMBER IN APPLICATION APPL COULD NOT BE SUBMITTED BECAUSE THE EQQUX001 EXIT RETURNED AN ERROR CODE NOT ZERO

The job submit exit was called and returned an error code that was different from '0000'.

The job is not submitted and its error status is set to the error code that was returned by the submit exit job.

Check why the submit exit job, EQQUX001, stopped submission.

EQQW525E

JOB MEMBER IN APPLICATION APPL COULD NOT BE SUBMITTED BECAUSE OF AN ERROR IN THE JOB CARD

HCL Workload Automation for Z has been requested to submit a job that has an incorrect job card.

The job is not submitted.

Correct the JCL for this job and use the Modify Current Plan dialog to restart the occurrence at the failing operation.

EQQW526E

JOB MEMBER IN APPLICATION APPL COULD NOT BE SUBMITTED BECAUSE NO JOB CARD COULD BE FOUND

HCL Workload Automation for Z has been requested to submit a job that does not have a job card or a job that has been packed by ISPF in EQQJBLIB.

The job is not submitted.

Check that the JCL for this job has not been packed by ISPF. Correct the JCL for this job and use the Modify Current Plan dialog to restart the occurrence at the failing operation.

EQQW527W

THE JOB CARD OF JOB MEMBER IN APPLICATION APPL SPECIFIES JOB NAME CURNAME. THE JOB IS SUBMITTED ANYWAY

HCL Workload Automation for Z has been requested to submit a job whose name is different from the job name of the current operation.

HCL Workload Automation for Z submits the job without any changes.

If the difference in job names is intentional, the message can be ignored. If the message is not expected, make sure that the operation corresponding to this job has the correct status.

EQQW528W

INSUFFICIENT STORAGE TO BUILD NEW JCLAREA. EXIT01 CANNOT INCREASE JCL SIZE. APPLICATION IS: ADID, OPERATION NO IS: OPNO, INPUT ARRIVAL DATE IS: IAD AND INPUT ARRIVAL TIME IS: IAT

HCL Workload Automation for Z tried to allocate storage to build a new JCLAREA as requested by the OPCOPTS EXIT01SZ keyword during the EXIT01 processing, but the request for storage failed.

The scheduler submits the job without any change.

Ensure that the load module implementing the job-submit exit is link-edited with RMODE(24) and AMODE(31) attributes.

EQQW529E

JOB MEMBER IN APPLICATION APPL COULD NOT BE SUBMITTED BECAUSE THE JOB CARD SPECIFIES JOB NAME CURNAME

HCL Workload Automation for Z has been requested to submit a job whose name is different from that specified by the corresponding operation. JOBCHECK(SAME) has been defined on the JTOPTS initialization statement.

The job is not submitted.

Change the JCL for this job to use the correct job name and use the Modify Current Plan dialog to restart the occurrence at the failing operation.

EQQW531E

RE-RUN OF JCL WAS NOT POSSIBLE. STORAGE NOT AVAILABLE TO BUILD EXIT01 JCLAREA. APPLICATION IS: ADID, OPERATION NO IS: OPNO, INPUT ARRIVAL DATE IS: IAD AND INPUT ARRIVAL TIME IS: IAT

The worstation analyzer task tried to allocate an area to copy the JCL to be passed to the EQQUX001 user exit, but the storage allocation failed.

The job is submitted but the EQQUX001 user exit is not called.

Relink-edit the EQQUX001 user exit to be loaded over 16MB.

EQQW532E

THE WSA TASK IS TERMINATING DUE TO A SEVERE ERROR. REFER TO THE SYSUDUMP DATA SET FOR MORE INFORMATION

The workstation analyzer task has encountered a severe error.

The workstation analyzer task terminates and a dump of the HCL Workload Automation for Z subsystem address space is generated.

Refer to the SYSUDUMP data set to determine the cause of the error. If the problem is caused by either of the exits taken by the workstation analyzer, that is, by EQQUX001 or by EQQUX002, the exit must be updated. After correcting all errors, restart the HCL Workload Automation for Z subsystem.

EQQW533E

THE WSA TASK WILL ATTEMPT TO RECOVER FROM A SEVERE ERROR. REFER TO THE SYSUDUMP DATA SET FOR MORE INFORMATION

The workstation analyzer task has encountered a severe error.

The workstation analyzer task generates a dump of the HCL Workload Automation for Z subsystem address space and attempts to continue normal processing.

Refer to the SYSUDUMP data set to determine the cause of the error. If the problem is caused by either of the exits taken by the workstation analyzer, that is, by EQQUX001 or by EQQUX002, the exit must be updated.

EQQW534E

THE WSA TASK HAS DETECTED A LOOP. SNAP OF DOA, CPLREC3P, AND WAP FOLLOWS:

The workstation analyzer task has tried to start the same operation repeatedly. The associated DOA, CPLREC3P, and WAP are written to the message log (MLOG). The operation status is set to error, with error code LOOP.

The failing operation is not dispatched and the workstation analyzer task continues processing.

This might be a user error or an internal HCL Workload Automation for Z error. Keep copies of the MLOG, JTARC and active JTnn, and CP. If you suspect that this is not a user error, contact the Software Support.

Review the MLOG, job tracking (JT) log, and current plan (CP) to determine the cause of the error.

EQQW536E

JOB MEMBER IN APPLICATION APPL COULD NOT BE SUBMITTED BECAUSE PRE-SUBMIT TAILORING FAILED

The scheduler has been requested to submit a job that needed the pre-submit task tailoring, but the tailoring failed.

The job is not submitted.

Check the EQQMLOG for additional messages. One of the possible reasons might be lack of storage: if so, increase the controller region size.

EQQW537E

WS ANALYZER WAS UNABLE TO READ OR UPDATE CURRENT PLAN OCCURRENCE RECORD WITH KEY (HEXADECIMAL): X'F0F3'occindex

The workstation analyser encountered a VSAM error when reading or updating the current plan data set (occurrence record: see Diagnosis DCLCPR3C).

The workstation analyser continues normal processing with the next ready operation.

Review earlier messages in the message log and SYSLOG data set to determine the cause of this error. If the error can be reproduced, activate the VSAM trace (/F subsystem,VSTRC=START).

EQQW538E

WS ANALYZER WAS UNABLE TO READ OR UPDATE CURRENT PLAN JOBLOG RECORD WITH KEY (HEXADECIMAL): X'F1F4'logindex

The workstation analyser encountered a VSAM error when reading or updating the current plan data set (Joblog record: see Diagnosis DCLCPR14).

The workstation analyser continues normal processing with the next ready operation.

Review earlier messages in the message log and SYSLOG data set to determine the cause of this error. If the error can be reproduced, activate the VSAM trace (/F subsystem,VSTRC=START).

EQQW539E

THE EXECUTE COMMAND FAILED DUE TO INACTIVE WORKSTATION APPL: APPLID IA: IA OPERATION: OPNO

The workstation analyzer task has detected that there is no active workstation for the actual operation.

The workstation analyzer task resets the execute indicator. The operation remain in ready status and is scheduled as any normal operation.

If an immediate execution of the operation is desired, activate the ordinary workstation or, if the operation is reroutable, activate the alternative workstation. Reissue the EXECUTE command.

EQQW550W

ADID OPERATION NO: OPNO WITH INPUT ARRIVAL: IA AND JOBNAME: JOBNM CANNOT BE RESUBMITTED BECAUSE MANUAL CLEAN UP IS REQUESTED

The workstation analyzer detected an operation to resubmit that can not be scheduled. This is because the operation has a cleanup type of Manual and it is waiting for cleanup actions to be started through the Start Clean Up command.

The workstation analyzer ignores this operation and continues processing normallly.

  1. Select the operation mentioned in the message text in the MCP panel.
  2. Issue the RC line command to enter the Restart and Cleanup main panel.
  3. Select the START CLEANUP option and wait for the cleanup to complete.
When the cleanup is complete, the WSA schedules the operation automatically.

EQQW551E

SUBMISSION FAILED FOR OPERATION OPERNUM, IN APPLICATION APPL, IA=ARRTIME BECAUSE IT HAS EXCEEDED THE MAXIMUM NUMBER OF RETRY SENDING THE SCRIPT TO THE AGENT

The submission of operation OPERNUM in application APPL with input arrival ARRTIME failed while the engine was sending the script for the operation to the distributed agent. The controller has retried 10 times but the error persists.

The Workstation Analyzer task stops trying to submit the job and sets the operation status according to the SUBFAILACTION option specified in the JTOPTS statement of the controller's initialization parameters.

Check the Controller and the server MLOG for the error that has caused the failure.

Contact your system programmer to solve the problem and reset the operation status to Ready to retry job submission.

EQQW552W

JOB MEMBER, IN APPLICATION APPL WAS NOT STORED IN JS DUE TO STORAGE PROBLEMS

When a job is submitted in a Restart and Cleanup path (Step Restart, Job Restart, or rerun of an operation with automatic Cleanup type), HCL Workload Automation for Z controller requires the removal of the EQQCLEAN pre-step from the submitted JCL, before storing it in JS VSAM. During this process, storage cannot be allocated and the EQQCLEAN removal cannot be done.

If no other problems occur (for example, OJCV error), the job is submitted. The job is not stored in JS VSAM.

None.

EQQW553E

A NOT NUMERIC STRING HAS BEEN SPECIFIED AS STARTING OFFSET IN SDEPFILTER KEYWORD.

SDEPFILTER must specify a number from 1 to 20 as starting position to activate the check on the JOB card programmer name.

The scheduler cannot use SDEPFILTER as filter criteria to produce the step-end event.

Specify a correct value as startpos.

EQQW554E

STARTING OFFSET VALUE IS NOT VALID FOR SDEPFILTER KEYWORD. THE OFFSET MUST NOT BE GREATER THAN PROGRAMMER NAME FIELD LENGTH.

SDEPFILTER must specify a maximum value of 20 as starting position to activate the check on the JOB card programmer name.

The scheduler cannot use SDEPFILTER as filter criteria to produce the step-end event.

Specify a correct value as startpos.

EQQW555E

WRONG SDEPFILTER KEYWORD SPECIFICATION: SPECIFIED VALUE STARTING AT THE SPECIFIED OFFSET EXCEEDS PROGRAMMER NAME FIELD LENGTH.

SDEPFILTER must specify no more than 20 characters as string value to activate the check on the JOB card programmer name.

The scheduler cannot use SDEPFILTER as filter criteria to produce the step-end event.

Specify a correct value as stringvalue.

EQQW750W

STC STCNAME IS DEFINED AS A SUBSYSTEM THAT IS NOT MANAGED BY JES. THE SCHEDULER DOES NOT SUPPORT THIS STC

The submittor task cannot start this STC because it is defined as a subsystem not handled by JES.

The corresponding operation is set to ended-in-error with error code OSUB.

Check the active IEFSSNem in the SYS1.PARMLIB data set to see if the STC STCNAME is defined as a subsystem. If it is not defined, contact the Software Support.

EQQW751E

THE SUBMITTOR TASK GOT RC IN RETURN CODE FROM THE MGCR MACRO WHEN THE STC STCNAME WAS ABOUT TO BE STARTED

The submittor task cannot start this STC. The MGCR macro (SVC34) failed with the indicated return code in register 15.

The corresponding operation is set to ended-in-error with error code OSUB.

Contact the Software Support.

EQQW752W

A SUBMIT EVENT RECORD (TYPE I) WILL BE CREATED FOR STC STCID, BUT IT MAY BE TOO LATE

The submittor task has been restarted after ending abnormally. The abnormal termination occurred immediately after the start command was performed for an STC, before the I event record could be created.

If more than five minutes has passed since the submittor task ended abnormally, the A1 event record is timed out. HCL Workload Automation for Z tracking of the operation fails.

None.

Investigate why the submittor task ended abnormally and take appropriate action.

Check the status of the corresponding operation. If the status is wrong, correct it manually.

EQQW753E

STC STCID HAS BEEN STARTED, BUT THE MVS EXIT IEFUJI WAS NEVER OR INCORRECTLY INVOKED. THE TRACKING WILL FAIL FOR THE STC

The submittor task started an STC, but did not receive the expected acknowledgment from the z/OS SMF exit IEFUJI. The tracking of the STC fails.

None.

Check that the active SMFPRMxx member in the SYS1.PARMLIB data set specifies that IEFUJI is to be invoked for STCs.

Carefully check that the IEFUJI supplied with HCL Workload Automation for Z is correctly installed.

Check the status of the corresponding operation. If the status is wrong, correct it manually.

EQQW754E

THE STARTED TASK FILE, DDNAME = EQQSTC, COULD NOT BE OPENED

The submittor task failed to open the started task temporary proclib file, EQQSTC.

The submittor task does not submit started tasks, but continues to submit batch jobs and write-to-operator (WTO) operations.

Add an EQQSTC ddname to your HCL Workload Automation for Z start procedure JCL. The ddname must specify an empty partitioned data set.

  • Save the message log (MLOG) from the HCL Workload Automation for Z subsystem.
  • Save the JCL from the failing job or started task.

EQQW755E

THE STARTED TASK FILE, DDNAME = EQQSTC, IS NOT A PDS

The started task temporary proclib file, EQQSTC, was not allocated as a partitioned data set.

The submittor task does not submit started tasks, but continues to submit batch jobs and write-to-operator (WTO) operations.

Check that the data set allocated to the EQQSTC ddname is a partitioned data set.

  • Save the message log (MLOG) from the HCL Workload Automation for Z subsystem.
  • Save the JCL from the failing job or started task.
  • Run the AMASPZAP utility specifying ABSDUMP ALL on the data set and save the output.

EQQW756E

THE STARTED TASK FILE, DDNAME = EQQSTC, IS NOT EMPTY

The started task temporary proclib file, EQQSTC, is not empty.

The submittor task does not submit started tasks, but continues to submit batch jobs and write-to-operator (WTO) operations.

Check that the data set allocated to the EQQSTC ddname is an empty partitioned data set.

  • Save the message log (MLOG) from the HCL Workload Automation for Z subsystem.
  • Save the JCL from the failing job or started task.
  • Run the AMASPZAP utility specifying ABSDUMP ALL on the data set and save the output.

EQQW757E

THE STARTED TASK FILE, DDNAME = EQQSTC, HAS WRONG LRECL OR WRONG BLOCK SIZE

The started task temporary proclib file, EQQSTC, was allocated with either a record length not equal to 80 or an invalid block size.

The submittor task does not submit started tasks, but continues to submit batch jobs and write-to-operator (WTO) operations.

Check that the data set allocated to the EQQSTC ddname is an empty partitioned data set.

  • Save the message log (MLOG) from the HCL Workload Automation for Z subsystem.
  • Save the JCL from the failing job or started task.
  • Run the AMASPZAP utility specifying ABSDUMP ALL on the data set and save the output.

EQQW758E

THE SUBMITTOR TASK DETECTED THAT THE STC STCID IS STILL IN JES3 INPUT SERVICE (STARTING)

The started task has not passed the JES3 input service phase.

This message is repeated every ten minutes.

The submittor task does not submit started tasks until the STC has passed JES3 input service, but continues to submit batch jobs and write-to-operator (WTO) operations.

None.

  • Save the message log (MLOG) from the HCL Workload Automation for Z subsystem.
  • Save the SYSLOG from the primary system console.
  • Produce a dynamic console dump of the HCL Workload Automation for Z address space. Make sure that CSA is part of the SDUMP option.

EQQW759E

THE SUBMITTOR TASK COULD NOT HANDLE STC STCNAME. THE STC SUBMISSION IS STOPPED

The started task was queued to the submittor queue, SUBQ. The STC could not be submitted because of errors (indicated by previous messages).

The submittor task does not submit started tasks, but continues to submit batch jobs and write-to-operator (WTO) operations.

Investigate the MLOG and look for other messages that explain the error. After the error has been corrected, the STC submission functionality can be reactivated by restarting either the submit task or the HCL Workload Automation for Z subsystem after deleting any entry that might have been left in the data set allocated to the EQQSTC ddname.

Manually set the corresponding operation to the correct status.

  • Save the message log (MLOG) from the HCL Workload Automation for Z subsystem.
  • Produce a dynamic console dump of the HCL Workload Automation for Z address space. Make sure that CSA is part of the SDUMP option.

EQQW760E

AN I/O ERROR OCCURRED ON THE EQQSTC DATA SET WHEN THE SUBMITTOR TASK WAS WRITING THE JCL FOR STC STCNAME. THE SYNAD ERROR MESSAGE WAS: SYNMSG

The submittor task encountered an I/O error writing to the started task temporary proclib file,EQQSTC. A SYNAD error routine was given control and issued an error message.

The submittor task does not submit started tasks, but continues to submit batch jobs and write-to-operator (WTO) operations.

The corresponding operation is set to status E.

This is probably a hardware error. Contact the Software Support.

The SYNAD routine collects information such as jobname, stepname, unit address, device type, ddname, operation, error description, and access method. The SYNADAF macro is used to extract this information. For a detailed description of the layout, refer to the appropriate documentation for the MVS/DFP product installed on this system.
  • Save the message log (MLOG) from the HCL Workload Automation for Z subsystem.
  • Save the SYSLOG from the primary system console.
  • Run the AMASPZAP utility specifying ABSDUMP ALL on the data set and save the output.

EQQW761E

AN ABEND OCCURRED WHEN THE SUBMITTOR TASK WAS WRITING THE JCL FOR STC STCNAME ON THE EQQSTC DATA SET. THE ABEND CODE WAS: ABCODE

The submittor task received an ABEND when writing the started task temporary proclib file, EQQSTC. An ABEND exit routine was given control and issued an ABEND code.

The submittor task does not submit started tasks, but continues to submit batch jobs and write-to-operator (WTO) operations.

The corresponding operation is set to status E.

See Abend codes for an explanation of the ABEND code and take the appropriate action.

  • Save the message log (MLOG) from the HCL Workload Automation for Z subsystem.
  • Save the SYSLOG from the primary system console.
  • Run the AMASPZAP utility specifying ABSDUMP ALL on the data set and save the output.

EQQW762E

AN I/O ERROR OCCURRED ON THE EQQSTC DATA SET WHEN THE SUBMITTOR TASK WAS STOWING THE MEMBER FOR STC STCNAME. THE SYNAD ERROR MESSAGE WAS: SYNMSG

The submittor task encountered an I/O error during a STOW to the started task temporary proclib file, EQQSTC. A SYNAD error routine was given control and issued an error message.

The submittor task does not submit started tasks, but continues to submit batch jobs and write-to-operator (WTO) operations.

The corresponding operation is set to status E.

This is probably a hardware error. Contact the Software Support.

The SYNAD routine collects information such as jobname, stepname, unit address, device type, ddname, operation, error description, and access method. The SYNADAF macro is used to extract this information. For a detailed description of the layout, refer to the appropriate documentation for the MVS/DFP product installed on this system.
  • Save the message log (MLOG) from the HCL Workload Automation for Z subsystem.
  • Save the SYSLOG from the primary system console.
  • Run the AMASPZAP utility specifying ABSDUMP ALL on the data set and save the output.

EQQW763E

AN ABEND OCCURRED WHEN THE SUBMITTOR TASK WAS STOWING THE MEMBER FOR STC STCNAME ON THE EQQSTC DATA SET. THE ABEND CODE WAS: ABCODE

The submittor task received an ABEND when stowing on the started task temporary proclib file, EQQSTC. An ABEND exit routine was given control and issued an ABEND code.

The submittor task does not submit started tasks, but continues to submit batch jobs and write-to-operator (WTO) operations.

The corresponding operation is set to status E.

See Abend codes for an explanation of the ABEND code and take the appropriate action.

  • Save the messge log (MLOG) from the HCL Workload Automation for Z subsystem.
  • Save the SYSLOG from the primary system console.
  • Run the AMASPZAP utility specifying ABSDUMP ALL on the data set and save the output.

EQQW764E

THE SUBMITTOR TASK GOT AN UNEXPECTED RETURN CODE WHEN STOWING THE MEMBER NAME FOR STC STCNAME ON THE EQQSTC DATA SET THE RETURN AND REASON CODE WAS RC

The submittor task received an unexpected return code when stowing a member on the started task temporary proclib file, EQQSTC.

The return code is the content of register 15 and the reason code is the content of register 0 after the STOW macro.

The corresponding operation is set to status E.

The submittor task does not submit started tasks, but continues to submit batch jobs and write-to-operator (WTO) operations.

Use the return code and reason code to determine the cause of the error. For more information, refer to the documentation about the STOW macro for the currently active z/OS system.

  • Save the message log (MLOG) from the HCL Workload Automation for Z subsystem.
  • Save the SYSLOG from the primary system console.
  • Run the AMASPZAP utility specifying ABSDUMP ALL on the data set, and save the output.

EQQW765E

THE SUBMITTOR TASK GOT AN UNEXPECTED RETURN CODE WHEN ISSUING THE MGCR MACRO FOR STC STCNAME

The submittor task received an unexpected return code when the MGCR macro was invoked to start an STC.

The corresponding operation is set to status E.

The submittor task does not submit started tasks, but continues to submit batch jobs and write-to-operator (WTO) operations.

Use the return code and reason code to determine the cause of the error. For more information, refer to the documentation about the MGCR macro for the currently active z/OS system.

EQQW766W

THE EVENT CREATION ROUTINE DETECTED THAT THE JES2 EXIT7 (EQQEXIT) IS ON A LOWER RDMID LEVEL THAN THE SCHEDULER SUBSYSTEM MODULE EQQZEV2X

The level of the EQQEXIT macro in JES2 EXIT7 (OPCAXIT7) is at a lower maintenance level than the HCL Workload Automation for Z subsystem.

The event creation routine continues to create event records. The event records may contain invalid tracking information, causing the corresponding operation status to be inaccurate.

If necessary, set the correct operation status manually.

Reapply the EXIT7, and make sure that the appropriate maclibs are used in the SYSLIB concatenation. If you are assembling the OPCAXIT7 outside the JES2 SMP environment, make sure that you have the SMPMTS data set concatenated first in the SYSLIB concatenation.

EQQW767W

THE EVENT CREATION ROUTINE DETECTED THAT THE IATUX29 WAS GENERATED AGAINST A JES3 LEVEL THAT DOES NOT MATCH THE CURRENT EXECUTING JES3 LEVEL

The level of the JES3 macros used to generate the HCL Workload Automation for Z IATUX29 does not match the level of the active JES3 system.

The event creation routine continues to create event records. The event records may contain invalid tracking information, causing the corresponding operation status to be inaccurate.

If necessary, set the correct operation status manually.

Reapply the IATUX29 and IATUX19, and make sure that the appropriate maclibs are used in the SYSLIB concatenation. If you are assembling the IATUX29 and IATUX19 outside the JES3 SMP-environment, make sure that you have the SMPMTS data set top concatenated in the SYSLIB concatenation.

EQQW768W

AN I/O ERROR OCCURRED ON THE EQQSTC DATA SET WHEN THE SUBMITTOR TASK WAS READING. THE SYNAD ERROR MESSAGE WAS: SYNMSG

The submittor task encountered an I/O error reading the started task temporary proclib file, EQQSTC.

The submittor task does not submit started tasks, but continues to submit batch jobs and write-to-operator (WTO) operations.

The corresponding operation is set to status E.

This is probably a hardware error. Contact the Software Support.

The SYNAD routine collects information such as jobname, stepname, unit address, device type, ddname, operation, error description, and access method. The SYNADAF macro is used to extract this information. For a detailed description of the layout, refer to the appropriate documentation for the MVS/DFP product installed on this system.
  • Save the message log (MLOG) from the HCL Workload Automation for Z subsystem.
  • Save the SYSLOG from the primary system console.
  • Run the AMASPZAP utility specifying ABSDUMP ALL on the data set and save the output.

EQQW769W

AN ABEND OCCURRED WHEN THE SUBMITTOR TASK WAS READING ON THE EQQSTC DATA SET. THE ABEND CODE WAS: ABCODE

The submittor task received an ABEND when reading the started task temporary proclib file, EQQSTC.

The submittor task does not submit started tasks, but continues to submit batch jobs and write-to-operator (WTO) operations.

The corresponding operation is set to status E.

This is probably a hardware error. Contact the Software Support.

  • Save the message log (MLOG) from the HCL Workload Automation for Z subsystem.
  • Save the SYSLOG from the primary system console.
  • Run the AMASPZAP utility specifying ABSDUMP ALL on the data set, and save the output.

EQQW770E

EQQSTC DDNAME IS MISSING

The submittor task could not find the EQQSTC ddname in the JCL.

The submittor task does not submit started tasks, but continues to submit batch jobs and write-to-operator (WTO) operations.

Add an EQQSTC ddname to the HCL Workload Automation for Z JCL procedure and specify an empty data set that is allocated on the JES proclib concatenation.

For more information, refer to the Planning and Installation

EQQW771W

THE JCL FOR STC JOBNAME WILL NOT BE SUBMITTED BECAUSE SUBMIT RECORD IS TOO OLD

The started task JCL records in a submit/release data set are older than the limit defined by the SKIPTIME and SKIPDATE keywords in the EWTROPTS statement.

The old records are not processed. The event writer continues to read the submit/release data set.

If necessary, restart the corresponding operation.

EQQW772W

THE WTO WITH JOBNAME JOBNAME WILL NOT BE ISSUED BECAUSE SUBMIT RECORD IS TOO OLD

A write-to-operator (WTO) message in a submit/release data set is older than the limit defined by the SKIPTIME and SKIPDATE keywords in the EWTROPTS statement.

The old message is not processed. The event writer continues to read the submit/release data set.

If necessary, restart the corresponding operation.

EQQW773W

THE EVENT CREATION ROUTINE DETECTED THAT JES2 EXIT51 (EQQEXIT) IS ON A LOWER RMID LEVEL EXITL THAN THE SCHEDULER SUBSYSTEM MODULE EQQZEV2Y WHOSE LEVEL IS J2LVL

The level of the EQQEXIT macro in JES2 EXIT51 (TWSXIT51) is at a lower maintenance level than the HCL Workload Automation for Z subsystem.

The event creation routine continues to create event records. The event records may contain invalid tracking information, causing the corresponding operation status to be inaccurate.

If necessary, set the correct operation status manually.

Reapply exit EXIT51, and make sure that the appropriate maclibs are used in the SYSLIB concatenation. If you are assembling TWSXIT51 outside of the JES2 SMP environment, make sure that the SMPMTS data set is placed first in the SYSLIB concatenation.

EQQW774W

THE EVENT CREATION ROUTINE DETECTED THAT JES2 EXIT51 (EQQEXIT) IS ON A HIGHER RMID LEVEL EXITL THAN THE SCHEDULER SUBSYSTEM MODULE EQQZEV2Y WHOSE LEVEL IS J2LVL

The EQQEXIT macro used to generate the currently active JES2 EXIT51 is on a higher maintenance level than the EQQZEV2Y subsystem module of HCL Workload Automation for Z.

The event creation routine continues to create event records. The event records may contain invalid tracking information, causing the corresponding operation status to be inaccurate.

If necessary, set the correct operation status manually.

EQQZEV2Y is part of the EQQSSCMx load module, which is normally loaded during IPL. To activate a new EQQSSCMx, until a planned IPL can be performed, specify SSCMNAME(EQQSSCMx) in the OPCOPTS initialization statement and restart the tracker address space.

EQQW775I

APPLICATION: ADID OP#: OPNO WITH INPUT ARRIVAL: IA AND JOBNAME: JOBNM ON WORK STATION: WSNAME HAS BEEN STARTED. OPERATION TEXT: OPTEXT

A write-to-operation (WTO) operation has been started by HCL Workload Automation for Z.

This message is for information only. It can be intercepted and interpreted in a customer-defined manner.

None.

None.

EQQW776I

APPLICATION: ADID OP#: OPNO WITH INPUT ARRIVAL: IA AND JOBNAME: JOBNM ON WORK STATION: WSNAME HAS PASSED DEADLINE: DEADL OPERATION TEXT: OPTEXT

An operation has passed its deadline.

This message is for information only. It can be intercepted and interpreted in a customer-defined manner, for example to automate termination.

None.

None.

EQQW777W

THE EVENT CREATION ROUTINE DETECTED THAT THE JES2 EXIT7 (EQQEXIT) IS ON A HIGHER RMID LEVEL (EXITL) THAN THE SCHEDULER SUBSYSTEM MODULE EQQZEV2X WHOSE LEVEL IS J2LVL

The EQQEXIT macro used to generate the currently active JES2 EXIT7 is on a higher maintenance level than the subsystem module EQQZEV2X.

The event creation routine continues to create event records. The event records may contain invalid tracking information, causing the corresponding operation status to be inaccurate.

If necessary, set the correct operation status manually.

The EQQZEV2X is part of the EQQSSCMx load module, which is normally loaded during IPL. To activate a new EQQSSCMx, until a planned IPL can be performed, specify SSCMNAME(EQQSSCMx) in the OPCOPTS initialization statement and restart the tracker address space.

EQQW778W

EQQEVDS DDNAME IS NOT PRESENT OR SPECIFIES DD DUMMY

The submittor task could not find the EQQEVDS DDNAME in the JCL for the HCL Workload Automation for Z address space or the DDNAME specifies DD DUMMY.

The submittor task does not checkpoint submit requests, but continues to submit jobs.

It is not mandatory to run a HCL Workload Automation for Z address space with the EQQEVDS data set, that is, when EWTRTASK(NO) is specified. However, to gain the submit checkpointing benefits, add this data set. When the data set is used only for submit checkpointing, allocate it with the minimum size, which is two tracks.

EQQW779I

NO CHECKPOINTING FOR SUBMITS ON WORKSTATION WSNAME (DQETYPE DQETYPE) WHY

The submittor task could not checkpoint a submit request for a DQETYPE (J1=JOB, J2=STC, WTO=WTO) defined on workstation WSNAME. The reason is defined by WHY, which can be any of the following:
  1. Access to the EQQEVDS data set is not available
  2. A Read from the EQQEVDS header record failed
  3. No entries are left in the EQQEVDS header record
  4. A delete WS from EVDS failed: WS not found
  5. A Write to the EQQEVDS header record failed.

The submittor task does not checkpoint submit requests, but continues to submit jobs.

For all reasons except number 3, other associated messages are present in the message log (MLOG). Reason number 3 indicates that the maximum number of entries (13) that the checkpoint record can hold has been reached. If this limit has been reached, verify that all 13 workstations that are defined in the record still exist in the current plan. If the workstations are not in the current plan, the workstation name can be blanked out or zeroed to make the position eligible for a new workstation. Alternatively, you can delete and reallocate the EQQEVDS data set. The entries are built only for workstations in the current plan. Refer to Customization and Tuning for details of instructions for deleting and reallocating an EQQEVDS data set.

EQQW780E

FT WORK STATION OPTION INVALID OR NOT DEFINED

You have entered an incorrect FTW value. Allowed values are: Y for FTW, or N for not FTW.

The system waits for you to respond.

Enter the correct value.

EQQW781E

IF THE FTW OPTION IS SET TO YES, DO NOT DEFINE THE DESTINATION

For a fault-tolerant workstation, the destination value is not defined.

The system waits for you to respond.

Enter the correct value.

EQQW782E

IF THE FTW OPTION IS SET TO YES, THE WS TYPE MUST BE COMPUTER

For a fault-tolerant workstation, the workstation type must be only C Computer.

The system waits for you to respond.

Enter the correct value.

EQQW783E

IF THE FTW OPTION IS SET TO YES, THE REP.ATTR. MUST BE AUTOMATIC

For a fault-tolerant workstation, the reporting attribute of the workstation must be only A Automatic.

The system waits for you to respond.

Enter the correct value.

EQQW784E

FT WORKSTATION HAS DEFAULT VALUES EQUAL N FOR PLANNING CONTROL

For a fault-tolerant workstation, the resources must have the value equal N for planning and control.

The system waits for you to respond.

Enter the correct value.

EQQW785E

FT WORKSTATION HAS DEFAULT VALUES FOR AVAILABILITY

For a fault-tolerant workstation, the availability must have the default values.

The system waits for you to respond.

Enter the correct value.

EQQW786E

FT WORKSTATION HAS DEFAULT VALUES FOR ACCESS METHOD

For a fault-tolerant workstation, the access method must have the default values.

The system waits for you to respond.

Enter the correct value.

EQQW787E

FOR FT WORKSTATIONS RESOURCES CANNOT BE USED AT PLANNING

For a fault-tolerant workstation you must specify not to use the R1 and R2 resources availability during daily planning.

The request is rejected.

Enter the correct value.

EQQW788E

FOR FT WORKSTATIONS RESOURCES CANNOT BE USED FOR CONTROL

For a fault-tolerant workstation, you cannot specify to submit a job if the requested R1 and R2 resources amount is only available.

The request is rejected.

Enter the correct value.

EQQW789E

IF THE FTW OPTION IS SET TO YES, THE STARTED TASK MUST BE N

For a fault-tolerant workstation, the started task attribute of the workstation must be only 'N' No.

The system waits for you to respond.

Enter the correct value.

EQQW790E

THE ALTERNATE WORKSTATION CANNOT BE A FAULT-TOLERANT WORKSTATION

It is impossible to assign a fault-tolerant workstation as an alternate workstation in the database.

Request is rejected.

Enter the correct value.

EQQW791W

FT WORKSTATION HAS DEFAULT VALUES FOR A, M AND R ATTRIBUTES

The availability, the access method, and the resources for a fault-tolerant workstation must have the default values.
  • Resources not allowed
  • Access method not available
  • Open intervals always opened

None.

To set the default values automatically for the fault-tolerant workstation, press the PF3 key or the END command. To save the new settings change the fault-tolerant workstation to a computer workstation with the automatic reporting attribute.

EQQW792E

Z-CENTRIC AGENT OPTION ALLOWED ONLY FOR COMPUTER AUTOMATIC

The Z-CENTRIC AGENT option is allowed only on a Computer Automatic workstation.

None.

Change either the workstation type or the selected option.

EQQW793E

Z-CENTRIC AGENT OPTION NOT ALLOWED WITH STC OPTION

The STC option is not allowed when the Z-CENTRIC AGENT option is selected.

None.

Change one of the selected options.

EQQW794E

DESTINATION TYPE IS NOT ALLOWED FOR THE WORK STATION

The destination specified is not set in the ROUTOPTS statement (with either the HTTP or HTTPS keyword).

The workstation is not modified or created.

Change the destination defined for this workstation.

EQQW795E

DESTINATION CANNOT BE BLANK

A workstation with the Z-CENTRIC AGENT option selected supports only non blank destinations.

None.

Specify a valid destination.

EQQW796E

DESTINATION CANNOT BE BLANK

The command issued is not valid for an operation defined on a Z-CENTRIC AGENT workstation.

The command is not run.

Specify a valid command.

EQQW797E

INCONSISTENT OPTION FOR AN OPERATION ON Z-CENTRIC OR DYNAMIC WORKSTATION

The operation option specified is not supported on operations defined on HCL Workload Automation Agent or dynamic agent workstations.

None.

Specify a valid option.

EQQW798E

ACTION ALLOWED ONLY FOR OPERATIONS ON FT AND Z-CENTRIC WORK STATIONS

The operation command specified is supported only on operations defined on fault-tolerant or z-centric workstations.

None.

Specify a valid command.

EQQW799E

INVALID FIELD FIELD VALUE IF OPERATION RUNS ON Z-CENTRIC OR DYNAMIC.

You tried to modify or add an operation that runs on a z-centric or dynamic agent workstation, but the value set for field FIELD is not valid. For field FIELD, the following values are allowed:
CRT
Workload monitor critical path
SE
Scheduling Environment name

The request is rejected.

Specify a valid value.

EQQW800E

INVALID OPTION

Z-Centric option not allowed with Dynamic option.

The system rejects the option.

Specify either z-centric or dynamic option.

EQQW801E

INVALID COMMAND

The O command is allowed only for z-centric or dynamic workstations.

The system rejects the invalid command.

Specify a valid command.

EQQW802E

VALUE INVALID. ALARM=YES

Correct values are Y, N, A or blank.

The system rejects the invalid value.

Specify a valid value.

EQQW803E

DYNAMIC OPTIONS NOT ALLOWED FOR Z-CENTRIC WORKSTATION

Dynamic options are not supported for HCL Workload Automation Agent workstations.

Specify N for HCL Workload Automation Agent workstations.

None.

EQQW804E

INCONSISTENT DYNAMIC OPTIONS

Dynamic options have been specified incorrectly, for example, the broker option is specified as Yes and the pool name is also specified. You cannot specify both of these options together.

The workstation changes are not saved.

You specified the Dynamic options incorrectly, for example, the broker option is specified as Yes and the pool name is also specified. You cannot specify both of these options together.

EQQW805W

POOL INFORMATION HAS BEEN RESET IN COPIED WORKSTATION

The workstation description record has been created and added to the workstation description database but the Pool or Dynamic Pool information has been reset and the Broker option is set to Yes.

None.

If you want to create a Pool or Dynamic Pool workstation, use the Dynamic Workload Console.

EQQW902E

JCC IS LOOPING ON DATA SET DSNAME FOR JOB JOBNAME - JOBNUM. PROCESSING ON THIS DATA SET IS SKIPPED.

This message is stored in the MLOG file of the controller or tracker when the job completion checker (JCC) detects a loop while reading a data set from the spool. If the same data set name is always returned, JCC stops the loop and skip the specific job processing. The job is identified by job name JOBNAME and Job ID JOBNUM. The data set is identified by the data set name DSNAME.

A loop has been detected by JCC, which performs the following actions:
  1. Stops processing the current and remaining data sets for the job being processed.
  2. Applies the actions set in the SYSOUTDISP parameter, if possible.
  3. Issues message EQQW902E to notify the problem occurred to the job being processed: the job is set to error status JCCE unless the system has already set another error code for the job
  4. Switches to process the next job in the JCC queue.

None.