You have attempted to access the application description (AD) database, but you are not authorized to access it. Or, you do not have access authority to a minimum of one of the following HCL Workload Automation for Z resources that are used together with the AD database: the calendar database, the workstation description database, or in some cases, the long-term plan data set.

The application already exists with the valid-from date that you specified.

The predecessor you selected is not external. When defining an external dependency, you must specify the application ID of the external predecessor before selecting to describe it.

No application description matched the generic or nongeneric search criteria you specified to generate a list of applications.

You selected an application that does not have a matching application description. In a list of applications, in either the browse or list function, the application you selected was not found. The application may have been deleted or modified after the list of application entries was generated.

You have attempted to display the run cycles of an application for which no run cycles have been specified.

You have attempted to display the predecessors of an operation for which no predecessors have been specified.

This message indicates a programming error.

The application has been created and saved in the application description database.

The selected application has been modified and saved in the application description database.

The selected application has been copied and the copy has been saved in the application description database.

The selected application has been deleted from the application description database.

You specified too many internal predecessors.

You specified too many external predecessors.

You specified too many special resources.

Operation OP has an external predecessor workstation (EWS) that does not exist in the workstation description database.

You specified too many conditional dependencies.

You have attempted to display the special resources of an operation for which no special resources have been defined.

See text.

See text.

See text.

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

The selected operation has no conditional dependency, therefore the condition list is empty.

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

You entered the same option in both the condition rule fields.

The name of a variable table contains 1 to 16 alphanumeric characters, where the first character is alphabetic.

You have attempted to create an application, but the application ID that you specified already exists in the application description database.

Another user is currently updating the application you want to update.

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

You have attempted to refer to a JCL variable table. To do this, you need read authority to the JCL variable table database.

The deadline must be later than the input arrival time.

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

This does not prevent you from updating only one of the items.

You have attempted to display the user fields of an operation for which no predecessors have been specified.

A job name is required for an operation at a job setup, print, or computer workstation.

If you do not specify any value for the WLM POLICY field, the value specified in the WLM parameter of the OPCOPTS statement will be used.

In the variable duration and deadline table, the same rule name was specified in more than one line.

The input arrival time specified for the operation is later than one or more variable deadlines specified for the application.

The variable deadline that you specified is earlier than the application input arrival time for the application. This does not prevent you from saving the application description as it is.

The variable deadline time must be later than the input arrival time.

See text.

Valid input arrival times are 00.00 through 23.59.

Valid deadline times are 00.01 through 24.00.

The operation deadline that you specified is earlier than the application input arrival time for the application. This does not prevent you from saving the application description as it is.

The operation input arrival time that you specified is later than the deadline time for the application. This does not prevent you from saving the application description as it is.

The deadline time must be later than the input arrival time.

The application input arrival time that you specified is later than an operation input arrival time defined in the OPER table. This does not prevent you from saving the application description as it is.

The operation input arrival time that you specified is earlier than the input arrival time for the application. This does not prevent you from saving the application description as it is.

The operation deadline time that you specified is later than the deadline time for the application. This does not prevent you from saving the application description as it is.

No application input arrival time is specified for this application. This does not prevent you from saving the application description as it is.

See text.

The out-of-effect-from date for a run cycle must be later than the in-effect-from date.

The rule includes run cycle groups that generate more than one instance per day due to the definition of several IA times. But an Input Arrival time value is specified for the run cycle in the AD panels. This value overruns the IA times defined in the run cycle group and is used to define a single occurrence for each day while the multiple daily instances are ignored.

A problem has been detected in the referenced run cycle group.

The occurrence input arrival time specified is out of the prearranged range. Valid input arrival times are 00.00 through 23.59. The inout has therefore been converted to 00.00 the day after.

The occurrence deadline specified is out of the prearranged range. Valid deadline times are 00.01 through 24.00. The deadline has therefore been converted to 24.00 the day before.

The SUPPRESS IF LATE option can be YES only when the TIME DEPENDENT option is specified as YES.

