You have attempted to access the ready list, but you are not authorized to access it.

You have attempted to access the job setup facility, but you are not authorized to access it.

Event reader ERC processing has completed and control is returned to the HCL Workload Automation for Z subsystem.

Event reader ERC. has been requested to stop while waiting for positioning information in the event data set to become available.

Event reader ERC has been restarted. This message is issued only for event readers that service the NCF application at remote sites. The probable reason is that the event reader is restarted either with new positions in the event data set after a control plan refresh or when an NCF session is reestablished after failure.

An event reader task was unable to locate the EQQERBEX load module.

Event reader ERC encountered a header record that contained invalid information, for example, the track capacity and the total number of records in the data set were missing. The most probable reason is that a new event data set has been created and it is being formatted by the event writer before usage. The header record is not updated with the characteristics of the data set until the formatting job has completed. This might take some time if the event data set is large.

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

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

Event reader ERC could not open its associated input data set (ddname DDN).

Event reader ERC encountered a situation where the event writer overwrites event records not yet processed by the event reader. Event data sets are used in a wrap-around fashion and for some reason the event reader cannot keep up with the event writer.

Event reader ERC has encountered initialization errors.

Event reader ERC has successfully completed its initialization processing and is now ready.

Event reader ERC encountered an I/O error when reading its associated event data set (ddname DDN). The event data set is defined on the DDN ddname statement.

Event reader ERC found that the KEYWORD keyword was not specified on the ERDROPTS statement.

Event reader ERC found that the keyword KEYWORD was not specified correctly on the ERDROPTS statement. If the ERSEQNO keyword specification was in error, ERC consists of **.

Event reader ERC found no ERDROPTS statement in the member (specified on the OPCOPTS statement) that was to hold initialization parameters for an event reader. Because no event reader sequence number is available, ERC consists of **.

The ready list layout table already contains the layout that you tried to add.

The layout has been successfully added to the ready list layout table and saved.

The layout has been successfully deleted from the ready list layout table.

The layout has been successfully updated in the ready list layout table.

A layout is required for the requested ready list display.

HCL Workload Automation for Z could not open the ready list layout table.

You have attempted to delete an installation-defined layout, but you are allowed to delete only your own layouts.

The layout RLLAYOUT does not exist.

The layout RLLAYOUT does not exist.

Data entry error.

Data entry error.

Data entry error.

OCHCYES is the national language character for Y (yes) and OCHCNO is for N (no).

The ready list was to be displayed using the default layout, RSRLT, that is, the layout that was used last time the ready list was displayed for the same workstation. That layout could not be found and the first layout in the layout table is used.

The Ended in Error List cannot be displayed without a layout ID.

There is an invalid parameter in the input to the ready list module (module name MODNM).

The active exit for this ready list layout ended with a return code greater than or equal to 8.

The active exit for this ready list layout has returned a code of 9 in the status field URNSTAT, which means cancel the request.

Data entry error.

Data entry error.

A character that you have specified as a selection criterion for status codes is not a valid status code.

There are no operator instructions for the operation that you selected in the ready list.

There is no JCL for the operation that you selected in the ready list.

There is a JCL record for the operation that you selected, but the record does not contain JCL.

A read failed when trying to read the JCL record with the key JSADIDJSIADJSIATJSOPNUM. The key is derived from ISPF variables set up in a panel.

In a modify control plan (MCP) dialog for a JCL edit session the controller returned data that could not be retrieved and displayed, because not enough storage had been preallocated to receive it.

Data entry error.

STR is the national language character for R (ready), STS is for S (started), STI is for I (interrupted), STE is for E (ended-in-error), and STC is for C (complete).

Data entry error.

STR is the national language character for R (ready), STS is for S (started), STI is for I (interrupted), STE is for E (ended-in-error), and STC is for C (complete).

Data entry error.

OSOPSTS is the national language character for S (started), OSOPSTI is for I (interrupted), OSOPSTE is for E (ended-in-error), and OSOPSTC is for C (complete).

Data entry error.

OSOPSTS is the national language character for S (started), OSOPSTE is for E (ended-in-error), and OSOPSTC is for C (completed).

Data entry error.

OSOPSTI is the national language character for I (interrupted), OSOPSTE is for E (ended-in-error), and OSOPSTC is for C (complete).

You have attempted to set an operation in the current plan to ready, but only operations with status arriving can be set to ready.

You have attempted to set an operation in the current plan to started, but the operation has already started.

You have attempted to interrupt an operation that has not yet started. You can interrupt an operation only if it has already started.

You have attempted to set an operation in the current plan to ended-in-error status, but the operation is already set to that status.

You have attempted to set an operation in the current plan to complete status, but the operation has already completed.

You have attempted to interrupt an operation in the current plan, but the operation has already been interrupted.

Data entry error.

You have attempted to reset an operation that is waiting for arrival. This is not allowed.

You have attempted to reset an operation that is ready. This is not allowed.

The operation either cannot be read from the current plan or has another status, real duration, or error code than is displayed. The operation has been changed from its condition in the ready list.

The intended status change is not supported. You must enter a reset request and a request to get the desired status.

You attempted to reset an operation with error code OSEQ from the Ready List dialog. This cannot be done. The error code OSEQ indicates that a job began to execute before all the predecessors to the operation were complete.

You have attempted to update the JCL, but it is being updated by another user &usr.

Data entry error; see Data entry errors.

A duration of operation is required when setting the status to OSOPSTI, the national language character for I (interrupted).

Data entry error; see Data entry errors.

You tried to resolve variables using the program interface request JCLPREPA, with SIMTYPE FULL, and HCL Workload Automation for Z found one or more unresolvable variables in the JCL for the operation.

Data entry error.

The value that you entered is invalid according to the validation criteria defined for this variable.

Data entry error; see Data entry errors.

According to the definition of this variable, a value must be entered.

Data entry error; see Data entry errors.

If it is specified that a JCL variable requires a value other than blank, the default value must not be blank.

An error was detected during INSERT JS PROGRAM INTERFACE (PIF) processing. This message is issued in the EQQMLOG for the PIF job when a user tries to add a JCL already present in the JS file.

An error occurred while reading a JCL member.

Run cycle group name is missing or invalid.

A period/rule name must be specified.

A run cycle group with this ID already exists.

The run cycle group is being updated by another user. Try later.

One or more invalid characters were used in the subset name. Only alphanumeric characters are admitted.

See text.

The period name that you specified is not defined in the calendar database.

You have not entered a valid rule name. A valid rule name has a maximum of 8 characters, where the first character is alphabetical and the remaining characters are alphanumeric or national.

You selected a period, but failed to specify any offsets.