When an occurrence is deleted, the external predecessors are connected to the external successors. During this process, an operation record could exceed its maximum size; in this case, the deletion of the occurrence fails and this message shows the operation that cannot be modified.

This message is issued by the controller when you request to access an Application Description with application dependencies, but you are not using the level of code required to access this kind of objects. The user code level is identified by the “user level” value.

This message is issued by the controller when an occurrence add or modify caused the creation of a record too big to be stored in the plan. This might occur when you have a very high number of application dependencies.

This message is issued by the controller when the number of occurrences in the current plan exceeds the value specified by JTOPTS(MAXOCCNUM), in the percentage specified in PERCENTAGE.

The request to initiate a bulk discovery for an external monitor cannot be honored, because a planning activity is in progress.

The monitoring task has ended.

The monitoring task has encountered severe processing errors while sending data to the monitoring agent. The task has ended.

The monitoring task has encountered processing errors while sending data to the monitoring agent.

The monitoring task has ended unexpectedly while sending data to a monitoring agent

The monitor data set identified by DDNAME EQQMONDS contains invalid data.

A bulk discovery is already running

A bulk discovery has ended.

The controller monitoring task is trying to reconnect to the remote monitoring agent after a previous attempt to reconnect has failed.

You specified both the MONOPTS and TCPOPTS server initialization statements. Both of them contain host name and connection timeout parameters.

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

The monitoring task requires that the monitor data set is large enough to contain a minimum of 100 events. The data set defined by the DDNAME does not fulfill this requirement.

The monitoring task is unable to open the data set referenced by the DDNAME.

The monitoring task on the controller has connected to the remote monitoring agent. HOSTNAME indicates the host name or IP address of the remote monitoring agent.

The monitoring task could not close the data set referenced by the DDNAME.

The monitoring task data set utilization has reached the percentage indicated by the value of PERCENT. Some events might be lost.

The monitoring task data set utilization has reached 100%. Some events might be lost.

The TCP/IP connection between the HCL Workload Automation for Z monitoring task and the monitoring agent has experienced an error. The error is identified by ERRNO and TCPIPMSG.

The controller has failed to establish a connection to the remote monitoring agent identified by the hostname or IP address.

To use the function you selected, you must have access authority to the current plan.

To use the function you selected, you must have update authority to the current plan.

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 specified an external dependency that generates a loop. This must be corrected.

You specified an application that could not be found in the application description database. The application may have been deleted after the list of applications was created.

You specified an occurrence that was added to the current plan.

You specified an occurrence that was modified in the current plan.

You specified an occurrence that was deleted from the current plan.

In the current plan, the status of the specified occurrence was changed to rerun.

In the current plan, the status of the specified occurrence was changed to waiting.

You specified an occurrence that has been completed.

During the time taken to enter the modifications for the occurrence, at least one operation status has been updated because an automatic event has been processed.

You selected an occurrence that is being updated by another user.

You attempted to add an occurrence that already exists in the current plan or long-term plan.

You specified an application description that is currently being updated by another user.

In the Modify Current Plan dialog, you entered an invalid status for selecting occurrences in the current plan.

In the current plan, the status of the specified operation was reset to ready.

You specified an operation that has been completed.

You selected a function that attempts to modify an occurrence that has been deleted from the current plan.

The modify current plan request failed because of an I?O error.

Operations that have external dependencies to the occurrence that you attempted to modify have been changed in such a way that your modify request failed.

The modify current plan request failed because of an error in the HCL Workload Automation for Z subsystem.

The modify current plan request failed because of an error in the HCL Workload Automation for Z subsystem.

An attempt to delete an occurrence with status complete has been rejected because a daily planning batch program is currently creating a new current plan. Occurrences that were complete when the daily planning job started are removed, and are not available in the new plan.

The modify current plan request failed because of an error in the HCL Workload Automation for Z subsystem.

Data entry error; see Data entry errors.

The selected occurrence has no external dependencies.

The request requires an operation in error status with error code OSEQ to change status. There are restrictions as to how this can be done when the operation has uncompleted predecessors, that is, the operation is still out of sequence. This is not one of the accepted ways.

You entered an invalid code for selecting occurrences from the current plan in the Modify Current Plan dialog.

You tried to rerun an operation, but the JCL for this operation is being edited by another user.

HCL Workload Automation for Z was validating an occurrence to be added. A workstation referenced by an operation in this occurrence is not defined to the current plan.

It is possible that a new workstation has been created, but the daily plan batch program has not yet been executed.

HCL Workload Automation for Z submits a time dependent operation as soon as possible after its input arrival, but this time is not specified.

The Restart and Cleanup action for the operation might no longer be necessary, because the operation status or the job ID, or both, have changed. Before proceeding, ensure that you still want to restart this operation.