See text.

See text.

Valid deadline WTO options are Y for Yes, and N for No.

The operation arrival date is earlier than the occurrence. This is accepted, but might not be what you intend.

See text.

The REPEAT END TIME must be a value between the input arrival time of the run cycle and the calendar work day end time of the application.

See text.

See text.

See text.

See text.

See text.

See text.

You have tried to define a variable table ID that does not exist in HCL Workload Automation for Z's database.

See text.

See text.

See text.

See text.

See text.

Valid print option characters are A for always and C for conditionally.

See text.

The SUPPRESS IF LATE option must be specified when the TIME DEPENDENT option is specified as YES.

See text.

Valid job option characters are Y for yes and N for no.

See text.

See text.

See text.

See text.

Operations on a computer workstation can use only one parallel server.

See text.

See text.

See text.

The JCL edit/browse option can be called only if a jobname has been specified.

You cannot define the same job as both conditional and normal predecessor.

You cannot define the same job as both conditional and normal predecessor.

See text.

The operation number specified for the conditional predecessor is equal to the owning operation number.

Valid special resource held options are S for shared and X for exclusive.

The number that you specified for a positive or negative run day offset is greater than the period interval value. If the period is type A, no occurrences are created in the long term plan (LTP) for this offset. If the period type is W, the message is issued as a warning but occurrences can still be created in the LTP.

Y deletes the application and N cancels the deletion of the application.

See text.

See text.

See text.

See text.

See text.

