The value for MAX USAGE LIMIT is not valid.

The group ID value contains characters that are not valid.

The ON COMPLETE value is not valid.

You have entered an invalid character in the field. It must be either a OCHCYES or a OCHCNO.

You must not leave this field blank.

You have entered an invalid quantity in the field. It must be in the range 1–999999.

You have entered an invalid keep on error option.

You have entered an invalid name.

You have entered an invalid day. Enter either a valid day or a valid date.

You have entered a combination of day/date and time that is invalid because it overlaps another interval.

You have entered an invalid combination of to-time and from-time.

Data entry error; see Data entry errors.

Valid to-times are 00.00 through 23.59.

You have selected to view an operation that no longer exists in the current plan.

You have requested to delete an operation from the queue or list that no longer exists in the queue or list.

You have entered an invalid value in the rules field.

The MAX USAGE TYPE value is not valid.

You have entered an invalid day in the field. It must be in the range 1–366.

You have entered an invalid deviation in the field. It must be in the range -999999 to 999999.

Data entry error; see Data entry errors.

Valid from-times are 00.01 through 24.00.

You have entered the name of a workstation that does not exist.

You have entered a workstation that has already been defined as connected to the resource.

You have attempted to access either the in-use list or waiting queue for a special resource and it has no operations either using or waiting for it.

You have entered an invalid value in the On Error field.

You have entered the name of a workstation that contains invalid characters. The first character must be a national character, an alphabetic character, or one of the HCL Workload Automation for Z generic selection characters. The remainder of the workstation name must consist of alphanumeric characters, national characters or HCL Workload Automation for Z generic search characters.

You have attempted to access the list of connected workstations that acts as the defaults, but none have been defined.

You have attempted to access the list of connected workstations in an interval for which no list has been defined. The default connected workstations that are defined for this special resource are used.

You have attempted to access the list of intervals, but none have been defined.

The special resource has been created and stored.

The special resource has been modified and stored.

The special resource has been deleted and removed.

You have entered an invalid value in the usage field.

You have attempted to access the special resource database for the modify current plan, but you are not authorized to access it.

You entered a not valid value for filtering on operations having pending predecessors.

You have attempted to create a special resource that already exists.

You have attempted to access the special resource description (RD) database, but you are not authorized to access it.

The special resource has no operations in the current plan that are currently allocated to it.

The special resource has no operations in the current plan that are currently waiting for it.

No special resource (or resources) matched the generic or nongeneric search criteria that you specified to generate a list of special resources.

The special resource could not be found.

The operator is adding a dependency on a special resource to a job running on a Fault Tolerant Workstation. The system warns that the job could run even if the resource is not available. This could only happen if it is the first dependency on a special resource for this job; in fact, when there are no dependencies on Special Resources, the WS decides by itself if the job can start or not. So it could happen that the WS starts the job before being notified that the dependency has been added. In this case if the resource is available the scheduler allocated it correctly; or else if the resource isn’t available, it is overallocated.

HCL Workload Automation for Z could not delete the special resource data space. The storage is not freed.

A data space has been successfully created for special resource records. SIZE shows the number of pages (each 4096 bytes) used to create the data space. NUM shows the maximum number of special resource records that the data space can contain.

HCL Workload Automation for Z uses a minimum of 20 pages.

HCL Workload Automation for Z could not create a data space for special resource storage. Reason code REASON is set by the DSPSERV service. SIZE shows the number of pages (each 4096 bytes) that HCL Workload Automation for Z needed. NUM shows the number of special resource records that HCL Workload Automation for Z wanted to store in the data space.

A requested special resource RESNAME did not exist in the current plan, but has been dynamically added to the special resource data space by you or by the function USER. Status STAT=NEW means that the special resource did not previously exist in the resource description (RD) database. Status STAT=OLD means that the special resource had already been defined.

This message can be issued at daily planning, when an operation becomes ready or when a special resource event record is processed.

A HCL Workload Automation for Z subtask encountered an unexpected error when accessing a resource in the resource data space.

A data space for special resource records has been successfully extended. SIZE shows the number of pages (each 4096 bytes) to which the data space was extended. NUM shows the maximum number of special resource records that the data space can contain.

The normal mode manager has started a current plan copy process. This copy process causes a backup of the special resource data space. Updated records in the data space are written to the current plan extension data set (EQQCXDS).

The normal mode manager has successfully written all updated records from the special resource data space to the current plan extension data set (EQQCXDS).

The normal mode manager (NMM) could not write all updated records in the special resource data space to the current plan extension data set (EQQCXDS).

This message is issued to the message log when a special resource is too large to fit into the CX file.

An SRSTAT command with LIFESPAN interval time 0 was specified for the special resource RES. As a consequence, the LIFESPAN pending action for the resource has now been removed.

The MAX USAGE LIMIT value was set to 0 to deactivate the MAX LIMIT function for the special resource RES.

The value for the usage counter was greater than 0 because some operations using this special resource were run with MAX USAGE LIMIT function active.

The global availability of the special resource RES was changed to the value STATUS. This occurred because the special resource usage counter exceeded the MAX USAGE LIMIT value set for the special resource. The current global availability value was set according to the MAX USAGE TYPE value of the special resource.

After the global availability was changed, the usage counter was reset to 0. Consider that the usage counter is increased by 1 at each job start.

The global availability of the special resource RES was changed to the value STATUS. This occurred because the operation identified by the application name APPLID, Input Arrival time IA, and operation number OPNO was completed.

The global availability of the special resource RES was changed to the value STATUS. This occurred because the LIFESPAN interval, specified through SRSTAT or data set triggering mechanism, expired. To update the special resource, the new LIFESPAN global availability value is used.