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.

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 workstation description record has been updated and added to the workstation description database.

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

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

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

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

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.

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

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

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

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

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

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

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.

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

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

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.

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

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 initialization of the job completion checker (JCC) has completed and the JCC has been requested to stop execution.

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 abend prevented the event writer from writing an event record to the event data set.

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.

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

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

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.

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

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

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.

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

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.

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

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 error occurred when the joc completion checker (JCC) was trying to open a SYSOUT data set for the job JOBNAME(JOBNUM).

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

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

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

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 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 found job submit records in a submit/release data set that could not be processed because some submit records were missing.

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

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

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.

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

An abend in the event filtering exit prevented the event writer from writing an event record to the event 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.

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 event data set referenced by ddname DDNAME has been allocated with an invalid logical record length.

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.

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 same class has been defined in the CHKCLASS keyword in the JCCOPTS statement and in the DSTCLASS keyword in the RCLOPTS statement.

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

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 could not locate the event filtering exit load module, EQQUX004.

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.

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.

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.

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

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

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

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.

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.

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 encountered an unknown record type when skipping records of the submit/release data set that are too old.

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

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

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.

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 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 scheduler could not locate the subsystem routine used to send events to an FTW (fault-tolerant workstation).

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

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.

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

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 end-to-end task could not open one of its event data sets (end-to-end input/output queue).

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

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

The Translator process has successfully switched the new Symphony File.

The Translator was unable to switch the new Symphony file.

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 is unable to open the PDSE specified by ddname EQQTWSCS.

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

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.

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.

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.

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.

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.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

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

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

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

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

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

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

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

The alternative workstation cannot be the current workstation.

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.

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

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

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.

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.

Data entry error; see Data entry errors.

All workstations closed has been updated.

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

An ISPF table contains duplicate entries.

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

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

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.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

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.

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.

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 specified destination is not defined to HCL Workload Automation for Z in the ROUTOPTS initialization statement.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

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

Automation option not valid or not defined.

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

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

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

Data entry error; see Data entry errors.

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.

Data entry error; see Data entry errors.

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

Data entry error; see Data entry errors.

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

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

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.

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

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

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

You cannot specify this option for virtual workstations.

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

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

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 specified destination is duplicated.

Data entry error; see Data entry errors.

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

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

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.

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.

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

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.

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

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 workstation analyzer encountered a VSAM error when reading or updating the current plan data set.

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

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

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.

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

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

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 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 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 joblib I/O exit was called to retrieve a job to be submitted, but the exit did not return any data.

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.

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

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.

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

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

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

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.

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

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 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 workstation analyzer task has encountered a severe error.

The workstation analyzer task has encountered a severe error.

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 scheduler has been requested to submit a job that needed the pre-submit task tailoring, but the tailoring failed.

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

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

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

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

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.

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

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

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

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

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

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.

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.

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

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

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

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

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

This message is repeated every ten minutes.

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 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 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 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 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 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 received an unexpected return code when the MGCR macro was invoked to start an STC.

The corresponding operation is set to status E.

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 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 submittor task encountered an I/O error reading the started task temporary proclib file, EQQSTC.

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

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

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.

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 level of the EQQEXIT macro in JES2 EXIT51 (TWSXIT51) is at a lower maintenance level than the HCL Workload Automation for Z subsystem.

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.

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.

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.

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Z-Centric option not allowed with Dynamic option.

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

Correct values are Y, N, A or blank.

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

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

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.