You tried to vary the status of a z-centric workstation to ACTIVE, but the workstation had been automatically set to OFFLINE. You cannot set to ACTIVE a z-centric agent the is not reachable.

An error code must be given for an operation in error.

Error code only has meaning for an operation in error.

The automatic job recovery request could not be processed because the operation record could not be read.

The status of the virtual workstation destination changed.

System information is not available for a virtual workstation because the workstation is associated to a list of destinations, not to a specific one.

The selected workstation has the VIRTUAL option set to N. The V command is only allowed for virtual workstations.

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

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

You requested to delete a dependency belonging to a logical condition.

The workstation status must be A, F, or O.

The restart option can be R (restart), E (set to error), or L (leave). The reroute option can be Y (yes, reroute operations) or N (no, do not reroute).

The alternative workstation is not defined in the workstation database.

The alternative workstation is not defined in the workstation database as a computer type workstation.

Fail?offline options do not apply to active workstations. If you change the status of a workstation to A (active), any previously defined fail?offline options are ignored.

An active workstation cannot have an alternative workstation.

The status of a workstation has changed, as you requested on the previous panel.

The alternative workstation cannot be the current workstation.

The alternate workstation must be of the same type.

It is not possible to change the Active/Offline status of a fault-tolerant workstation and, at the same time, change the Active/Offline status link status.

HCL Workload Automation for Z was validating an occurrence to be added. A Job definition referenced by an operation in this occurrence isn’t correctly defined in the EQQSCLIB library.

The application that the user is trying to add to the current plan contains an operation defined on a fault-tolerant workstation. This kind of operations cannot be added to the current plan if the end-to-end feature is not active.

The command to change the status or the link for workstation WSID has been sent as you requested in the previous panel.

An invalid modification request has been issued for an operation running on a Fault-tolerant workstation.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

You specified a deadline that is invalid because it is earlier than the input arrival time. However, the deadline value is accepted.

The date and time are required for the late start alert.

The date and time are required for the late start action.

The day and time are required for the deadline action.

No applications were found in the application description database, which met the selection criteria that you specified.

The day and time are required for the not started action.

You entered a value for the dependency resolution attribute that is not recognized by the Modify Current Plan dialog. You must change the value to one of the supported values defined by this message.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

The valid-from date and time of the occurrence that you attempted to add to the current plan lie outside the current plan end.

Data entry error; see Data entry errors.

In the occurrence that you are modifying, there is more than one network of dependencies. This is not allowed.

The job name (MOJBN) specified for the job setup, process, and print operations must be the same.

A print operation must be preceded by a process operation.

The specified workstation (MOWSN) does not exist in the current plan or you are not authorized to access this workstation.

A setup operation must be succeeded by a process operation.

A predecessor to operation MONUM is also a successor. This forms a dependency loop and is not allowed.

The specified dependencies create a loop in the operations network.

There is a record on the JS file that matches an operation on a computer workstation in the occurrence being added. This record was not added during the current Modify Current Plan dialog session.

An invalid input arrival date was specified while adding an application to the current plan.

The general service task could not process a request to manually define the status of the indicated condition dependency. The request is valid only for step dependencies that are undefined because of missing step-end information.

The general service task received an incorrect value when processing a request to manually define the status of the indicated condition dependency.

In MCP you can select the JCL browse function if operation is on a fault-tolerant workstation and is a non-centralized script. This action is allowed only when the JOBLIB and the SCRPTLIB are concatenated in the EQQJBLIB. If a member with the same name is present both in the JOBLIB and in the SCRPTLIB, then the JCL in the JOBLIB is displayed when browsing the non centralized script.

The operation is the only one of the occurrence.

The occurrence to be deleted or completed has a predecessor that is not yet in the current plan.

The operation that has an OSEQ error code cannot be modified to ERRCODE because the status of a predecessor is not C, D, nor X.

As a predecessor you can specify only O (Operation) or A (Application occurrence).

The command can be issued only for operations, not occurrences.

A request to modify or create an occurrence on the current plan specifies an input arrival time later than or equal to the current plan end time. All modifications to the current plan must be earlier than the current plan end time.

A request to create an occurrence in the current plan failed due to an I?O error.

A request to create an occurrence in the current plan failed because the occurrence already exists. No input arrival time was given in the request, which implies that a default input arrival time should be used.

A request to create an occurrence in the current plan failed because the current plan end time has passed. No input arrival time was given in the request, which implies that a default input arrival time should be used. The default input arrival time is the current time, consisting of the current date, current hour, and current minute. The request is rejected because the current plan ends before the current time.

A request to create an occurrence in the current plan failed because the Resolve Required option was Y (yes). There are also occurrences in the current plan that are possible successor occurrences, but the application description defines more dependencies than could be resolved using existing successor candidates.

A request to create or modify an occurrence in the current plan specifies an application ID and input arrival date and time that are the same as an existing occurrence in the long-term plan.