An application ID can be made up of the following valid characters: A through Z, 0 through 9, and national characters (that is, #, $, and @).

See text.

See text.

A stands for active and P for pending.

See text.

You have attempted to enter an active version of an application description but the maximum four active versions of the application description already exist in the application description database.

You have attempted to enter a pending version of an application description but the maximum four pending versions of the application description already exist in the application description database.

You have attempted to copy a pending version of the application description but only an active version can be copied.

In the copy function, one of the three key fields (application ID, status, or valid-from key fields) must be changed to create a new version of an existing application description, or a new application description.

The list of run days cannot contain duplicate offsets.

See text.

The list of operations cannot contain duplicate operation numbers.

The list of predecessors cannot contain duplicate predecessors.

The list of special resources cannot contain duplicate resources.

The specified external predecessor application does not exist in the application description database. This does not prevent you from saving the application as it is.

The specified external predecessor application does not exist in the application description database, so the predecessor workstation name cannot be picked up. Therefore, you must specify the predecessor workstation name.

The specified external predecessor operation does not exist in the external predecessor application. This does not prevent you from saving the application as it is.

The specified external predecessor operation does not exist in the external predecessor application, so the predecessor workstation name cannot be picked up. Therefore, you must specify the predecessor workstation name.

The print operation number (OP) can have only one CPU internal predecessor.

The job setup operation number (OP) must have the same job name as any of its CPU successors.

The print operation number (OP) must have the same job name as its CPU predecessor.

The application valid-from date for a previously defined application description version has been modified. The valid-from date now falls within the validity period of another version of this application description.

The specified external predecessor application has pending status. This does not prevent you from saving the application as it is.

You specified the same conditions details in more than one condition definition.

The out-of-effect-from date must be later than the in-effect-from date.

The print function can handle up to 12 print items at a time.

No more than five sort items can be selected to be part of the cross reference list.

See text.

See text.

The digits representing the sort order must be continuous and start with the digit 1.

You have attempted to read the operator instruction (OI) database, but you are not authorized to read it.

You have attempted to update the operator instruction (OI) database, but you are not authorized to update it.

See text.

See text.

A job name can be made up of the following valid characters: A through Z, 0 through 9, and national characters (that is, #, $, and @). The first character must be alphabetic or national, the remaining characters can be alphabetic, numeric, and national characters.

See text.

A group ID can be made up of the following valid characters: A through Z, 0 through 9, and national characters (that is, #, $, and @).

See text.

See text.

See text.

This message indicates a programming error.

This message indicates a programming error.

The table of pending updates cannot contain duplicate updates.

The table cannot contain duplicate rows.

It is not allowed to specify more than 25 pending updates in this session.

A valid batch job type is T for trial run or U for updating run.

You have attempted to update the application description database, but you are not authorized to update it.

You have attempted to read the calendar database, but you are not authorized to read it.

You have attempted to read the workstation (WS) description database, but you are not authorized to read it.

The data that you have specified for mass updating is longer than the maximum length allowed for the data item.

This message indicates a programming error.

See text.

See text.

See text.

See text.

See text.

See text.

See text.

See text.

See text.

See text.

See text.

When the name of the data set is specified, it is not necessary to specify the application IDs.

See text.

The application has no operations. You must specify at least one operation.

The predecessor operation (predecessor operation number PO) was not found for the operation (operation number OP). An internal predecessor operation must exist within the application.

The operation (operation number OP) has no predecessor or successor connections to the application.

The operation (operation number OP) of this application specifies a workstation (workstation name OPWS), which was not found in the workstation description database.

A loop was detected in the operation (operation number OP) dependency network which must be corrected. For example, operation 10 has operation 5 as its predecessor, and operation 5 has operation 10 as its predecessor.

When modifying an application, the valid-from date cannot be changed to a date later than the valid-to date.

If the time-dependent job option is specified as YES, an operation input arrival time must be specified.

The job setup operation (operation number OP) must have a CPU successor operation.

The print operation (operation number OP) must have a CPU predecessor operation.

See text.

See text.

While specifying an external conditional predecessor, you entered no workstation name and a number that does not correspond to any operation defined for the external application.

While specifying an external conditional predecessor, you entered a number that does not correspond to any operation defined for the external application.

See text.

See text.

See text.

The field indicated by the cursor contains one or more superfluous shift-out or shift-in characters.

The field indicated by the cursor contains out-of-range DBCS characters. With the exception of DBCS blank, X'4040', each byte must be within the range X'41' - X'FE'.

The field indicated by the cursor is specified as a DBCS field, and requires two bytes per character.

See text.

See text.

See text.

The condition has no dependencies defined. You must specify at least one condition dependency.

The COND command is not supported on an end-to-end operation that is not centralized.

You are trying to set the centralized option to NO for an end-to-end operation that has conditions defined.

You entered an upper boundary greater than the lower one as range values.

The specified predecessor does not exist in the database.

See text.

See text.

See text.

You requested to create a new condition for an operation that is not in ready or waiting status.

You requested to create a condition dependency specifying a predecessor that was removed by daily planning.

You specified the maximum allowed value as first boundary of a range.

STEPNAME can be made up of the following valid characters: A through Z, 0 through 9, and national characters (that is, #, $, and @). The first character must be alphabetic or national, the remaining characters can be alphabetic, numeric, and national characters.

See text.

PROCSTEP can be made up of the following valid characters: A through Z, 0 through 9, and national characters (that is, #, $, and @). The first character must be alphabetic or national, the remaining characters can be alphabetic, numeric, and national characters.

See text.

See text.

See text.

See text.

See text.

The selected information cannot be specified for remote engine workstations.

Remote job information is not available for non-remote engine workstations.

See text.

Remote job information must be specified if the operation is defined to run on a remote engine workstation.

The operation option specified is not supported on operations defined on remote engine workstations.

The COND command is not supported on an operation defined on a remote engine workstation.

See text.

See text.

See text.

No job descriptions were found matching the generic or non-generic search criteria that you specified to generate a list of jobs.

The job that you selected from a list does not have a matching job description. The job may have been deleted or modified after the list of job entries was generated.

You tried to display the run cycles for a job for which no run cycles have been specified.

The job has been created and saved as a job description.

The job has been modified and saved as a job description.

See text.

You tried to create a job with an ID that already exists in the application description database.

Another user is currently updating the job that you want to update.

See text.

The selected job has been deleted from the job description database.

You have tried to enter the job description dialog but DBCS bracketed input has been defined for application IDs in your installation. The application ID of job descriptions must be the same as the job name. Job names cannot be entered in DBCS bracketed format.

The workstation pointed to by the cursor must be entered.

The workstation must be a workstation with the JCL preparation indicator set to Y.

The workstation must be a MANUAL workstation.

See text.

You tried to select predecessors for a job. No predecessors were found with the specified selection criteria.

See text.

Either a run time has been entered or run cycles are missing.

If you are currently defining a job, the application ID must be completed for a predecessor.

A group definition cannot contain operations.

The current application description (AD) references an application group definition that cannot be found in the AD database. Either you entered the wrong name, or the application group has not yet been created, or the application group has a pending status (not selectable for processing), or you are not authorized to reference it. If you want to, and if you are authorized, you can save the current application description while it references an application group that does not exist. Such an application description is not used to create occurrences in the long term plan (LTP).

You cannot specify a group definition ID when run cycles already exist.

You can specify a group definition ID only when the application type is A.

The selection criteria that you have specified contains an invalid application type. OCHCSTN and OCHCGRP are the national language characters for 'A' (applications) and 'G' (group definitions).

You have specified an invalid application type. OCHCSTN and OCHCGRP are the national language characters for 'A' (applications) and 'G' (group definitions).

An application that references a group definition for run cycle information does not itself contain run cycles.

A group definition (application type=G) does not contain operations.

A job description that references a group definition for run cycle information cannot itself contain run cycles.

A job description that references a group definition for run cycle information cannot itself contain run cycles.

You cannot specify priority for a group definition.

A calendar ID cannot be specified for an application that references a group definition for run cycle information.

Group definitions can be specified only when the application type is A (application) or blank (both application and group definition).

Calculate and print rundays, or Modify long term plan (LTP) can be requested only for applications.

The group definition contains no run cycle information. Applications that reference this group definition are automatically included in the long term plan.

A calendar ID cannot be specified for a job that references a group definition for run cycle information.

An application that references a group definition for run cycle information cannot itself contain run cycles.

In the user field table, the same user field name was specified in more than one line.

Too many user fields were specified; the maximum allowed is 120.

Too many variable durations and deadlines were specified.

A rule-based run cycle (type R or E) was inserted or replicated in the run cycle table, but no rule definition was specified.

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

You have specified a rule name that has already been defined for a rule-based run cycle for this application description.

You have modified the type from an offset-based run cycle to a rule-based run cycle, or vice versa. You can only change type within the run cycle subtype; that is, N and X for offset-based run cycles, or R and E for rule-based run cycles.

The specifies value cannot exceed the number of specified condition dependencies.

See text.

You specified a value not compatible with condition check type or operator.

The condition status does not allow the requested change.

You cannot change the condition identifier.

This value is wrong for a fault-tolerant workstation. The fault-tolerant workstation requires a default value.

This option is wrong for a fault-tolerance workstation. The fault-tolerant workstation requires a default value.

The fault-tolerant workstation does not accept a general workstation as a predecessor.

The fault-tolerance workstation does not accept a printer workstation as a predecessor.

System automation information is available for a workstation that is not-Automation.

System automation information was not defined, but at least the command text is required for an Automation workstation.

Automation information were specified for a not Automation workstation.

Automation information is not available for an Automation workstation.

This option is wrong for a System Automation workstation. The System Automation workstation requires the default value.

For a job defined on a remote workstation (shadow job) you must set the automatic submission to Yes (Y), otherwise the cross dependencies feature does not work properly for that job.

An incorrect request was received from the Dynamic Workload Console.

The job library dynamic allocation failed.

The program cannot open the job library.

The record length of the job library is incorrect.

The program cannot find the JCL member in the job library.

The program cannot read the JCL member in the job library.

The program cannot close the JCL member in the job library.

The operation cannot be performed because JCL member specified is empty.

The job library dynamic deallocation failed.

The operation cannot be performed because of a memory problem