A Modify Current Plan action caused an application predecessor to be added to an operation running on a fault-tolerant or remote engine workstation. This is not allowed.

A request to create or modify an occurrence in the current plan failed due to a storage allocation failure. The reason code provides debugging information for the personnel.

The application description record defines an operation that has more special resources than are supported by the Create Occurrence function in the Modify Current Plan dialog.

The application description record defines one or more operations that have more special resources than are supported by the Create Occurrence function in the Modify Current Plan dialog.

The current occurrence contains an operation that contains too much information to be saved in the current plan data set.

An operation with system automation information was defined for a not-Automation workstation.

An operation without system automation information was defined for an Automation workstation.

System automation information cannot be read due to a missing security authorization, because AD.SECELEM, CP.SECELEM, or both are set in the AUTHDEF initialization statement.

No more occurrences of this application can be added. HCL Workload Automation for Z can handle approximately 870 occurrences of each application.

No more occurrences can be added to the current plan because either the maximum number of occurrences (32767) or the number specified in the MAXOCCNUM option of the JTOPTS statement has been reached.

The JCL for an operation in this occurrence has been edited. Changing the input arrival for this occurrence may cause the edited JCL to be lost.

You specified a condition type different from RC.

If you specify the procedure invocation step name, you must specify also the step name in the JCL procedure.

The first character must be one of the following: A through Z and national characters (that is, #, $, and @).

The first character must be one of the following: A through Z and national characters (that is, #, $, and @).

The procedure invocation step 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.

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

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

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 and the remaining characters can be alphabetic, numeric, and national characters.

A jobname must be given for an operation at a general workstation with the job setup option, or at a computer or printer workstation.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

You tried to change the status of an operation that has external or conditional successors already started, completed, suppressed by condition, or ended in error. This is not allowed. This situation can occur both if you try to change the status directly (for example, from the EQQMMGEP panel) and if you try to do it indirectly (for example, issuing a Step restart or Job Restart command).

Data entry error; see Data entry errors.

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

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 tried to change the status of an operation with external predecessors that are not completed, or conditions that are not true. This is not allowed.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

In the current plan, there are no operations that meet your selection criteria.

This message is issued when the Automatic Dep option is set to Y or P and the Resolve Required option is set to Y. When the message is issued on the EQQMAOCP panel, it means that the current occurrence could not be added to the current plan because one or more external predecessors defined by the application description could not be resolved. When the message is issued on the EQQMARXL panel, it means that one or more external predecessors displayed by the panel could not be resolved. The input arrival time for unresolved dependencies is blank.

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

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

The specified operation deadline is later than the occurrence deadline. This is accepted, but might not be what you intend.

Data entry error; see Data entry errors.

A dependency to a potential successor operation could not be added because the successor operation has already started.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors. It is not allowed to browse or edit JCL for non-processor operations.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

The specified operation has been added as a predecessor.

The specified operation has been added as successor.

Data entry error; see Data entry errors.

The value of this input field must be Y (for Yes), N (for No), or a blank (for no value). Read the help text for the panel, and decide which option you want.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

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

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

You selected more than one restart point in the application occurrence being rerun. You cannot use multiple restart points because the occurrence has external dependencies that would be updated by the rerun.

If you want to use more than one restart point, the application occurrence being rerun must be the only occurrence whose status changes.

The operation that you selected as a restart point has at least one pending or mandatory pending predecessor (not in the current plan).

Pending predecessors are marked with *P* in the predecessor type column at the far right of the panel. Mandatory pending predecessors are marked with *M*.

The manual HOLD command (MH) is not supported for operations with pending or mandatory pending predecessors.

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

When trying to start an auto recovery action, the scheduler found that there is a cleanup action in progress.

If the data store has been stopped, the auto recovery action cannot start unless a stop and start of the FL task is performed.

The dependent occurrence OCC was not found in the current plan.

Data entry error. See Data entry errors.

Data entry error. See Data entry errors

Data entry error. See Data entry errors

Only operations in status A, W, R, *, C, X, or E can be manually held.

For operations with pending predecessors, the manual HOLD command is not supported at all.

The operation has already been set to MANUAL HOLD by a Tivoli OPC dialog user.

The operation for which the MANUAL RELEASE command was issued, is not Manually HELD by a HCL Workload Automation for Z dialog user request.

For operations with pending predecessors, the MANUAL RELEASE command is not supported at all.

The operation for which the manual HOLD command was issued is now recognized to be HELD by Tivoli OPC.

A previously held operation has been release from hold at a Tivoli OPC dialog user's request.

Only operations in status A, W, R, C, X, or * can be NOPed.

For operations with pending predecessors, the NOP operation command is not supported at all.

The operation for which the NOP command was issued has already been NOPed by a dialog request.

The operation for which the UN-NOP command was issued, is not currently NOP.

For operations with pending predecessors, the UN-NOP command is not supported at all.

The operation has been recognized as no-oped by Tivoli OPC The operation is not executed, and dependent operations may be started as a result.

An operation has been successfully reset from its NOP indication at a Tivoli OPC dialog user's request.

An operation has been marked as EXECUTE by Tivoli OPC and is started without regard to the normal job submission criteria.

Only operations in status A, R or * can be the subject of an EXECUTE request.

To use the function you selected, you must have update authority to the EXECUTE resource.

The workstation on which this operation was scheduled is not a computer type workstation with the automatic reporting attribute.

The command is not supported by Tivoli OPC.

The command you issued is supported on automatic computer type workstations, or workstations with the nonreporting attribute.

The operation is scheduled on a workstation that is inactive. If alternative workstations are specified, these are also inactive.

You cannot request Tivoli OPC to set the next logical status for an operation that has been manually held.

You have issued a request of prompt reply, but the task was unable to satisfy it, because the request is not valid for a centralized script or for an operation not scheduled on fault-tolerant workstation.

Only an occurrence rerun request or internal scheduler actions can produce this kind of change, that might refer to the selected operation or its internal non-conditional successors.

It is not possible to change a non-fault-tolerant workstation with another FTW in the same operation in MCP.

In MCP it is impossible to change field FLD to operation, if this operation runs on a Fault-tolerant workstation. FLD values:

WS = workstation

JNM = Job name

PS = Parallel servers

R1 = Resource 1

R2 = Resource 2

It is impossible to insert an operation when the same number was use by a deleted operation with a fault-tolerant workstation.

It is impossible to change a fault-tolerant workstation with a workstation that is not fault-tolerant.

It is impossible to assign a Fault-tolerant workstation as an alternate workstation in Modify Current Plan.

In Modify Current Plan, you cannot change the operation status to "I" on fault-tolerant workstation.

You cannot change the operation status to R for a fault-tolerant workstation in Modify Current Plan if the operation status is S or if the operation has a recovery job that is running.

You cannot change the operation status to W for a fault-tolerant workstation in Modify Current Plan if the current status is S or if it is A, R, * and the operation does not use special resources or centralized script support. Moreover, you cannot re-run an operation that completed correctly if it has a fault-tolerant workstation successor in waiting status.

You are modifying or adding an operation running on a Fault-tolerant workstation and you entered an invalid value for field FLD.

The following are values for FLD:

AEC = Automatic error completion

AJR = Automatic job hold/release

CRT = Workload monitor critical path

HRC = Highest return code

SUB = Automatic job submission

WTO = Issue deadline WTO

You are changing the status of an operation running on a fault-tolerant workstation and the new status you specified is invalid. As a rule, only R for Ready or C for Completed are accepted. The R value is not allowed if the operation is running or if it has a recovery job that is running.

Error in data entry; see Data entry errors.

When the operation that you are updating was added to the current plan, the TWSJOBNAME parameter in the JTOPTS statement was set to EXTNAME or to EXTNOCC; this choice implies that the extended name is used to generate the job name in the symphony file. Now you are modifying the operation but you cannot change the Extended Info field because it is used as a key to identify a job in the symphony file.

You cannot change the Extended Name field to "operation" in the MCP, because, when the operation that you are updating was added to the current plan, the TWSJOBNAME parameter in the JTOPTS statement was set to EXTNAME or EXTNOCC; this choice implies that the extended name is used to generate the job name in the symphony file. Now you cannot change the Extended Info field because it is used as a key to identify a job in the symphony file.

You cannot change the Extended Name or Jobname fields to "operation" in the MCP because, when the operation that you are updating was added to the current plan, the TWSJOBNAME parameter in the JTOPTS statement was set to EXTNAME or JOBNAME; this choice implies that either name is used as a key in the symphony file.

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

You can modify a condition while its status is undefined.

A predecessor to operation OPNO is also a successor. This forms a dependency loop and is not allowed.

Data entry error; see Data entry errors.

The modify current plan (MCP) service detected a loop while processing a request to modify a network with conditional dependencies defined.

While defining a conditional dependency in the current plan, you entered an invalid row command.

The scheduler did not add the indicated condition dependency to prevent inconsistencies in the dependency network.

The command EX was issued to execute a shadow job whose bind process was already started.

The information collected about the remote job has been reset.

The workstation has been updated in the current plan.

You have attempted to modify a workstation, but it is currently being updated by another user.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Selecting a history operation is allowed only for operations that are defined on computer workstations.

The request is valid only for step dependencies that are undefined because of missing step-end information.

A new job run occurred before a joblog retrieval request for a previous run was able to complete. The requested joblog is now obsolete. The joblog (identified by jobname JOBN and JobId JNUM) will not be stored in JS VSAM.

Data entry error; see Data entry errors.

It is not allowed to have overlapping open time intervals for the workstation.

Data entry error; see Data entry errors.

The open interval start time must be earlier than the open interval end time.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

The table result is merged from modified and planned intervals. The table is built from the modified and planned intervals according to the workstation.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

When HCL Workload Automation for Z initially checked the JCL, inconsistencies were found.

The selected stepname or proc stepname, or both, occurs more than once in the JCL.

To tailor the JCL for step restart, HCL Workload Automation for Z needs a step selection.

If the cancel was for a step restart, the JCL for this operation has not been stored in the JS repository file, because no step selection was made.

You have excluded all steps for the job, so the JCL cannot be created.

HCL Workload Automation for Z has investigated the JCL for restart and has detected inconsistencies. HCL Workload Automation for Z detects many situations that can cause problems during the step restart, for example, missing instream data or references to a temporary data set created prior to the restart step.

An occurrence that belongs to an occurrence group cannot be deleted.

An occurrence that belongs to an occurrence group cannot be completed.

The occurrence does not belong to an occurrence group.

The application does not belong to an application group.

The application is a member of an application group. This message is issued as a reminder in case you should also add the other members of the same group to the current plan.

One or more of the applications could not be added because another user is adding the same application to the current plan with the same input arrival date and time. InUse is displayed in the list to indicate the failing occurrence.

One or more of the applications could not be added because an occurrence for the same application already exists in the current plan. Exist is displayed in the list to indicate the failing occurrence.

One or more of the applications could not be added because you do not have current plan update authority for the application names. NoAuth is displayed in the list to indicate the failing occurrence.

Either there are no valid versions of any applications in the application description database for the date and time specified by the input arrival or HCL Workload Automation for Z has been unable to execute the request.

All occurrences in the group have been successfully released.

The occurrences in the group have been successfully deleted from the current plan.

One or more of the applications added to the plan could not be released. Error is displayed in the list to indicate the failing occurrence.

One or more of the applications added to the plan could not be deleted from the current plan. Error is displayed in the list to indicate the failing occurrence.

All occurrences in the group have been successfully added to the current plan. The occurrences are held until you release them.

One or more of the occurrences defined in the group could not be added to the current plan. This can happen because HCL Workload Automation for Z was unable to resolve the dependencies for the application.

The valid-from date of the group that you attempted to add to the current plan lies outside the current plan end.

You attempted to add a group of applications to the current plan, but no valid version of the corresponding group definition could be found.

One or more dependency loops has been found in the occurrence group.

The limit for the number of concurrent enqueues on a resource has been reached. This limit is defined by the GVTCREQ field in the GVT control block

Restarting this job may interfere with the JES3 dependent job control net.

The statement in the JCL has been modified by HCL Workload Automation for Z so that a replacement JCL statement could be inserted. The original statement is changed to a JCL comment.

Restarting this operation is not possible due to a previously defined COND statement.

A step-level restart has already been set for this operation and the operation has not yet been restarted.

Restarting this job is not possible due to a refer back specifying a step that is prior to a restart step. This would cause a JCL error.

The inconsistency is highlighted by placing the JCL in ISPF note line s that are then preceded with the procname and stepname where the JCL statements were found.

Restarting this job could result in unpredictable results as the IF statement refers to a step prior to a restart step. This is a JCL error.

The job is not restartable because the JCL statement that contains the OVERRIDE statement is within recursive called procedures..

The JESJCL and JESYSMSG joblog files are needed to define a step-level restart. One or both of these files are missing and HCL Workload Automation for Z cannot rebuild the JCL for step-level restart.

The JCL statement contains a DISP=MOD for a data set. This restart may corrupt the contents of this data set.

The JCL statement contains a reference to a temporary name of a data set that was created in a previous step. Restarting this job would cause a JCL error.

This step has a status of FLUSH due to a prior error. Restarting from this step may be possible. However, verification of the JCL for the status of data sets is recommended.

The JCL statement contains a condition statement that refers to a previous step. Restarting this job could cause steps to be executed that are not supposed to be executed.

HCL Workload Automation for Z attempts to delete this data set before this job is restarted.

HCL Workload Automation for Z attempts to uncatalog this data set before this job is restarted.

HCL Workload Automation for Z attempts to catalog this data set before this job is restarted.

The JCL statement contains a DCB reference to a name in a data set that has been referenced by an IEF377I message in the joblog. Restarting the job may cause problems as HCL Workload Automation for Z deletes only the cataloged data sets and not those that have just been allocated and not cataloged.

The JCL contains automatic recovery statements. The automatic recovery subtask processes those statements as soon as the cleanup actions are completed.

HCL Workload Automation for Z has investigated the JCL for restart and has found errors. Use the JCL primary to determine whether JCL updates are required.

HCL Workload Automation for Z was unable to find the absolute GDG number for the data set.

Unpredictable results may occur when the selected restart step is within an IF-THEN-ELSE clause.

The number of steps found in the job log is not consistent with the number of steps reported by the tracker when the job ended.

HCL Workload Automation for Z was unable to find the GDG base for the data set at job submit time.

You have defined one or more exclude-step row commands (X = Exclude a step from restart) and at least one of the excluded steps is either before the Start-selection or after the End-selection.

You have selected, or excluded, steps without issuing the GO command to build JCL according to the selected or excluded steps, or both.

You have attempted a step restart without selecting a restart step or an end step.

To use the row command just entered, the operation must have been selected previously for restart.

No job for this operation was found in the history database. This job was copied from the EQQJBLIB file.

The value set for the day is not valid. The allowed value is a number from 0 to 99.

No time is set for the Not Started Alert or Not Started Action field. The time is required.

The time set is not valid.

No day is set for the Not Started Alert or Not Started Action field. The day is required.

When an action is set for the deadline, a day offset is also required.

When the Not Started Action is set, a day offset is also required.

When the Not Started day and time are set, an action is also required.

The variable day offset is not valid. The allowed value is a number from 0 to 99.

The day specified for the Not Started Alert field is not valid. The allowed value is a number from 0 to 99.

The time specified for the Not Started Alert field is not valid. Allowed value is in the format HH.MM.

The day specified for the variable Not Started Alert field is not valid. Allowed value is a number from 0 to 99.

The time specified for the variable Not Started Alert field is not valid. Allowed value is in the format HH.MM.

The day specified for the Not Started Action field is not valid. Allowed value is a number from 0 to 99.

The time specified for the Not Started Action field is not valid. Allowed value is in the format HH.MM.

The day offset specified for the variable Not Started Action field is not valid. Allowed value is a number from 0 to 99.

The time specified for the variable Not Started Action field is not valid. Allowed value is in the format HH.MM.

You issued a Restart a Cleanup request like step restart, Job rerun, Start Cleanup, or Display cleanup result, but HCL Workload Automation for Z is not supporting this function because the initial parameter RCLEANUP is not set to YES.

You issued a Restart a Cleanup request like step restart, Job rerun, Start Cleanup, or Display cleanup result, but HCL Workload Automation for Z is not supporting this function because the FL task (job log fetch task) is not active.

You issued a restart and cleanup request like Step restart, Job rerun, Start Cleanup, or Display cleanup result, but HCL Workload Automation for Z is not supporting this function because the PSU task pre submit task is not active.

You issued a Restart a Cleanup request like step restart, Job rerun, Start Cleanup, or Display cleanup result but when the scheduler tried to read the OperInfo structure from the restart and cleanup data store, it was not found.

You issued a Restart a Cleanup request like step restart, Job rerun, Start Cleanup, or Display cleanup result but the scheduler has not yet completed restart and cleanup data store initialization

You issued an ARC command for an operation that has the cleanup type set to Automatic. The ARC command starts Automatic Recovery, which scans a JCL operation to process the recovery statements. However, Automatic Recovery cannot be applied the cleanup type is Automatic.

You changed the status of a ready operation that had a step restart or cleanup process pending (JCL was already tailored but not submitted). This caused the loss of the tailored JCL.

You are trying to add remote job information to an operation defined on a workstation which is not a remote engine workstation or it is defined with a type that is not consistent with the remote job information you are specifying.

You are trying to delete the remote job information related to an operation defined on a remote engine workstation.

You are trying to modify the remote job information related to an operation defined on a z/OS remote engine workstation, but the application name is not valid.

You are trying to modify the remote job information related to an operation defined on a distributed remote engine workstation, but the job stream name is not valid.

You are trying to modify the remote job information related to an operation defined on a distributed remote engine workstation, but the workstation name is not valid.

You are trying to modify the remote job information related to an operation defined on a distributed remote engine workstation, but the job name is not valid.

You are trying to modify the remote job information related to an operation defined on a remote engine workstation, but the option Complete if bind fails is set to a value that is not valid.

You are trying to modify the remote job information related to an operation defined on a z/OS remote engine workstation, but the operation number is not valid.

You are trying to add or modify an operation that was defined on a remote engine workstation, without specifying any remote job information.

You are trying to specify resources, special resources, or conditions for an operation defined on a remote engine workstation.

You are trying to specify a scheduling environment for an operation defined on a remote engine workstation.

You are trying to set to Y the deadline WTO option for an operation defined on a remote engine workstation.

You are trying to make eligible for WLM assistance an operation defined on a remote engine workstation.

You issued a Restart and Cleanup request such as: Step restart, Job rerun, Start Cleanup, or Display cleanup result. You need the last Joblog info and you just started the retrieval process.

You issued a Restart and Cleanup request like step restart, Job rerun, Start Cleanup, or Display cleanup result. You need the last Joblog info and this has already been requested but has not yet arrived.

You issued a Restart and Cleanup request like step restart, Job rerun, Start Cleanup, or Display cleanup result. You need the Oper_Info structure updated with the last Joblog info but the scheduler did not find it in the restart and cleanup data store. A possible cause for this error is the FL subtask on the controller might be down. When this subtask is down, the restart and cleanup operation is not permitted.

You issued a Job Restart for an operation for which a restart and cleanup process is in progress. Restart and cleanup status is I (Initiated) or S (Started).

You issued a Step Restart for an operation for which a restart and cleanup process is in progress. Restart and cleanup status is I (Initiated) or S (Started).

You specified an invalid cleanup status.

You specified an invalid cleanup type.

You issued a Restart and Cleanup request like step restart, Job rerun, Start Cleanup, or Display cleanup result. You need the last Joblog info and this has already been requested but the process failed and a retry is in progress.

You selected as a restart step a step marked as not restartable. This can be due to the JCL logic or the initial parameters setting (see RCLOPTS for details).

You selected as a restart step a step marked as not executable. This can be due to the JCL logic or the initial parameters setting (see RCLOPTS for details).

You selected as an end step a step marked as not executable. This can be due to the JCL logic or the initial parameters setting (see RCLOPTS for details).

You included in the restart range a step marked as not executable. This can be due to the JCL logic or the initial parameters setting (see RCLOPTS for details).

You excluded from the restart range a step marked as always executable. This is due to the initial parameters setting (see RCLOPTS for details).

You issued a Start Cleanup for an operation for which a restart and cleanup process is already in progress. Restart and cleanup status is I (Initiated) or S (Started).

You set more than one step as the restart step.

You set more than one step as the end step.

You did not include in the restart range steps that are marked as always executable. This is the due to the initial parameters setting (see RCLOPTS for details).

You issued a Step Restart for an operation for which it was not possible to retrieve information about the executed steps.

You tried to use an empty JCL in a job rerun or Step or Job restart dialog. This is not allowed.

You tried to use JCL GET from JS VSAM or JOBLIB in a Step or Job Restart dialog but it was not found. This is not allowed.

You issued a Restart and Cleanup command (like Step restart, Job Restart or start cleanup action) for an operation that has a cleanup type different to none but no action is really needed.

You issued a Start Cleanup for an operation having cleanup type set to none.

You issued a Step restart or a Job restart while you were modifying an occurrence. This is not allowed.

You issued a Job restart or a Job restart while you were modifying an occurrence. This is not allowed.

You issued a Restart and Cleanup command and this needs Operinfo structure updated with the last joblog info. HCL Workload Automation for Z checked that this update was not done and just restarted the process for update it.

You issued a display cleanup result command but a restart and cleanup process is in progress.

You issued a Restart and Cleanup command for a deleted operation. This is not allowed.

You issued a Discard request from the MODIFYING CLEANUP ACTIONS panel but did not confirm it: No data sets have been excluded from the cleanup list.

You issued a Discard request from the MODIFYING CLEANUP ACTIONS panel and confirmed it. All data sets have been excluded from the cleanup list. If you confirm the start cleanup or restart job selection, no data set is deleted.

The system waits for you to respond.

It is not possible to do cleanup actions because you do not have the CMAC Update authority for performing them.

You requested to browse the joblog of an operation. The joblog has not yet been requested and the scheduler starts the retrieval process just now on user demand.

You requested to browse the joblog of an operation. The joblog retrieval process is in progress.

Structured joblog info retrieval process has been completed and the information has been stored in Restart and Cleanup data store. At this point you can continue the restart and cleanup action selected by the dialog (Step Restart, start cleanup, Display cleanup, Job Restart).

Structured joblog information retrieval process was cancelled due to FL task closure. Re-issue the command after checking that the FL task has been restarted.

You issued the Display Cleanup command for an operation that did not require cleanup action in a previous run.

You tried to include in the cleanup actions data sets that are protected, that is, listed in the RCLOPTS statement as data sets that can not be deleted. See the Customizing and Tuning manual for details about RCLOPTS DDPROT, DSNPROT, DDPRMEM, and DSNPRMEM keywords.

You tried to start a restart and cleanup action from dialog but the last cleanup result has not been merged in the Operinfo structure and retrieval of the last cleanup result is already in progress.

While running a JR or SR command from dialog, the expanded jcl was required and it had empty sysin. JCL could be correctly restored merging the missing SYSIN DD * statement from JS JCL.

There is a Restart keyword in the jobcard of the JCL you are trying to submit. To continue, delete the keyword, because it is not compatible with the option you selected.

While running a JR or SR command from dialog, the expanded JCL was required and it had empty sysin. It has been restored merging the missing SYSIN DD* statement from the JS JCL.

A Step Restart function was invoked from dialog, with the STEPRESCHK parameter in the RCLOPTS statement set to NO. This means that a product logic check about the restarting is not performed, and the restart is performed without any warning message.

You filled the completion code field into the EQQMERSL panel with an invalid value. Numeric code must have a length of 4 chars.

You filled the completion code field into the EQQMERSL panel with an invalid value. Not numeric code can be only Unnn or FLUSH or NORUN.

You issued the STEP command from EQQMERSL panel to display the step information list (EQQMERSI) panel, but the step name table record was not found in CP.

The STEP command, provided in the EQQMERSL panel, shows the mapping among step names used in the original JCL and step names used in the Expanded JCL. This command is meaningful only if you selected Expanded JCL= Y. Since you selected Expanded JCL= N, you are prevented from using the STEP command.

The recovery info for this operation is not available. This could occur if the operation has never ended in error or if the operation has no recovery action or no recovery option defined..

In MCP, you cannot select the recovery info (RI) or kill (K) command for an operation on a non-fault-tolerant workstation.

In MCP you cannot select the recovery info (RI) when the operation is on a fault-tolerant workstation with Centralized Script specified.

In MCP you cannot select the JCL edit function when the operation is on a fault-tolerant workstation with unspecified Centralized Script.

When the Start Cleanup with AR option is selected, the cleanup actions, whose completion is waited for by the automatic recovery processing, are started manually. The Start Cleanup with AR option is meaningful only for operations whose cleanup type is Manual.

The automatic recovery function did not detect any restart steps.

The operation status is not Error or the cleanup action was already performed.

The expanded JCL field was automatically reset to a value that matches the requested function.

You tried to change the scheduling environment name of an operation in STARTED status, but this is not allowed.

The JCL was edited after the actual start of the operation and therefore it may be different from the last submitted one.

An SJR command has been issued against an operation with cleanup type set to Manual. Therefore, remember that a stand-alone cleanup has to be performed before having the operation actually re-run.

The JCL is no longer present in the JS VSAM data set (when an occurrence is completed, the scheduler flags for deletion all records for that occurrence and deletes all occurrences previously flagged as ready for deletion). The scheduler will get the JCL from the JOBLIB.

The Fast step restart (FSR) row command is being correctly processed.

The Fast job restart (FSR) row command is being correctly processed.

The jesysmsg parser ignored a message issued for a dynamically allocated GDG having the same root as a GDG referred to in the JCLl.

The scheduler restarted the OPERINFO retrieval process. OPERINFO is related to the job identified by Job Name JOBN (JID) and Job ID (JID). This job can be associated to the operation identified by Application Name APPL, Input arrival time IA and Operation number OPER or it can be the related standalone cleanup job. Standalone cleanup jobs are identified by means of a prefix specified in the RCLOPTS CLNJOBPX initial parameter.

The operation status does not allow you to update the system automation information. The operation is either started or ready to start.

The kill command for a job or recovery job running on a fault-tolerant workstation can be issued only if the job status is STARTED and the extended status is EXECUTING (for example, a job ID is available for the job).

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

The status of the condition you requested to delete is false. Conditions in false status cannot be deleted.

The processed operation is not centralized, it cannot depend on a conditional predecessor.

The scheduler detected that the requested change is inconsistent with the status of the conditional dependency network.

The scheduler detected that the requested change is inconsistent with the status of the conditional dependency network.

During the automatic successor resolution, the processing reached the maximum allowed number of conditions.

You requested to change a condition generated during the automatic resolution of conditional successors. Only the description can be changed.

You requested to change a condition generated during the automatic resolution of conditional successors. Only the description can be changed.

The Fast Start Cleanup (FSC) row command is being correctly processed.

You issued a Fast Start Cleanup (FSC) row command for an operation for which a cleanup process is already in progress. Cleanup status is either I (Initiated) or S (Started).

You issued a Fast Start Cleanup (FSC) row command for an operation having cleanup type set to "None".

A request to modify an occurrence or an operation in the current plan failed.

Data entry error; see Data entry errors.

Data entry error; see Data entry errors.

While browsing an operation in the current plan, the Step List option was selected. This option is available for z/OS jobs only.

Validation of data has failed.

An attempt to change the status of a shadow job in the current plan to a value different from Ready or Complete has been rejected, because this is not allowed. The application for which the request was attempted is identified by the application name APPL, input arrival date and time IA and operation number OPER.

An attempt to change the status of a shadow job in the current plan to a value different from Ready or Complete has been rejected, because this is not allowed.

An attempt to start a bind process for a shadow job with a status different from Ready has been rejected, because this is not allowed.

An attempt to start a bind process for a shadow job with a status different from Ready has been rejected, because this is not allowed.

An attempt to start a bind process for a shadow job has been rejected, because this is not allowed. To run the Bind command, it is required to have the appropriate authorization.