EQQMC00E - EQQM905

EQQMC00E

OPERATION APPL, IA, OPER, WOULD BECOME TOO BIG IF DEPT OPERATIONS ARE ADDED.

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.

The operation shown by the message exceeds the maximum CP record length.

To delete the occurrence that you selected, reduce the size of the operation shown by this message. For example, remove the dependency between this operation and the occurrence that you want to delete. Consider that if you try to delete a group of occurrences and this error occurs, some occurrences of the group might be deleted and others not.

EQQMC01W

USER LEVEL IS LOWER THAN CONTROLLER LEVEL: USER USER CANNOT GET AD.

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.

The request is rejected.

Ensure that you are using the required level of code.

EQQMC02E

OCCURRENCE APPL IS TOO LARGE. MCP UPDATE NOT POSSIBLE.

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.

The request is rejected.

Reduce the number of application dependencies and try again.

EQQMC03I

THE CURRENT NUMBER OF OCC NETWORK IDS IS NETNUM. IT HAS EXCEDEED PERCENT OF ITS MAXIMUM VALUE (65535).

The number of the Occurrence Network IDs in the current plan (including stand-alone occurrences and occurrences with their external dependencies) reached 80% of the maximum value allowed (65535). The value NETNUM indicates the current number of Network IDs.

Processing continues.

Reduce the number of Occurrence Networks that are currently active by performing one of the following actions:
  • Run a DP batch replan.
  • Timely check the operations that ended in error, which prevent occurrences from completing.
  • When possible, use a dependency relationship among occurrences, instead of stand-alone occurrences.
  • Make the first not completed occurrence (FNONC) as close as possible to the current plan start date.
  • Do not leave occurrences waiting in the CP for resources that will never be available or events that will not occur.
See message EQQ3168I to check the number of current Occurrence Network IDs and prevent the current plan from becoming blocked.

EQQMC09W

THE ACTUAL NUMBER OF OCCURRENCES IS OCCNUM. IT HAS EXCEEDED THE PERCENTAGE% OF THE MAXOCCNUM VALUE.

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.

None.

To prevent that the number of occurrences in the current plan reaches the value set for JTOPTS(MAXOCCNUM) and therefore no new occurrences can be added to the current plan, submit a daily planning REPLAN. In this way, the counter of the occurrences in the current plan is updated by not considering the occurrences that were completed and deleted.

EQQMH00I

THE BULK DISCOVERY HAS BEEN INTERRUPTED DUE TO PLANNING ACTIVITY: IT WILL BE RESTARTED

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

The bulk discovery is postponed. The request will be honored when planning activities complete.

None.

EQQMH01I

THE MONITORING TASK HAS ENDED

The monitoring task has ended.

None.

None.

EQQMH02E

THE MONITORING TASK HAS ENDED DUE TO PROCESSING ERRORS

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

The monitoring task is not restarted.

Check in the message log of the controller (EQQMLOG) for error messages that will help you determine the cause of the error. Correct any errors and recycle the controller. If the error persists, contact the Software Support.

A severe processing error occurred and the monitoring task cannot be restarted. Additional messages in the message log provide details on the nature of the error.

EQQMH03E

THE MONITORING TASK TERMINATED DUE TO A PROCESSING FAILURE. THE MONITORING TASK WILL BE RESTARTED

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

The system attempts to restart the monitoring task.

To collect appropriate documentation for problem determination, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, sub-section "Information to collect for monitoring problems". Search the IBM Support database for a solution at Support.

Check the message log for other error messages that will help you determine the cause of the error.

EQQMH04E

THE MONITORING TASK HAS ENDED ABNORMALLY. FOR ADDITIONAL INFORMATION SEE THE SYSLOG MESSAGES AND DUMP DATA SET

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

The monitoring task ended abnormally.

To collect appropriate documentation for problem determination, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, sub-section "Information to collect for monitoring problems". Search the IBM Support database for a solution at Support.

Check the message log (EQQMLOG), the system log, and the dump data set (EQQDUMP) for other error messages that will help you determine the cause of the error.

EQQMH05E

THE MONITOR DATASET CONTAINS INCONSISTENT DATA. ALL RECORDS WILL BE DELETED

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

All records in the specified data set are deleted.

Check in the message log of the controller (EQQMLOG) for controller error messages that will help you determine the cause of the error. Try to solve the problem and recycle the controller. To collect appropriate documentation for problem determination, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, sub-section "Information to collect for monitoring problems". Search the IBM Support database for a solution at Support.

A controller error generated inconsistent data in the data set.

EQQMH06E

BULK DISCOVERY CANNOT BE PERFORMED. REASON IS: REASON

The request to initiate a bulk discovery for an external monitor cannot be honored. The reason is one of the following:
  • An error occurred while accessing current plan
  • Cannot send events to the monitoring agent

The bulk discovery is not initiated.

If necessary, run the BULKDISC TSO command again.

A bulk discovery was not initiated due to one of the reasons indicated. If a planning activity was in progress, the bulk discovery will be initiated when the planning activity terminates.

EQQMH07I

BULK DISCOVERY IS IN PROGRESS

A bulk discovery is already running

None.

None.

EQQMH08I

BULK DISCOVERY HAS ENDED

A bulk discovery has ended.

None.

None.

EQQMH09I

CONTROLLER IS ATTEMPTING TO RE-ESTABLISH THE CONNECTION TO THE REMOTE MONITORING AGENT

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

The controller attempts to re-establish a connection to the monitoring agent.

If the re-connection attempt fails, check for any TCP/IP messages indicating the type of error in EQQMLOG.

Check for other messages in EQQMLOG and the system log that will help you determine the cause of the first connection failure.

EQQMH10W

BOTH MONOPTS AND TCPOPTS STATEMENTS ARE SPECIFIED FOR THE CONTROLLER. LOCHOSTNAME AND CONNTIMEOUT VALUES IN MONOPTS HAVE BEEN REPLACED BY HOSTNAME AND CONNTIMEOUT VALUES IN TCPOPTS.

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

HOSTNAME and CONNTIMEOUT values in the TCPOPTS statement override LOCHOSTNAME and CONNTIMEOUT values in the MONOPTS statement.

If the HOSTNAME and CONNTIMEOUT values in the TCPOPTS statement are the ones that you expect, no action is required; anyway you can remove the unneeded MONOPTS keywords. Otherwise, remove or correct the HOSTNAME and CONNTIMEOUT parameter in the TCPOPTS statement.

EQQMH11E

THE MONITOR DATASET , DDNAME DDNAME, LRECL BLKSZIS INVALID. DATASET CANNOT BE USED

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

The monitoring task terminates.

Re-allocate the referenced data set.

The data set referenced by the DDNAME must have a logical record length between 160 and 32000. Check that the LRECL is within the supported range.

EQQMH12E

THE MONITOR DATASET , DDNAME DDNAME IS TOO SMALL

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

Re-allocate a larger data set. If necessary, restart HCL Workload Automation for Z to reference the new data set.

EQQMH13E

THE MONITORING TASK WAS UNABLE TO OPEN DATASET WITH DDNAME DDNAME

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

The monitoring task terminates.

Check that the data set referenced by the DDNAME is correctly defined and recycle the controller.

EQQMH14I

CONTROLLER HAS CONNECTED TO THE REMOTE MONITORING AGENT AT ADDRESS HOSTNAME

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.

None.

None.

EQQMH15E

THE MONITORING TASK WAS UNABLE TO CLOSE DATASET WITH DDNAME DDNAME

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

None.

Correct any errors and recycle the controller.

In the EQQMLOG data set look for messages that will help you determine the cause of the error.

EQQMH16W

THE MONITOR DATA SET UTILIZATION HAS EXCEEDED THE THRESHOLD VALUE. PERCENT % OF MONITOR DATA SET IN USE.

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

The monitoring task continues processing.

Check the system log and EQQMLOG for messages indicating a network problem. If this is not the case, allocate a bigger monitoring task data set and recycle the controller.

The monitoring task data set EQQMONDS is too small or there could be a problem in the connection with the monitoring agent.

EQQMH17W

THE MONITOR DATA SET IS FULL: LOST EVENTS OVERWRITTEN

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

The monitoring task continues processing and deletes older data set records.

Check the system log and EQQMLOG for messages indicating a network problem. If this is not the case, allocate a bigger monitoring task data set and recycle the controller.

The monitoring task data set EQQMONDS is too small or there could be a problem in the connection with the monitoring agent.

EQQMH18E

TCP/IP ERROR ERRNO RECEIVED BY MONITORING TASK ON CONNECTION WITH MONITORING AGENT. ERROR MESSAGE IS TCPIPMSG

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 monitoring task attempts to recover the error. If this is not possible, the monitoring task will restart the connection.

Correct the error. If the corrections involve a change in the monitoring task parameters, recycle the controller. If the changes involve a change in the metafile configuration recycle the Universal Agent and run a TSO BULKDISC command.

The ERRNO and TCPIPMSG fields provide specific information on the type of error. For an explanation of the type of error (network configuration or TCP/IP), see the z/OS Communications Server publications. If the value of ERRNO is EPIPE, verify that the host name is correctly specified in the metafile so that it is recognized by IBM Monitoring (for details about the Tivoli Enterprise Portal Configuration options, refer to Managing the Workload). If the host name is not correctly specified, events might be lost.

EQQMH19E

CONTROLLER CANNOT CONNECT TO THE REMOTE MONITORING AGENT AT ADDRESS HOSTNAME MONITORING EVENTS WILL BE STORED LOCALLY ON MONITORING DATASET

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

All collected events are stored locally in the monitoring data set and will be sent to the remote monitoring agent when the connection is established.

Correct the error as indicated in the messages. If necessary, recycle the controller. To collect appropriate documentation for problem determination, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, sub-section "Information to collect for monitoring problems". Search the IBM Support database for a solution at Support.

This message is issued in conjunction with other messages. Check EQQMLOG for additional messages that help you determine the cause of the error.

EQQM000E

YOU DO NOT HAVE AUTHORITY TO ACCESS THE CURRENT PLAN

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

The request is rejected and the system waits for you to respond.

If you require access to the current plan, contact your security administrator.

EQQM001E

YOU DO NOT HAVE AUTHORITY TO UPDATE THE CURRENT PLAN

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

The request is rejected and the system waits for you to respond.

If you need to update the current plan, contact your security administrator.

EQQM004E

PRIORITY MUST BE A NUMBER FROM 1 - 9

Data entry error; see Data entry errors.

EQQM005E

THE MCP ADDED OPTION MUST BE Y, N, OR BLANK

Data entry error; see Data entry errors.

EQQM006E

THE RERUN OPTION MUST BE Y, N, OR BLANK

Data entry error; see Data entry errors.

EQQM007E

OPTION INVALID - THE WAITING FOR SE OPTION MUST BE Y, N, OR BLANK.

Data entry error; see Data entry errors.

EQQM008E

EXTERNAL DEPENDENCIES FORM A LOOP

You specified an external dependency that generates a loop. This must be corrected.

The dependency is rejected and the system waits for you to respond.

Check your dependencies.

EQQM009E

THE SPECIFIED APPLICATION COULD NOT BE FOUND

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.

The system waits for you to respond.

Analyze messages in the HCL Workload Automation for Z message log to determine the cause of the error. If there are no messages, contact the Software Support.

Return to the previous panel and re-create the list of applications. If the problem persists, contact your system programmer.

EQQM010I

OCCURRENCE ADDED TO THE CURRENT PLAN

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

None.

None.

EQQM011I

OCCURRENCE MODIFIED IN THE CURRENT PLAN

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

None.

None.

EQQM012I

OCCURRENCE DELETED FROM THE CURRENT PLAN

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

None.

None.

EQQM013I

THE OCCURRENCE IS SET TO RERUN

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

None.

None.

EQQM014I

THE OCCURRENCE IS SET TO WAITING

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

None.

None.

EQQM015I

AN OCCURRENCE HAS BEEN COMPLETED

You specified an occurrence that has been completed.

None.

None.

EQQM016E

THE OCCURRENCE HAS BEEN UPDATED BY AN AUTOMATIC EVENT

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.

The request is rejected.

Repeat the dialog request. The status set when the automatic event was processed is now the initial status for the dialog request.

EQQM017E

OCCURRENCE BEING UPDATED BY ANOTHER USER

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

The system waits for you to respond.

Try again later.

EQQM018E

OCCURRENCE ALREADY EXISTS - NOT ADDED

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

The occurrence is not added to the current plan and the system waits for you to respond.

Check the existing occurrence to determine whether or not the occurrence specified should be added with a new input arrival date and time.

EQQM019E

APPLICATION IS BEING UPDATED BY USER USR TRY LATER

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

The request is rejected and the system waits for you to respond.

Try again later.
Note: If another user was editing the application through the Dynamic Workload Console and closed the browser without unlocking it, the application remains locked until the session timeout expires.

EQQM020E

VALID STATUSES ARE W, S, C, E, AND U, IN ANY COMBINATION

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

The panel is redisplayed and the system waits for you to respond.

Correct the invalid values.

EQQM021I

THE OPERATION WAS RESET TO READY

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

None.

None.

EQQM022I

THE OPERATION WAS COMPLETED

You specified an operation that has been completed.

None.

None.

EQQM023E

A DELETED OCCURRENCE CANNOT BE MODIFIED

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

The request is rejected.

Select a new function.

EQQM024E

SUBSYSTEM REQUEST FAILED DUE TO I/O ERROR

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

The modify current plan function is terminated. No updates are made.

Check the HCL Workload Automation for Z message log to determine the cause of the error.

Contact your system programmer.

EQQM025E

DEPENDENT OPERATIONS HAVE BEEN CHANGED DURING SESSION. RS: XSSRS

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 request is rejected. Message EQQMxssrsE is written to the message log, where xssrs is the reason code displayed by this message.

See the message indicated by the reason code.

EQQM026E

REQUEST FAILED BECAUSE OF SUBSYSTEM ERROR

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

The modify current plan function is terminated. No updates are made.

Check the HCL Workload Automation for Z message log to determine the cause of the error.

Contact your system programmer.

EQQM027E

REQUEST FAILED BECAUSE OF SUBSYSTEM ERROR. REASON: XSSRS

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

The modify current plan function is terminated. No updates are made. Message EQQMxssrsE is written to the message log, where xssrs is the reason code displayed by this message.

See the message indicated by the reason code.

EQQM028I

DELETE OF MAAIDMAIMDMAIMT IGNORED WHILE CREATING NEW PLAN

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 request is rejected. Message EQQM937E is written to the HCL Workload Automation for Z message log.

None.

EQQM029E

REQUEST FAILED BECAUSE OF SUBSYSTEM ERROR

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

The modify current plan function is terminated. No updates are made.

Check the HCL Workload Automation for Z message log to determine the cause of the error. To collect appropriate documentation for problem determination, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, sub-section "Information needed for all problems". Search the IBM Support database for a solution at Support.

Contact your system programmer.

EQQM030E

INPUT ARRIVAL IS LATER THAN CURRENT PLAN END

Data entry error; see Data entry errors.

EQQM031I

THE OCCURRENCE HAS NO EXTERNAL DEPENDENCIES

The selected occurrence has no external dependencies.

None.

None.

EQQM032E

UNSUPPORTED STATUS CHANGE OF OSEQ OP. WITH UNCOMPLETED PREDECESSOR(S)

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.

The request is rejected. The system waits for you to respond.

The OSEQ operation can be reset to the proper status, waiting, by using the operation restart request from the ended-in-error list panel. The modify occurrence request can also be used. The operation can be deleted or the occurrence can be deleted or set to waiting. An occurrence rerun or a change of the operation status is not accepted until all predecessors have been completed or the dependencies have been deleted.

EQQM033E

CODE MUST BE ONE OF ST1E , ST1D , ST1P or ST1A

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

The system waits for you to respond.

Enter the correct code.

EQQM034E

THE JCL FOR THIS OPERATION IS BEING EDITED BY ANOTHER USER

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

The system waits for you to respond.

Try again later.

EQQM035E

ONE OF THE WS REFERENCED BY OPERATIONS IN THIS OCC. IS NOT IN CP

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.

The request is rejected.

If necessary, run a daily plan batch program to add the workstation to the current plan.

Examine the HCL Workload Automation for Z message log. Message EQQM933E identifies the workstation and operation. Contact your system programmer.

EQQM036W

INPUT ARRIVAL CANNOT BE BLANK FOR A TIME DEPENDENT OPERATION

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 system waits for you to insert an Input Arrival Date and Time.

Specify an input arrival for the operation or set it to be not time dependent.

EQQM037W

OPERATION STATUS OR OPERATION JOB ID HAS CHANGED

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.

This message is shown only once in the EQQRCLSE panel, at the first Restart and Cleanup action requested.

Check if the Restart and Cleanup action is still required, and proceed accordingly.

EQQM038W

VARY ACTIVE NOT ALLOWED. A QUERY AGENT INFO REQUEST HAS BEEN SENT TO THE AGENT.

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.

The controller tries to send a Query Agent Info request to the z-centric agent. If the request is successful, the z-centric agent workstation is automatically set to ACTIVE.

None.

EQQM039W

CURRENT PLAN MODIFIED. AFFECTED CRITICAL PATHS MUST BE RECALCULATED

Modifying the current plan has caused one of the following:
  • One or more dependencies for operations belonging to a critical path were deleted.
  • The value in the CRITICAL field for the job was changed to P, or from P to another value.
As a consequence, all the affected critical paths must be recalculated. HCL Workload Automation for Z does not update the critical path during the plan execution.

None.

Recalculate the critical paths by running a DP batch replan.

EQQM040E

ERROR CODE MUST BE GIVEN FOR ERROR STATUS OPERATION

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

The panel is redisplayed.

Correct the error.

EQQM041E

ERROR CODE MUST BE BLANK FOR OPERATION NOT IN ERROR

Error code only has meaning for an operation in error.

The panel is redisplayed.

Change the operation status or blank out the error code.

EQQM043W

THE OPERATION WAS NOT FOUND, MAY HAVE BEEN ALTERED

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

The automatic job recovery request is ignored. The system waits for you to respond.

To determine the cause of the error, check the HCL Workload Automation for Z message log for I/O error messages issued at the time that the automatic job recovery request was made.

If the error persists, contact your system programmer.

EQQM044I

WORKSTATION WSID, DEST HAS BEEN SET TO STAT STATUS

The status of the virtual workstation destination changed.

The workstation status change might affect the ongoing work.

None.

EQQM045E

SYSTEM INFORMATION IS NOT POSSIBLE FOR VIRTUAL WORKSTATION

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 request is rejected.

Enter the Select command to access a list of destinations. You can display system information for each destination.

EQQM046E

INCORRECT SELECTION FOR NON-VIRTUAL WORKSTATIONS

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

The request is rejected.

Use the S command from the MODIFYING WORKSTATIONS IN THE CURRENT PLAN panel.

EQQM047E

A PREDECESSOR CANNOT BE DEFINED AS CONDITIONAL PREDECESSOR

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

The request is rejected.

Remove the inconsistency.

EQQM048E

A CONDITIONAL PREDECESSOR CANNOT BE DEFINED AS PREDECESSOR

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

The request is rejected.

Remove the inconsistency.

EQQM049E

A CONDITIONAL DEPENDENCY CANNOT BE DELETED

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

The request is rejected.

To handle conditional dependencies enter the COND row command.

EQQM061E

NEW STATUS MUST BE ONE OF THE SUPPORTED CHARACTERS

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

The workstation status is not changed.

Correct the status character or issue the CANCEL command to cancel the status change request.

EQQM062E

THE FAIL/OFFLINE OPTIONS ENTERED ARE NOT VALID

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 workstation status does not change. No fail or offline actions are performed.

Correct the options and try again.

EQQM063E

THE ALTERNATE WS NAME IS NOT FOUND IN THE DATA BASE

The alternative workstation is not defined in the workstation database.

The workstation status does not change. Reroute is not performed to an alternative workstation.

Correct the name specified for the alternative workstation or update the workstation description database with this workstation name.

EQQM064E

ALTERNATE WS IS REQUIRED TO BE CPU/WTO TYPE WS

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

The workstation status does not change.

Correct the name specified for the alternative workstation or update the workstation description database for this workstation to specify the correct attributes.

To exit the modification without saving any changes, issue the CANCEL command.

EQQM065W

FAIL/OFFLINE OPTIONS NOT APPLICABLE FOR SETTING WS TO ACTIVE

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.

The system waits for you to respond.

Confirm the request or cancel it.

EQQM066E

THE WORK STATION STATUS INHIBITS ALTERNATE WS SPECIFICATION

An active workstation cannot have an alternative workstation.

The workstation status does not change.

Either change the workstation status to something other than A (active) or clear the alternative workstation field in the panel.

EQQM067I

WORK STATION WSID, HAS BEEN SET TO STAT STATUS

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

The workstation status is changed. This may affect ongoing work.

None.

EQQM068E

THE CURRENT WS CANNOT BE ALTERNATE TO ITSELF

The alternative workstation cannot be the current workstation.

The workstation status does not change.

Change the alternative workstation name.

EQQM069E

INVALID ALTERNATIVE

The alternate workstation must be of the same type.

The WS status does not change.

Specify an alternate workstation that is the same type as this one.

EQQM070E

YOU CAN CHANGE ONLY ONE STATUS AT A TIME

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.

The request is rejected.

Enter the correct value.

EQQM071E

A JOB DEFINITION REFERENCED BY THIS OCCURRENCE IS WRONG

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 request is rejected.

Examine the message log. Message EQQ3077E identifies the EQQSCLIB member in error.

EQQM072E

THE END-TO-END FEATURE IS NOT ACTIVE. CANNOT ADD OPERATIONS ON FTW

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 request is rejected and the system waits for you to respond.

Install and configure the end-to-end feature. Make sure that the TPLGYSRV keyword is present in the OPCOPTS statement of the controller parameters.

If you need to add an operation on a fault-tolerant workstation, contact your system programmer; otherwise remove the operation defined on the fault-tolerant workstation or change its workstation before adding the occurrence to the plan.

EQQM073I

COMMAND SENT TO CHANGE LINK OR STATUS FOR WSID

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

The status or the link of the workstation will be changed.

None.

EQQM074E

INVALID STATUS CHANGE FOR A FTW OPERATION. RS: XSSRS

Possible reasons for the error are:
  • Successor FTW operations of the operation that you attempted to modify have a status inconsistent with your modify request.
  • The operation or its recovery job has not ended yet.

The request is rejected. Message EQQMxssrsE provides additional information, where xssrs is the reason code displayed by this message. If this is a Modify Current Plan dialog request, message EQQMxssrsE is written to the message log.

Depending on whether the request is from the Modify Current Plan dialog or from the Program Interface, refer to the message indicated by the reason code.

EQQM075E

INVALID REQUEST FOR A FTW OPERATION. RS: XSSRS.

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

The request is rejected. Message EQQMxssrsE is written to the message log, where xssrs is the reason code displayed by this message.

Refer to the message indication by the reason code to establish the cause of the error.

EQQM076E

REPORTING ATTRIBUTE MUST BE A FOR REMOTE ENGINE WORKSTATIONS

Data entry error; see Data entry errors.

EQQM077E

STARTED OPERATIONS MUST BE L FOR REMOTE ENGINE AND DYNAMIC WORKSTATIONS

Data entry error; see Data entry errors.

EQQM100W

DEADLINE IS EARLIER THAN INPUT ARRIVAL TIME - VALUE ACCEPTED

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

None.

None.

EQQM101E

BOTH DATE AND TIME MUST BE SPECIFIED FOR LATE START ALERT

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

None.

Specify the required values.

EQQM102E

BOTH DATE AND TIME MUST BE SPECIFIED FOR LATE START ACTION

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

None.

Specify the required values.

EQQM103E

DEADLINE ACTION REQUIRES DEADLINE DAY AND TIME

The day and time are required for the deadline action.

None.

Specify the required values.

EQQM104E

NO APPLICATIONS MET THE SELECTION CRITERIA

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

The system waits for you to respond.

Change the selection criteria.

EQQM105E

NOT STARTED ACTION REQUIRES DAY AND TIME

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

None.

Specify the required values.

EQQM106E

DEP OPTIONS ARE: OCHCYES, OCHPRED, OCHSUCC, OCHGRP OR OCHCNO

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.

The system waits for you to respond.

Change the dependency resolution value.

EQQM107E

BOTH DATE AND TIME MUST BE SPECIFIED FOR INPUT ARRIVAL

Data entry error; see Data entry errors.

EQQM108E

BOTH DATE AND TIME MUST BE SPECIFIED FOR DEADLINE

Data entry error; see Data entry errors.

EQQM109E

APPLICATION VALID-FROM IS LATER THAN PLAN END MPLENDI

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

The request is rejected. The system waits for you to respond.

Use the Application Description dialog to change the valid-from date and time of the occurrence.

EQQM110E

OPERATIONS WITH DUPLICATE NUMBERS ARE SPECIFIED

Data entry error; see Data entry errors.

EQQM112E

THE OCCURRENCE CONTAINS UNCONNECTED OPERATIONS

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

The modification is rejected. The system waits for you to respond.

Verify and correct the dependencies.

EQQM113E

JOBNAME MOJBN MUST BE SAME IN JOB SETUP, PROCESS, AND PRINT

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

The system waits for you to respond.

Verify and correct, for example, the dependencies or the job names.

EQQM115E

A PROCESS OPERATION MUST PRECEDE A PRINT OPERATION

A print operation must be preceded by a process operation.

The system waits for you to respond.

Verify and correct, for example, the print operation or the process operation.

EQQM117E

WORK STATION MOWSN IS NOT FOUND IN THE CP, OR ACCESS WAS REVOKED

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

The system waits for you to respond.

Change the occurrence so that it uses only workstations that are in the current plan. If you are not authorized to access this workstation, contact your security administrator.

EQQM118E

A SETUP OPERATION MUST HAVE A PROCESS SUCCESSOR

A setup operation must be succeeded by a process operation.

The system waits for you to respond.

Verify and correct, for example, the setup operation or the process operation.

EQQM119E

A PREDECESSOR TO OPERATION MONUM IS ALSO A SUCCESSOR

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

The system waits for you to respond.

Verify the dependencies to the operation MONUM.

EQQM120E

ADID: ADID, IA: IA, OPNO: OPNO, CAUSES A LOOP

The specified dependencies create a loop in the operations network.

The update request is rejected.

Check your dependency specifications.

EQQM121W

THERE IS JCL ON THE JS FILE FOR OPERATION MONUM

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.

The current panel is redisplayed.

None.

EQQM122W

IAD CANNOT BE EARLIER THAN 1984/01/01

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

The request is rejected.

Define a new date starting from 1984/01/01.

EQQM123E

CONDITION DEPENDENCY SIMP IN CONDITION COND IS NOT PRESENT OR DOES NOT HAVE THE MISSING INFO FLAG SET TO YES

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 request is rejected.

Verify your selection criteria.

EQQM124E

NOT VALID STATUS SPECIFICATION FOR CONDITION DEPENDENCY SIMP IN CONDITION COND

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

The request is rejected.

Valid value are T or F. Verify the specification criteria.

EQQM125W

UNEXPECTED RC OCCURRED FOR OPERATION: ADID APPL, IA ARRTIME, OPNO OPNUM, WS WSN, JOBNAME JOBNM, JOBID JOBID, DEST DEST WHEN MODIFYING THE CURRENT PLAN.

As a result of a modify current plan action, the operation specified in the message was marked with the Unexpected RC flag because the new operation status ST does not match any of those specified in the conditions of its conditional successors. This means that no possible path for progression exists.
Note: JOBNM, JOBID and DEST could be blank depending on specified operation status and characteristics.

The operation is flagged as Unexpected RC and the status of the conditions of its conditional successors is set to Undefined.

Verify the following:
  • Make sure you correctly typed condition definitions.
  • If the operation result was expected, make sure that a successor is defined for that result.
  • If the operation result was not expected, fix the error that caused that result.
Then rerun the occurrence or manually operate appropriately to let the successors start.

EQQM126I

A JCL is displayed if this member exists in the EQQJBLIB.

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 JCL member of the JOBLIB is displayed when the member is present also in the SCRPTLIB. The script member is displayed when the member is present only in the SCRPTLIB.

None.

EQQM127E

THE OCCURRENCE CONTAINS ONLY ONE OPERATION.

The operation is the only one of the occurrence.

The operation will not be deleted.

Consider to delete the entire occurrence.

EQQM128E

FAILED TO ADD APPLICATION ADID BECAUSE MAXIMUM NUMBER OF OCC NETWORK IDS REACHED. REQUESTING FUNCTION IS FUNC.

The number of the Occurrence Network IDs (including stand-alone occurrences and occurrences with their external dependencies) reached the maximum value allowed.

The MCP activity stops, because the number of Occurrence Network IDs exceeded the maximum allowed and might generate a plan corruption.

Reduce the number of Occurrence Networks that are currently active by performing one of the following actions:
  • Run a DP batch replan.
  • Timely check the operations that ended in error, which prevent occurrences from completing.
  • When possible, use a dependency relationship among occurrences, instead of stand-alone occurrences.
  • Make the first not completed occurrence (FNONC) as close as possible to the current plan start date.
  • Do not leave occurrences waiting in the CP for resources that will never be available or events that will not occur.
See messages EQQ3168I and EQQ3169I to check the current number of Occurrence Network IDs and prevent the current plan from becoming blocked.

EQQM130W

OCCURRENCE HAS A PENDING PREDECESSOR, REQUEST IS NOT POSSIBLE

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

The request is rejected.

The function cannot be performed until the pending predecessor dependency is removed.

EQQM131E

ERROR CODE VALUE CANNOT BE CHANGED TO ERRCODE. THE STATUS OF A PREDECESSOR IS NOT C, D, OR X.

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.

The request is rejected.

The function cannot be performed until the pending predecessor dependency is removed.

EQQM140E

DEPENDENCY MUST BE O (OPERATION) OR A (APPLICATION OCCURRENCE)

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

The request is rejected.

Specify the correct value and submit the request again.

EQQM141E

COMMAND IS VALID ONLY FOR OPERATIONS. THIS IS AN OCCURRENCE.

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

The request is rejected.

Specify a valid command and submit the request again.

EQQM150E

INPUT ARRIVAL IS LATER THAN CURRENT PLAN END CPEDCPET

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.

If this is a request to the program interface, the request is rejected and control is returned with the return code set to error.

Correct the input arrival time and resubmit the job.

EQQM151E

CURRENT PLAN READ ERROR, AD NOT ADDED TO CURRENT PLAN

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

If this is a request to the program interface, the request is rejected and control is returned with the return code set to error.

Review the message log of the HCL Workload Automation for Z subsystem to determine the cause of the error. This message is generally preceded by a more specific I/O error message. Check the HCL Workload Automation for Z message log to determine the cause of the error. To collect appropriate documentation for problem determination, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, sub-section "Information needed for all problems". Search the IBM Support database for a solution at Support.

Resubmit the job when the problem causing the I/O error has been corrected.

The message log of the HCL Workload Automation for Z subsystem contains the I/O error message.

EQQM152E

ALL OCCURRENCES OF AD BEFORE CP END CPED CPET EXIST

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.

If this is a request to the program interface, the request is rejected and control is returned with the return code set to error.

If necessary, resubmit the job after either extending the current plan or deleting some existing occurrence.

The default input arrival time is the current time, consisting of the current date, current hour, and current minute. If an occurrence of the application with that input arrival time already exists, the next minute is used. If that occurrence also exists, the following minute is used. This search for an input arrival time continues up to the current plan end time.

EQQM153E

IA NOT BEFORE CP END CPEDCPET, AD NOT ADDED

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.

If this is a request to the program interface, the request is rejected and control is returned with the return code set to error.

If necessary, resubmit the job after extending the current plan.

EQQM154E

ALL POTENTIAL EXTERNAL SUCCESSORS COULD NOT BE RESOLVED

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.

The current occurrence is not added to the current plan.

If necessary, change the Resolve Required option to N (no) and retry the request to add the occurrence to the current plan.

EQQM155E

OCCURRENCE WITH SAME ADID AND IA EXISTS IN LONG-TERM PLAN

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.

If this is a Modify Current Plan dialog request, the request is rejected. If it is a request to the program interface, the request is rejected and control is returned with the return code set to error.

Change the input arrival date or time and resubmit the request.

EQQM157E

FTA AND REMOTE ENGINE CANNOT HAVE APPLICATION PREDECESSORS.

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.

The action is ignored.

This kind of dependency cannot be added. Ensure that the affected occurrence does not have first operations (operations without internal predecessors) that run on fault-tolerant or remote engine workstations.

EQQM161E

MODIFY CP REQUEST FAILED, INSUFFICIENT STORAGE. REASON: RS

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.

If this is a request to the program interface, the request is rejected and control is returned with the return code set to error.

Allocate a larger region to the HCL Workload Automation for Z subsystem and restart the subsystem. If the error persists, contact the Software Support.

If necessary, resubmit the job after the HCL Workload Automation for Z subsystem has been restarted in a larger region.

EQQM162W

OPERATION MONUM DEFINES TOO MANY RESOURCES, FIRST MAXRES USED

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 dialog uses the maximum resources defined by the application description to initialize special resources for this operation.

Enter the OPER primary command to display operations for this occurrence. Select the operation defined by this message and review the current definition of special resources for the operation. If required, modify the currently defined resources, but note that no additional resources can be added for this operation.

EQQM163W

TWO OR MORE OPERATIONS DEFINE TOO MANY RESOURCES, FIRST MAXRES USED

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 dialog uses the maximum resources defined by the application description for each operation that have too many special resources.

Enter the OPER primary command to display operations for this occurrence. Review the current definition of special resources for this occurrence. If required, modify the currently defined resources, but note that the number of resources that can be defined per operation is limited by the maximum record length of 32,768 bytes.

EQQM164E

AN OPERATION RECORD IS TOO LARGE TO BE SAVED IN CURRENT PLAN

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

The occurrence has not been saved. The dialog waits for you to continue updating the current occurrence.

Enter the OPER primary command to display operations for this occurrence. Review the current definition of the operations. Try to reduce the number of special resources or dependencies, or both, defined for the most complex operations. After making corrections, retry the Current Plan update request.

EQQM165E

SYSTEM AUTO WS REQUIRED

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

The action cannot be continued and the modification cannot be saved, until the workstation is appropriately defined.

Ensure that the workstation has the Automation option set to Yes. If you changed the workstation from Automation to not-Automation, change it back or use a workstation that is Automation. If you no longer need the System Automation operation, you cannot change it to be a not-automation one; you must delete it and create a new one. If you cannot delete the operation for any reason, you can leave a System Automation workstation and define a dummy System Automation command for it in the command text.

EQQM166E

NO SYSTEM AUTO DATA

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

The action cannot be continued and the modification cannot be saved, until the workstation or operation is appropriately defined.

Check that the workstation used has the Automation option set to N. If you changed the workstation from non-Automation to Automation, change it back or use a non-Automation workstation. If you need this operation to be a System Automation operation, specify the command text and security element.

EQQM167E

AUTHORIZATION FAILED

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.

The requested system automation information is not retrieved.

Verify that you are trying to access the information for which you are granted access. If so, ask for the appropriate security authorization related to the specific SECELEM of the data.

EQQM169E

FAILED TO ADD. MAXIMUM NUMBER OF OCC NETWORK IDS REACHED.

The number of the Occurrence Network IDs (including stand-alone occurrences and occurrences with their external dependencies) reached the maximum value allowed.

The MCP activity stops, because the current number of Occurrence Network IDs might generate a plan corruption.

Reduce the number of Occurrence Networks that are currently active by performing one of the following actions:
  • Run a DP batch replan.
  • Timely check the operations that ended in error, which prevent occurrences from completing.
  • When possible, use a dependency relationship among occurrences, instead of stand-alone occurrences.
  • Make the first not completed occurrence (FNONC) as close as possible to the current plan start date.
  • Do not leave occurrences waiting in the CP for resources that will never be available or events that will not occur.
See also messages EQQ3168I and EQQ3169I to check the current number of Occurrence Network IDs and prevent the current plan from becoming blocked.

EQQM171E

MAXIMUM NUMBER OF OCCURRENCES OF AD EXISTS

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

The create request is rejected.

If possible, delete occurrences of this application that have finished processing. These occurrences are removed from the plan next time, producing a new plan. If necessary, copy the application description and add the occurrence with a new name.

EQQM172E

MAXIMUM NUMBER OF OCCURRENCES EXISTS, FAILED TO ADD AD

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 request is rejected.

Check that the current plan does not contain any occurrences that should not be in the plan. If you find any such occurrences, complete or delete them. Replan the current plan to remove all completed and deleted occurrences and try to add the occurrence again. If your current plan regularly contains a large number of occurrences, you should consider shortening the length of the current plan in future daily planning runs.

If you use event-triggered tracking (ETT), program interface (PIF), or Automatic Recovery, check that these functions are working correctly. For example, make sure that you do not have an endless ETT loop where the availability of a special resource is set to YES by a job that ETT adds when it detects that this same resource is set to YES. Check the current plan for instances of an unusually high number of occurrences of a particular application. If you see such an application, look in the application description database and make sure that the run cycles for the application are correct. When you specify PREVRES(YES) on the BATCHOPT initialization statement, information about completed and deleted occurrences is carried forward, for reporting purposes, into a new current plan. If your current plan regularly contains a large number of occurrences, and you specify YES for PREVRES, you should consider changing this value to NO.

EQQM173W

CHANGING INPUT ARRIVAL MAY CAUSE EDITED JCL TO BE LOST

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.

The system waits for you to respond

To keep the edited JCL, change the input arrival back to the original value and press ENTER. If you need the input arrival to change acknowledge this by pressing ENTER. This may cause the JCL that you edited to be lost.

EQQM174E

INCORRECT CONDITION DEPENDENCY SPECIFIED ON OPERATION APPL IA OPER CONDITION COND: SIMP. STEP LEVEL DEPENDENCIES REQUIRE CONDITION TYPE RC.

You specified a condition type different from RC.

The request is rejected.

Specify RC as condition type.

EQQM175E

INCORRECT CONDITION DEPENDENCY SPECIFIED ON OPERATION APPL IA OPER CONDITION COND: SIMP. STEP NAME SPECIFICATION REQUIRES PROC STEP SPECIFICATION TOO.

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

The request is rejected.

If the step is in a procedure specify both the parameters, otherwise specify only the name of the step that corresponds to the EXEC PGM= statement.

EQQM176E

INCORRECT CONDITION DEPENDENCY SPECIFIED ON OPERATION APPL IA OPER CONDITION COND: SIMP. FIRST CHARACTER INCORRECT FOR STEP NAME.

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

The request is rejected.

Specify an alphabetic or national character as initial character in the procedure invocation step name.

EQQM177E

INCORRECT CONDITION DEPENDENCY SPECIFIED ON OPERATION APPL IA OPER CONDITION COND: SIMP. FIRST CHARACTER INCORRECT FOR PROC STEP.

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

The request is rejected.

Specify an alphabetic or national character as initial character in the step name.

EQQM178E

INCORRECT CONDITION DEPENDENCY SPECIFIED ON OPERATION APPL IA OPER CONDITION COND: SIMP. WRONG STRING SPECIFICATION FOR STEP NAME.

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 request is rejected.

Correct the string.

EQQM179E

INCORRECT CONDITION DEPENDENCY SPECIFIED ON OPERATION APPL IA OPER CONDITION COND: SIMP. WRONG STRING SPECIFICATION FOR PROC STEP.

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.

The request is rejected.

Correct the string.

EQQM200E

THE SPECIFIED WORK STATION ID DOES NOT EXIST

Data entry error; see Data entry errors.

EQQM201E

THE OPERATION NUMBER MUST BE BETWEEN 1 - 255

Data entry error; see Data entry errors.

EQQM202E

THE JOBNAME MUST BE IN THE FORMAT CAAAAAAA

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.

EQQM203E

JOB SETUP, COMPUTER, AND PRINT OPERATIONS REQUIRE A JOBNAME

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

The panel is redisplayed.

Specify a jobname for the operation.

EQQM205E

NUMBER OF SERVERS MUST BE BETWEEN 1 - 99

Data entry error; see Data entry errors.

EQQM206E

NUMBER OF WORK STATION RESOURCES MUST BE BETWEEN 0 - 99

Data entry error; see Data entry errors.

EQQM207E

THE NEW STATUS MUST BE R, S, C, E or I

R
Ready
S
Started
C
Completed
E
Error
I
Interrupt
Data entry error; see Data entry errors.

EQQM208E

THE STATUS CANNOT BE CHANGED - EXT/CONDITIONAL SUCCESSOR S,C,X OR E

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

HCL Workload Automation for Z does not change the status and ignores the request.

When dependencies are involved, the status must be changed within the rerun occurrence path. Use option R in panel 5.2, or option RER in panel 5.4.

EQQM209E

THE VARIABLE TABLE IS NOT DEFINED

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.

EQQM210E

RESOURCES WITH DUPLICATE NAMES WERE FOUND

Data entry error; see Data entry errors.

EQQM211E

A RESOURCE NAME MUST BE SPECIFIED

Data entry error; see Data entry errors.

EQQM212E

RESOURCE OPTION MUST BE S-SHARE OR X-EXCLUSIVE

Data entry error; see Data entry errors.

EQQM213E

OPTION FOR AUTOMATIC TRACKING MUST BE Y OR N

Data entry error; see Data entry errors.

EQQM214E

OPTION FOR AUTOMATIC SUBMIT MUST BE Y OR N

Data entry error; see Data entry errors.

EQQM215E

OPTION FOR HOLD/RELEASE MUST BE Y OR N

Data entry error; see Data entry errors.

EQQM216E

OPTION FOR TIME DEPENDENCY MUST BE Y OR N

Data entry error; see Data entry errors.

EQQM217E

OPTION FOR SUPPRESS IF LATE MUST BE Y OR N

Data entry error; see Data entry errors.

EQQM218E

CANNOT CHANGE STATUS: EXT PRED NOT COMPLETE OR COND NOT TRUE

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.

HCL Workload Automation for Z does not change the status and ignores the request.

When dependencies are involved, the status change must be done within the rerun occurrence path.

EQQM219E

OPERATION NUMBER MUST NOT BE CHANGED FROM MOONU

Data entry error; see Data entry errors.

EQQM220E

DEPENDENCY TYPE MUST BE P-PREDECESSOR OR S-SUCCESSOR

Data entry error; see Data entry errors.

EQQM221E

NO OPERATIONS IN CURRENT PLAN MATCH THE SEARCH ARGUMENT

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

The system waits for you to respond.

Check your selection criteria.

EQQM222W

UNRESOLVED EXTERNAL PREDECESSORS EXIST

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 Modify Current Plan dialog waits for input.

If the message is issued on the EQQMAOCP panel, enter the DEP primary command to modify automatically added dependencies. If the message is issued on the EQQMARXL panel, delete all unresolved predecessor dependencies.

EQQM223W

OPERATION DEADLINE PRECEDES OPERATION INPUT ARRIVAL - ACCEPTED

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

None.

None.

EQQM224W

OPERATION INPUT ARRIVAL PRECEDES OCCURRENCE - ACCEPTED

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

None.

None.

EQQM225W

OPERATION DEADLINE LATER THAN OCCURRENCE DEADLINE - ACCEPTED

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

None.

None.

EQQM227W

A SUCCESSOR DEPENDENCY COULD NOT BE ADDED

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

If this message is issued when the DEP command has been entered, unresolved successors are indicated by a missing (blank) input arrival time. If this message is issued when trying to add an occurrence to the plan and the RESOLVE REQUIRED indicator is Y, the occurrence is not added.

If the occurrence should be added to the plan without the successor dependency, change the RESOLVE REQUIRED indicator to N and retry the add occurrence function.

EQQM228E

A DEPENDENCY TO THE OPERATION IS ALREADY DEFINED

Data entry error; see Data entry errors.

EQQM229E

JCL BROWSE/EDIT CAN ONLY BE SELECTED FOR PROCESSOR WORK STATIONS

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

EQQM230E

HIGHEST RETURN CODE IS NOT NUMERIC

Data entry error; see Data entry errors.

EQQM231E

SPECIFIED OPERATION IS ALREADY A PREDECESSOR

Data entry error; see Data entry errors.

EQQM232E

SPECIFIED OPERATION IS ALREADY A SUCCESSOR

Data entry error; see Data entry errors.

EQQM233I

THE SPECIFIED OPERATION HAS BEEN ADDED AS A PREDECESSOR

The specified operation has been added as a predecessor.

None.

None.

EQQM234I

THE SPECIFIED OPERATION HAS BEEN ADDED AS A SUCCESSOR

The specified operation has been added as successor.

None.

None.

EQQM235E

THE SPECIFIED OPTION MUST BE EITHER Y, N, OR BLANK

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.

EQQM236E

VARIABLE TABLE NAME CONTAINS AN INVALID CHARACTER

Data entry error; see Data entry errors.

EQQM237E

OPTION FOR DEADLINE WTO MUST BE Y OR N

Data entry error; see Data entry errors.

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

EQQM238E

YOU ARE NOT AUTHORIZED TO READ THE JCL VARIABLE TABLE DATA BASE

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

The system waits for you to respond.

Contact your security administrator if you need to refer to JCL variable table names.

EQQM239E

MULTIPLE RESTART POINTS ARE NOT ALLOWED, DUE TO EXTERNAL DEPENDENCIES

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 first restart point that you selected is accepted. All other restart points are cancelled.

If you want to rerun the application occurrence starting from the first restart point, enter Y on the Rerun Confirmation panel. Otherwise, enter N.

EQQM240E

RESTART OPERATION HAS PENDING OR MANDATORY PENDING PREDECESSORS

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.

The occurrence status is not changed to rerun, but updates made to the JCL are saved.

Select another restart point in the application occurrence, or delete the pending dependencies. Run the occurrence again.

EQQM241I

THE OCCURRENCE STATUS HAS NOT BEEN CHANGED

The occurrence status has not set to rerun because:
  1. The operation that you selected as a restart point has at least one predecessor that is pending (not in the current plan). The status cannot be set to rerun until you delete the pending dependencies.
  2. You entered the cancel command on the EQQMOSTL panel.

The occurrence status is not changed to rerun, but updates made to the JCL are saved.

None.

EQQM242E

THE NUMBER OF PARALLEL SERVERS MUST BE 1 FOR CPU OPERATIONS

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

The panel is redisplayed and the dialog waits for you to change the number of parallel servers.

Change the number of parallel servers to 1.

EQQM245W

THE CLEANUP ACTION HAS STARTED FOR THIS OPERATION

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 automatic recovery request is ignored.

Try again later.

If the data store has been stopped, stop and start the FL task to restart the auto recovery action.

EQQM246E

DEPENDENT OCC NOT FOUND

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

Add new predecessor/successor occurrences to the current plan.

EQQM247E

OPTION FOR EXTERNAL MONITOR MUST BE Y OR N

Data entry error. See Data entry errors.

EQQM248E

OPTION FOR CENTRALIZED SCRIPT MUST BE Y OR N

Data entry error. See Data entry errors

EQQM249E

OPTION FOR IGNORED AT REMOVAL MUST BE Y OR N

Data entry error. See Data entry errors

EQQM250E

CURRENT OPERATION STATUS MUST BE A, *, R, W, C, X, OR E TO BE HELD

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 request is ignored.

None.

EQQM251I

OPERATION IS ALREADY MANUALLY HELD BY DIALOG

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

The request is ignored.

None.

EQQM252I

OPERATION IS NOT MANUALLY HELD BY DIALOG

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 request is ignored.

None.

EQQM253I

OPERATION IS PUT IN MANUAL HOLD

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

The operation is manually HELD.

None.

EQQM254I

OPERATION HAS BEEN MANUALLY RELEASED FROM MANUAL HOLD

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

The operation is released, and may be scheduled byTivoli OPC.

None.

EQQM255E

CURRENT OPERATION STATUS MUST BE A, *, W, C, X, OR R TO BE NOPED

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 request is ignored.

None.

EQQM256I

OPERATION IS ALREADY NOPED BY USER REQUEST

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

The request is ignored.

None.

EQQM257I

OPERATION IS NOT NOPED

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 request is ignored.

None.

EQQM258I

OPERATION HAS BEEN NOPED

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.

The operation is indicated as no-oped.

None.

EQQM259I

OPERATION NOP HAS BEEN RESET

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

The operation's NOP indication is removed.

None.

EQQM260I

OPERATION HAS BEEN EXECUTE INDICATED

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

Processing continues.

None.

EQQM261E

CURRENT OPERATION STATUS MUST BE A, *, OR R TO BE EXECUTED

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

The request is ignored.

EQQM262E

YOU DO NOT HAVE AUTHORITY TO USE THE EXECUTE COMMAND

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

The request is rejected and the system waits for you to respond.

Contact your security administrator if you need to use the EXECUTE command.

EQQM263E

COMMAND VALID ONLY ON COMPUTER AUTOMATIC, SYSTEM AUTO WS, AND WTO WS.

The workstation on which the command was issued is not a valid type of computer.

The request is ignored.

Ensure that you issue the command only on the following types of computers:
  • Workstation with the automatic reporting attribute
  • System Automation workstation
  • WTO general workstation

EQQM264E

THE COMMAND THAT WAS ISSUED IS NOT SUPPORTED

The command is not supported by Tivoli OPC.

The request is ignored.

Issue only valid Tivoli OPC commands.

EQQM265E

COMMAND SUPPORTED ON AUTOMATIC CPU OR NONREPORTING WORKSTATIONS

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

The request is ignored.

Issue the command only on supported workstations.

EQQM266E

THERE IS NO ACTIVE WORKSTATION FOR THIS OPERATION

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

The request is ignored.

Issue the EXECUTE command when the workstation, or an alternative workstation, becomes active again.

EQQM267E

STATUS CANNOT BE CHANGED AS THE OPERATION HAS BEEN MANUALLY HELD

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

The request is ignored.

Either set a specific status using the N–x row command, or manually release the operation (MR) and reissue the N row command.

EQQM268E

PROMPT CANNOT BE REPLIED FOR THIS OPERATION

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.

The request is rejected.

Verify that the operation has the prompt and that the prompt is in the required status.

EQQM269E

THE STATUS CANNOT BE CHANGED FROM OR TO X

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.

The request is rejected.

Consider rerunning the occurrence.

EQQM270E

THIS IS NOT AN FTW, IT CANNOT BE CHANGED TO AN FTW ONE

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

Request is rejected.

Enter the correct value.

EQQM271E

CANNOT CHANGE THE FIELD FLD IF OPERATION RUNS ON FTW.

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

Request is rejected.

Enter the correct value.

EQQM272E

OP. NUMBER OP ALREADY USED BY A DELETED OPERATION ON FTW

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

Request is rejected.

Insert an operation with another operation number.

EQQM273E

OP. NUMBER OP ALREADY USED BY A DELETED OPERATION ON NON-FTW

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

Request is rejected.

Enter the correct value.

EQQM274E

THE ALTERNATE WORKSTATION CANNOT BE A FAULT-TOLERANT WORKSTATION

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

Request is rejected.

Enter the correct value.

EQQM275E

THE NEW STATUS CANNOT BE I IF THE OPERATION IS ON FTW

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

The request is rejected.

Enter the correct value.

EQQM276E

THE STATUS CANNOT BE SET TO READY IF THE FTW OPERATION IS NOT ENDED.

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.

The request is rejected.

Enter the correct value.

EQQM277E

INVALID STATUS CHANGE TO WAITING REQUESTED FOR A FTW SUCCESSOR

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.

The request is rejected.

Enter the correct value.

EQQM278E

INVALID VALUE FOR FIELD FLD IF OPERATION RUNS ON A FTW.

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

The request is rejected.

Enter the correct value, for example:

AEC = Y

AJR = Y

CRT = N

HRC = blank or 0

SUB = Y

WTO = N

EQQM279E

FTW OPERATION: THE STATUS CAN BE R (FOR NON-RUNNING OPERATION) OR C

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.

Request is rejected.

Enter the correct value.

EQQM280I

EXTENDED INFO USED AS KEY IN SYMPHONY. ENTER AGAIN TO BROWSE IT

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.

Informs that it is possible to show the Browse panel.

Re-enter the request to display the Browse panel.

EQQM281I

CANNOT CHANGE EXTENDED NAME IF TWSJOBNAME VALUE IS EXTNAME/EXTNOCC

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.

The request is rejected.

Cancel the request.

EQQM282E

CANNOT CHANGE EXTENDED NAME OR JOBNAME IF IT IS A SYMPHONY KEYWORD

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.

The request is rejected.

Enter the correct value.

EQQM283E

SELECTION NOT VALID

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

EQQM284W

THIS CONDITION IS EVALUATED AND CANNOT BE MODIFIED

You can modify a condition while its status is undefined.

The request is rejected.

Specify a valid selection.

EQQM285E

A PREDECESSOR TO OPERATION OPNO IS ALSO A SUCCESSOR

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

The request is rejected.

Verify the dependencies to the operation OPNO.

EQQM286E

CONDITION CID IN OPERATION OPNO IS NOT VALID

Data entry error; see Data entry errors.

EQQM287E

DEPENDENCY LOOP DETECTED IN OCCURRENCE NETWORK

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

The request is rejected.

Check the message log for any message identifying the occurrences and the affected operations.

EQQM288E

SELECTION TYPE MUST BE S

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

The request is rejected.

Use S to select an operation.

EQQM289I

INTERNAL CONDITIONAL PREDECESSOR PRED NOT ADDED TO OPERATION APPL, OPER IN CONDITION COND DURING AUTOMATIC CONDITIONAL SUCCESSORS RESOLUTION AT OCCURRENCE ADD

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

The dependency resolution process skips the indicated condition dependency.

Consider checking your dependency definition to remove inconsistencies.

EQQM290E

CURRENT OPERATION IS NOT EXECUTED. BIND PROCESS WAS STARTED.

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

The EX command is not performed.

None.

EQQM291I

BIND INFORMATION HAS BEEN RESET.

The information collected about the remote job has been reset.

Processing continues.

None.

EQQM301I

WORK STATION UPDATED IN CURRENT PLAN

The workstation has been updated in the current plan.

The modify workstation function is terminated.

If you added or modified an open interval, ensure that the begin time was the same or later than the current time, otherwise the update is not made.

EQQM302W

A WORK STATION IS CURRENTLY BEING UPDATED, TRY LATER

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

The system waits for you to respond.

Try again later.

EQQM303E

THE REPORTING ATTRIBUTE SPECIFIED MUST BE A, S, C, OR N

Data entry error; see Data entry errors.

EQQM304E

CONTROL ON SERVERS OR RESOURCES MUST BE Y-YES OR N-NO

Data entry error; see Data entry errors.

EQQM305E

COMMAND VALID ONLY ON COMPUTER WORKSTATIONS

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

EQQM306E

CONDITION DEPENDENCY MUST BE UNDEFINED WITH MI SET TO Y

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

EQQM309I

RETRIEVED JOBLOG (JOBN JNUM) NOT STORED: NEW RUN OCCURRED

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.

The joblog is not stored in JS VSAM.

None.

EQQM310E

OPEN TIME INTERVALS MUST NOT OVERLAP

Data entry error; see Data entry errors.

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

EQQM311E

INTERVAL START MUST PRECEDE END

Data entry error; see Data entry errors.

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

EQQM312E

START TIME MUST BE SPECIFIED FOR AN INTERVAL

Data entry error; see Data entry errors.

EQQM313E

END TIME MUST BE SPECIFIED FOR AN INTERVAL

Data entry error; see Data entry errors.

EQQM314E

VALUE FOR PARALLEL SERVERS MUST BE 0 - 99

Data entry error; see Data entry errors.

EQQM315I

TABLE RESULT IS MERGED FROM MODIFIED AND PLANNED INTERVALS

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

Processing continues.

If you want the displayed table to be used, use the END command. Press ENTER to display the table without this message.

EQQM317E

VALUE FOR PARALLEL SERVERS MUST BE 0 - 65535

Data entry error; see Data entry errors.

EQQM328E

A VALID RESPONSE IS EITHER Y OR N

Data entry error; see Data entry errors.

EQQM333W

THE SCHEDULER INITIALLY FOUND INCONSISTENCIES IN THE JCL

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

The system waits for you to respond

Enter Yes to accept the step-level restart selected or enter No to reject the restart setting.

EQQM334I

MORE THAN ONE STEP WITH SAME PROCSTEP/STEPNAME

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

HCL Workload Automation for Z chooses the first occurrence of the selected step name and uses it as the restart step.

None.

EQQM335E

THE SCHEDULER CAN NOT TAILOR ANY JCL BECAUSE NO RESTART STEP WAS SELECTED

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

The system waits for you to respond.

Select a step or cancel the step restart.

EQQM336I

THE RESTART HAS BEEN CANCELLED FOR THIS OPERATION

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.

None.

None.

EQQM337E

NO STEPS WERE SELECTED FOR RESTART

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

The system waits for you to respond.

Make sure that a minimum of one step is selected for the job and reissue the GO command.

EQQM339W

THE OPERATION CANNOT BE RESTARTED WITHOUT CHANGING THE JCL

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.

The JCL i s displayed. ISPF message lines are inserted by HCL Workload Automation for Z to document the detected inconsistencies.

Change the JCL, or cancel the restart for this operation, or save the JCL after determining that the reported inconsistencies are not expected to result in a problem during restart.

EQQM340E

OCCURRENCE IN A GROUP MUST BE REMOVED BEFORE IT CAN BE DELETED

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

The system waits for you to respond.

You must remove the occurrence before you can delete it. To do this, type the row command RG on the MODIFYING OCCURRENCES IN THE CURRENT PLAN pa nel or the HANDLING OPERATIONS ENDED IN ERROR panel. Alternatively, erase the group definition ID field on the MODIFYING AN OCCURRENCE IN THE CURRENT PLAN panel.

EQQM341E

OCCURRENCE IN A GROUP MUST BE REMOVED BEFORE IT CAN BE COMPLETED

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

The system waits for you to respond.

You must remove the occurrence before you can complete it. To do this, type the row command RG on the MODIFYING OCCURRENCES IN THE CURRENT PLAN panel or the HANDLING OPERATIONS ENDED IN ERROR panel. Alternatively, erase the group definition ID field on the MODIFYING AN OCCURRENCE IN THE CURRENT PLAN panel.

This message can also be issued when you try to complete the last uncompleted operation of an occurrence belonging to a group. It is issued because the completion of an operation would imply the completion of the occurrence. However, HCL Workload Automation for Z does not allow manual completion of this kind of occurrence before the occurrence has been removed from the group.

EQQM342E

OCCURRENCE IS NOT A MEMBER OF AN OCCURRENCE GROUP

The occurrence does not belong to an occurrence group.

The request is rejected.

Check the occurrence definition and correct it.

EQQM343E

APPLICATION IS NOT A MEMBER OF AN APPLICATION GROUP

The application does not belong to an application group.

The request is rejected.

Check the application definition and correct it.

EQQM344W

APPLICATION IS A MEMBER OF A GROUP. CONSIDER ADDING THE OTHER MEMBERS

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.

Normal processing continues.

If applicable, create occurrences in the current plan for the other applications in the same group.

EQQM345E

ONE OR MORE OCCURRENCES ARE IN USE

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.

The system waits for you to respond.

Check that Group ID and Input arrival date and time have been specified correctly. Or, check with the other user who is creating the same occurrence to determine which of the occurrences should be added. Alternatively, use the row command D to delete the occurrence from the list.

EQQM346E

ONE OR MORE OCCURRENCES ALREADY EXISTS

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.

The system waits for you to respond.

Check that Group ID and Input arrival date and time have been specified correctly. Use the row command D to delete the occurrence from the list. Alternatively, use the Modify Current Plan dialog to delete the previously added occurrence from the current plan.

EQQM347E

INSUFFICIENT AUTHORITY TO ADD ONE OR MORE APPLICATIONS

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.

The system waits for you to respond.

Verify that Group ID has been specified correctly. Alternatively, use the row command to delete the occurrence from the list.

EQQM349E

NO OCCURRENCES TO ADD, OR TERMINATING ERRORS FOUND

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.

The system waits for you to respond.

Check that Group ID and Input arrival date and time have been specified correctly.

EQQM350I

ALL ADDED OCCURRENCES HAS BEEN SUCCESSFULLY RELEASED

All occurrences in the group have been successfully released.

The occurrences have been released.

None.

EQQM351I

ALL ADDED OCCURRENCES HAS BEEN SUCCESSFULLY DELETED

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

The occurrences have been deleted from the current plan.

None.

EQQM352E

SOME ADDED OCCURRENCES COULD NOT BE RELEASED

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.

The system waits for you to respond.

See the message log for possible error information. Use the row command D to delete the occurrence from the list.

EQQM353E

SOME ADDED OCCURRENCES COULD NOT BE DELETED

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.

The system waits for you to respond.

See the message log for possible error information. Use the row command D to delete the occurrence from the list.

EQQM354I

ALL SELECTED OCCURRENCES HAS BEEN SUCCESSFULLY ADDED

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

Processing continues.

Modify the individual occurrences as required and release the group.

EQQM355E

SOME SELECTED OCCURRENCES COULD NOT BE ADDED

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 occurrence group is added to the current plan, but not all of the occurrences were added.

Add the individual occurrences to the plan as members of the existing group. Alternatively, delete the entire occurrence group before the occurrences are released.

The message log contains messages that describe the reason why the individual occurrences could not be added.

EQQM356E

GROUP VALID-FROM DATE IS LATER THAN PLAN END MPLENDI

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

The request is rejected.

Use the Application Description dialog to change the valid-from date of the group definition.

EQQM357E

NO VALID GROUP DEFINITION AVAILABLE

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

Possible reasons for this error are:
  • The group definition has been deleted from the application description database
  • You do not have security access to read the group definition
  • An active group definition is not in effect for the specified input arrival date.

The system waits for you to respond.

Check why the group definition could not be found, correct the error and resubmit the request.

EQQM358W

DEP LOOP DETECTED, NOT ALL DEPS RESOLVED WITHIN THE GROUP

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

In each loop, the external dependencies for one of the operations has not fully been resolved within the group. If there are other occurrences, external to the group, in the current plan that matches these dependency definitions, the dependencies have been resolved to those occurrences. Message EQQM976W is written to the message log, once for each loop detected.

Check the message log to identify the occurrences and the affected operations.

EQQM359E

LIMIT FOR THE NUMBER OF CONCURRENT ENQUEUES REACHED

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

The request is rejected.

Increase the z/OS value of the GVTCREQ field.

EQQM360W

WHEN THE SCHEDULER CHECKED THE JCL IT FOUND JES3 DJC STATEMENTS

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

None.

Verify that the restart does not affect the DJC net or change the JCL accordingly, or both.

EQQM361I

STATEMENT OVERRIDDEN DUE TO CONFLICT WITH ORIGINAL JCL

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.

Processing continues.

Verify that the step restart selected is correct.

EQQM362E

THE SCHEDULER DIDN'T INSERT COND AS ONE IS ALREADY PRESENT

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

None.

Verify that the existing COND statements are valid and amend the JCL accordingly.

EQQM364W

A STEP LEVEL RESTART HAS ALREADY BEEN SELECTED FOR THE OPERATION

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

Processing continues.

Verify the step-level restart that was previously selected. Change it if necessary.

EQQM365E

THE STATEMENT CONTAINS REFER BACK TO STEP PRIOR TO RESTART

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.

None.

Verify that the step from which to restart is correct and amend the JCL accordingly.

EQQM366I

STATEMENT FOLLOWS FROM STEP STEPNAME PROC STEP PROCNAME

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.

None.

Verify that the highlighted data is in error and amend the JCL accordingly.

EQQM368E

IF STATEMENT REFERS BACK TO STEP PRIOR TO RESTART STEP

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.

None.

Verify that the step being referred to is correct and amend the JCL accordingly.

EQQM369E

UNABLE TO OVERRIDE THE JCL BECAUSE IT IS INSIDE RECURSIVE CALLED PROCEDURES

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

None.

Update the procedure manually for the duration of this job.

EQQM370W

THE JOBLOG FOR THIS OPERATION IS NOT COMPLETE

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.

None.

Use the JOB primary command to view the part of the joblog that is present (if any) and use the J row command in the Previous Operation list panel to update the JCL accordingly.

EQQM371W

THE STATEMENT CONTAINS A DATASET WITH DISPOSITION MOD

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

None.

Verify if the step was executed or not. If it was not, ignore this message. If it was executed, verify that a restart is possible or change the JCL accordingly.

EQQM372E

THE STATEMENT CONTAINS A REFERENCE TO A TEMPORARY DATASET

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.

None.

Change the JCL accordingly.

EQQM373W

STEP STATUS IS FLUSH. POSSIBLE INCONSISTENCIES EXIST

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.

None.

Change the JCL if necessary.

EQQM374W

STEP EXECUTION CONDITION TO A PREVIOUS STEP

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.

None.

If necessary, change the COND/IF keyword accordingly. Change AUTOSAVED as 100003 AUTOSAVE A1

EQQM375I

THE SCHEDULER WILL ATTEMPT TO DELETE THIS DATASET

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

None.

None.

EQQM376I

THE SCHEDULER WILL ATTEMPT TO UNCATALOG THIS DATASET

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

None.

None.

EQQM377I

THE SCHEDULER WILL ATTEMPT TO CATALOG THIS DATASET

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

None.

None.

EQQM378W

VERIFY JCL: THE SCHEDULER COULD DELETE WRONG DATASET (IEF377I)

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.

None.

Change if this could lead to problems, and, if so, remove the involved data sets from the data set list suggested by HCL Workload Automation for Z for deletion. If necessary, manually make any required changes or alter the JCL.

EQQM379W

THE JCL STATEMENTS CONTAIN AUTOMATIC RECOVERY STATEMENTS

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

The system waits for you to respond.

Select the Start cleanup with AR option to show a cleanup list consistent with the RESSTEP parameter defined in the JCL.

EQQM380W

JCL CONTAINS REFERENCES TO INSTREAM DATA THAT IS MISSING

The JCL statement contains a reference to instream data that cannot be located. Possible reasons for this error are:
  • An error was reported when HCL Workload Automation for Z submitted the operation that prevented the JCL from being stored in the JCL repository.
  • The JCL for this operation has been deleted from the JCL repository.
  • The operation was not submitted by HCL Workload Automation for Z and the corresponding data is not available in the JES job log.
  • The data is missing from one of the following: a DD * or DD DATA reference, a JES XMIT or DATASET statement, or a PASSWORD= keyword on the job card.

Processing continues.

Enter any required instream data.

EQQM382W

THE OPERATION CANNOT BE RESTARTED WITHOUT CHANGING THE JCL

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.

The system waits for you to respond.

Either edit and change the JCL or cancel the restart of the operation.

EQQM383E

THE ABSOLUTE GDG NUMBER IS MISSING FOR THIS DATASET

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

None.

Check to ensure that the GDG base exists and that the GDG level has not been deleted or that the data set has not been filtered out by a user exit.

EQQM384W

THE RESTART STEP IS INSIDE AN IF/THEN/ELSE CLAUSE

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

None.

Check to ensure that the step selected is the correct step and that the IF-THEN-ELSE clause is understood.

EQQM385E

NUMBER OF STEPS FOUND IN THE JOB LOG INCONSISTENT

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.

Processing continues.

Keep a copy of the event data set from the tracker where the job executed, the current plan, and the JCL repository, and contact the Software Support.

Contact your system programmer.

EQQM386W

THE GDG BASE IS MISSING FOR THIS DATASET

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

None.

Check that the GDG name is specified correctly. The GDG may be created during the life time of the job so this may not be an error.

EQQM388W

VERIFY JCL FOR POSSIBLE INCONSISTENCIES

One of the following situations has occurred:
  • At least one step staus of FLUSH was detected. Restarting from this step may be possible. However, verification for the status of data sets used in this step is recommended.
  • At least one IEF377I message was found in the job log. This means that in the previous run the job successfully allocated the data set, but did not manage to catalog it.

None.

If necessary, change the JCL. If flushed steps have been detected, message EQQM373W indicates which ones they are. If there are catalog problems, message EQQM378W indicates which data sets are involved. See the description for EQQM378W for details on what action should be taken.

EQQM396E

EXCLUDE SELECTION COMMAND(S) OUTSIDE RESTART SCOPE

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.

The panel is redisplayed with this error message.

Correct your definitions by moving the exclude commands inside the Start-End restart scope.

EQQM397E

SELECTED STEPS CHANGED - REBUILD JCL

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

The panel is redisplayed with this error message.

Change the selections, issue the GO command for the current selection, or CANCEL the step restart.

EQQM398W

NO STEPS HAVE BEEN SELECTED FOR THIS STEP RESTART

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

If you confirm the restart, HCL Workload Automation for Z performs cleanup of data sets for the entire job and the current JCL is resubmitted without modification.

Either accept the restart with the current JCL or cancel the step-level restart on the Step-Restart Confirmation panel.

EQQM400W

THE OPERATION HAS NOT BEEN SELECTED FOR RESTART

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

None.

Enter the S (select) row command to select the operation for restart and enter one of the other history row commands.

EQQM404I

THE JCL FOR THIS OPERATION MIGHT NOT BE THE ORIGINAL JCL

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

Processing continues.

Verify if the job needs to be changed before it is submitted.

EQQM407E

STEP RESTART REQUIRES MSGLEVEL=(1,1)

Step restart was invoked but the MSGLEVEL value specified in the job JCL is wrong. The required value is:
MSGLEVEL=(1,1)

The request is rejected.

Set MSGLEVEL to (1,1) to correct the job JCL and rerun the operation.

EQQM410E

DEADLINE ACTION NOT VALID. ALLOWED VALUES ARE: C, N, E, A, BLANK.

The action to be taken if the operation has not completed at the specified deadline is not valid. Allowed values are:
A
Only an alert message is issued.
C
The operation is set to Complete if its status allows it, otherwise it is NOPed.
E
The operation is set to Error with ODEA if its status allows it, otherwise it is ignored.
N
Operation and all its internal successors are NOPed, if their status allows NOPing. Otherwise it is ignored.
blank
No action is taken. Only an alert message is issued.

The request to write the record is rejected.

Set a correct value for the action.

EQQM411E

ACTION NOT VALID. ALLOWED VALUES ARE: C, N, E, A.

The action to be taken if the operation has not started at the specified day offset and time is not valid. The Not Started Action set is not valid. Allowed values are:
A
Only an alert message is issued.
C
The operation is set to Complete if its status allows it, otherwise it is NOPed.
E
The operation is set to Error with OLAT if its status allows it, otherwise it is ignored.
N
Operation and all its internal successors are NOPed, if their status allows NOPing. Otherwise it is ignored.

The request to write the record is rejected.

Set a correct value for the action.

EQQM412E

THE DAY OFFSET MUST BE A NUMBER 0 – 99.

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

The request to write the record is rejected.

Specify a value in the range 0-99.

EQQM413E

THE TIME IS REQUIRED.

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

The request to write the record is rejected.

Specify a value for the time.

EQQM414E

00.00 IS NOT ALLOWED AS A TIME.

The time set is not valid.

The request to write the record is rejected.

Specify the time in the format HH.MM.

EQQM415E

THE DAY IS REQUIRED.

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

The request to write the record is rejected.

Specify a value for the day.

EQQM416E

DEADLINE ACTION REQUIRES DEADLINE DAY OFFSET.

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

The request to write the record is rejected.

Specify a value for the day offset.

EQQM417E

NOT STARTED ACTION REQUIRES DAY OFFSET.

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

The request to write the record is rejected.

Specify a value for the day offset.

EQQM418E

NOT STARTED DAY AND TIME REQUIRE AN ACTION.

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

The request to write the record is rejected.

Specify a valid value for the action.

EQQM419E

THE VARIABLE DAY OFFSET IS NOT VALID, MUST BE A NUMBER 0-99.

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

The request to write the record is rejected.

Specify a value in the range 0-99.

EQQM420E

FILTER LATE CAN BE L (LATE ON LATEST OUT), N (LATE ON ALERT/ACTION), E (EITHER LATE ON LATEST OUT OR ON ALERT/ACTION), OR BLANK.

The value set for the LATE filter is not valid. Allowed values are:
blank
All operations, regardless if they started late or not.
L
Operations that did not start by their latest start time.
N
Operations that did not start by the day and time that you specified in Not started alert or Not started action.
E
Operations that did not start by either their latest start time or by the day and time that you specified in Not started alert or Not started action.

The request is rejected.

Set a valid value for the LATE field.

EQQM421E

THE DAY SET FOR THE NOT STARTED ALERT IS INVALID. MUST BE A NUMBER 0 - 99.

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

The request is rejected.

Specify a value in the range 0-99.

EQQM422E

THE TIME SET FOR THE NOT STARTED ALERT IS INVALID.

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

The request is rejected.

Specify a valid value for the time.

EQQM423E

THE DAY SET FOR THE VARIABLE NOT STARTED ALERT IS INVALID. MUST BE A NUMBER 0 - 99.

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

The request is rejected.

Specify a value in the range 0-99.

EQQM424E

THE TIME SET FOR THE VARIABLE NOT STARTED ALERT IS INVALID.

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

The request is rejected.

Specify a valid value for the time.

EQQM425E

THE DAY SET FOR THE NOT STARTED ACTION IS INVALID. MUST BE A NUMBER 0 - 99.

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

The request is rejected.

Specify a valid value for the action.

EQQM426E

THE TIME SET FOR THE NOT STARTED ACTION IS INVALID.

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

The request is rejected.

Specify a valid value for the time.

EQQM427E

THE DAY SET FOR THE VARIABLE NOT STARTED ACTION IS INVALID. MUST BE A NUMBER 0 - 99.

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

The request is rejected.

Specify a valid value for the day offset.

EQQM428E

THE TIME SET FOR THE VARIABLE NOT STARTED ACTION IS INVALID.

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

The request is rejected.

Specify a valid value for the time.

EQQM500E

RCLEANUP MUST BE SET TO YES TO ISSUE THIS REQUEST

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.

Request is rejected.

Set RCLEANUP to YES and check if the scheduler is correctly customized to support the Restart and cleanup function.

Ask the system programmer to customize the scheduler to support the restart and cleanup function.

EQQM501E

FL TASK MUST BE ACTIVE TO ISSUE THIS REQUEST

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.

Request is rejected.

Check the EQQMLOG file to see why the FL task is down.

Ask the system programmer to check why the FL task is not active.

EQQM502E

PSU TASK MUST BE ACTIVE TO ISSUE THIS REQUEST

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.

Request is rejected.

Check the EQQMLOG file to see why the PSU task is down.

Ask the system programmer to check why the PSU task is not active.

EQQM503E

OPER_INFO IS REQUIRED TO ISSUE THIS REQUEST

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.

Request is rejected.

Check the EQQMLOG file to understand what could cause the problem. This message is generally preceded by a more specific I/O error message. Check the HCL Workload Automation for Z message log to determine the cause of the error. To collect appropriate documentation for problem determination, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures, section "Information needed for all problems", sub-section "Information to collect for restart and cleanup problems". Search the IBM Support database for a solution at Support.

Ask the system programmer to check why OperInfo was not found.

EQQM504E

LOCAL DATA STORE IS NEEDED TO ISSUE THIS REQUEST

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

Request is rejected.

Retry later when the initialisation process is complete.

EQQM505E

CLEAN UP TYPE CANNOT BE AUTOMATIC

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.

Recovery statements will no longer be processed.

Check if the cleanup type can be changed to None, Immediate, or Manual.

EQQM506W

OPERATION CHANGE CAUSES PSU TAILORED JCL LOSS

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.

Pending restart and cleanup process will be suppressed.

None.

EQQM510E

CANNOT ADD REMOTE JOB INFO TO THE FOLLOWING OPERATION: APPL IA OPER ON WORKSTATION WSNAME. WORKSTATION IS NOT A REMOTE ENGINE OR REMOTE ENGINE TYPE IS NOT CONSISTENT.

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.

The requested change is not made.

None.

EQQM511E

CANNOT DELETE REMOTE JOB INFO IN THE FOLLOWING OPERATION: APPL IA OPER ON WORKSTATION WSNAME. WORKSTATION IS A REMOTE ENGINE.

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

The requested change is not made.

None.

EQQM512E

CANNOT UPDATE REMOTE JOB INFO FOR THE FOLLOWING OPERATION: APPL IA OPER ON WORKSTATION WSNAME. APPLICATION NAME 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 application name is not valid.

The requested change is not made.

None.

EQQM513E

CANNOT UPDATE REMOTE JOB INFO FOR THE FOLLOWING OPERATION: APPL IA OPER ON WORKSTATION WSNAME. 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 job stream name is not valid.

The requested change is not made.

None.

EQQM514E

CANNOT UPDATE REMOTE JOB INFO FOR THE FOLLOWING OPERATION: APPL IA OPER ON WORKSTATION WSNAME. 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 workstation name is not valid.

The requested change is not made.

None.

EQQM515E

CANNOT UPDATE REMOTE JOB INFO FOR THE FOLLOWING OPERATION: APPL IA OPER ON WORKSTATION WSNAME. JOB 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.

The requested change is not made.

None.

EQQM516E

CANNOT UPDATE REMOTE JOB INFO FOR THE FOLLOWING OPERATION: APPL IA OPER ON WORKSTATION WSNAME. THE COMPLETE IF BIND FAILS OPTION 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.

The requested change is not made.

None.

EQQM517E

CANNOT UPDATE REMOTE JOB INFO FOR THE FOLLOWING OPERATION: APPL IA OPER ON WORKSTATION WSNAME. OPERATION NUMBER 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.

The requested change is not made.

None.

EQQM518E

CANNOT UPDATE THE FOLLOWING OPERATION: APPL IA OPER ON WORKSTATION WSNAME. WORKSTATION IS A REMOTE ENGINE BUT NO REMOTE JOB INFO IS SPECIFIED.

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

The requested change is not made.

None.

EQQM519E

INCONSISTENCIES FOUND ON REMOTE JOB INFO OR WORKSTATION NAME

You are trying to modify an operation that was defined on a remote engine workstation, but either of the following occurred:
  • The remote job info specified are not valid or were not specified at all.
  • The workstation type is not consistent with the remote job info specified.

The requested change is not made.

Ensure that the workstation type is correct and the remote job info are consistent with it.

EQQM520E

RESOURCES AND CONDITIONS CANNOT BE SPECIFIED FOR OPERATION APPL IA OPER ON WORKSTATION WSNAME.

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

The requested change is not made.

None.

EQQM521E

SCHEDULING ENVIRONMENT CANNOT BE SPECIFIED FOR OPERATION APPL IA OPER ON WORKSTATION WSNAME.

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

The requested change is not made.

None.

EQQM522E

DEADLINE WTO MESSAGES CANNOT BE ISSUED FOR OPERATION APPL IA OPER ON WORKSTATION WSNAME.

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

The requested change is not made.

None.

EQQM523E

OPERATION APPL IA OPER ON WORKSTATION WSNAME CANNOT BE MADE ELIGIBLE FOR WLM ASSISTANCE.

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

The requested change is not made.

None.

EQQM600E

LAST RUN INFO NOT AVAILABLE

Possible reasons for the failure are the following:
  • RCLEANUP =YES was correctly specified in the OPCOPTS initial parameter statement, but a restart and cleanup request (Step restart, Job restart, Start cleanup, or Display cleanup result) was requested for an operation that did not run at least once producing a joblog.
  • You issued a restart and cleanup request for an operation that run at least once producing a joblog but the last run info cannot be retrieved because RCLEANIUP=NO was specified in the OPCOPTS initial parameter statement.
  • The operation did not run on a OS/390® system.

Request is rejected.

Verify the check list in the Explanation section.

Ask the system programmer to check the cause of the problem.

EQQM601I

NEEDED JOBLOG INFO REQUESTED TO PROCESS THE COMMAND.

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.

The dialog is displayed again.

Wait for the request to complete. Enter your dialog request again.

EQQM602W

JOBLOG INFO NEEDED TO PROCESS THE COMMAND. RETRIEVE IN PROGRESS

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.

Panel is redisplayed.

Wait for the request to complete. Re-enter your dialog request.

EQQM603E

NEEDED OPER_INFO NOT FOUND

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.

Panel is redisplayed.

Check the Controller and Data Store MLOG file to find error messages related to the operations.

Ask the system programmer to check the cause of the problem. Verify if the FL subtask is down on the controller and restart it.

EQQM604E

CLEAN UP STATUS DOES NOT ALLOW JOB RESTART

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

Request is rejected.

Wait for the restart and cleanup process to complete.

EQQM605E

CLEAN UP STATUS DOES NOT ALLOW STEP RESTART

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

Request is rejected.

Wait for the restart and cleanup process to complete.

EQQM606E

AN INVALID CLEAN UP STATUS WAS FOUND IN THE INPUT STRING

You specified an invalid cleanup status.

Request is rejected.

Specify a valid value.

EQQM607E

AN INVALID CLEAN UP TYPE WAS FOUND IN THE INPUT STRING

You specified an invalid cleanup type.

Request is rejected.

Specify a valid value.

EQQM608E

OPERATION STATUS DOES NOT ALLOW STEP RESTART

You issued a Step Restart for an operation whose status does not allow it:
  • If you are in a RERUN dialogue, you can only do this for the operation selected as the restart operation (and therefore with status temporarily changed to READY, and all external dependencies also in READY status).
  • Otherwise you can only do this for operations that are ready, in error, or complete.

Request is rejected.

Repeat the request according to the above explanation.

EQQM609W

JOBLOG INFO NEEDED TO PROCESS THE COMMAND. RETRY IN PROGRESS

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.

Panel is redisplayed.

Wait for the request to complete. Re-enter your dialog request.

EQQM610E

STEP NOT RESTARTABLE CANNOT BE SELECTED AS START STEP

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

Panel is redisplayed.

Choose another step as the restart step.

EQQM611E

STEP NOT EXECUTABLE CANNOT BE SELECTED AS START STEP

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

Panel is redisplayed.

Choose another step as the restart step.

EQQM612E

STEP NOT EXECUTABLE CANNOT BE SELECTED AS END STEP

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

Panel is redisplayed.

Choose another step as the end step.

EQQM613E

STEP NOT EXECUTABLE CANNOT BE INCLUDED

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

Panel is redisplayed.

Exclude the step from the restart range.

EQQM614E

STEP ALWAYS EXECUTABLE CANNOT BE EXCLUDED

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

Panel is redisplayed

Include the step in the restart range.

EQQM615E

CLEAN UP IN PROGRESS: CANNOT BE STARTED NOW

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

Request is rejected.

Wait for the restart and cleanup process to complete

EQQM616E

VALID SELECTION ARE S, E, X OR I

You have specified an invalid value for the step selection in the step restart panel. Allowed values are:
S
to indicate the restart step
E
to indicate the end step
X
to indicate a step that must not be executed
I
to indicate a step that must be executed if in the restart range

Request is rejected.

Specify a valid value.

EQQM617E

ONLY ONE START STEP IS ALLOWED

You set more than one step as the restart step.

Panel is redisplayed.

Specify only one start step.

EQQM618E

ONLY ONE END STEP IS ALLOWED

You set more than one step as the end step.

Panel is redisplayed.

Specify only one end step.

EQQM619E

MUST STEPS MUST BE INCLUDED IN THE RESTART RANGE

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

Panel is redisplayed.

Change the restart range.

EQQM620E

NO STEPS AVAILABLE. ONLY JR IS POSSIBLE

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

Panel is redisplayed.

Issue a Job restart.

EQQM622E

OPERATION STATUS DOES NOT ALLOW JOB RESTART

You issued a Job Restart for an operation whose status does not allow it:
  • If you are in a RERUN dialog, you can only do this for the operation selected as the restart operation (and therefore with status temporarily changed to READY, and all external dependencies also in READY status).
  • Otherwise you can only do this for operations that are ready, in error, or complete.

The request is rejected.

Repeat the request according to the above explanation.

EQQM623W

EMPTY JCL CANNOT BE USED FOR RESTART

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

The panel is displayed again.

None.

EQQM624E

EMPTY JCL CANNOT BE USED FOR RESTART.

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.

The panel is displayed again.

None.

EQQM625I

NO CLEAN UP ACTIONS ARE REQUIRED

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.

Panel is redisplayed.

None.

EQQM626E

CLEAN UP TYPE NONE DOES NOT ALLOW TO START CLEAN UP

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

Request is rejected.

Check the cleanup type value and change it in order to perform the Start Cleanup request.

EQQM627E

OPERATION STATUS DOES NOT ALLOW START CLEANUP

You issued a Start cleanup for an operation having a status that does not allow it:
  • Or the operation code is Started
  • Or the operation is ready and a standalone cleanup has already been executed.

Request is rejected.

None.

EQQM628E

WHILE MODIFYING AN OCCURRENCE ONLY SC AND DC ARE ENABLED

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

Request is rejected.

None.

EQQM629E

WHILE MODIFYING AN OCCURRENCE ONLY SC AND DC ARE ENABLED

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

Request is rejected.

None.

EQQM630I

LAST CLEANUP RESULT NOT MERGED IN OPERINFO. UPDATE WAS REQUESTED

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.

Panel is redisplayed.

Wait for update process complete.

EQQM631I

A RC REQUEST STILL IN PROGRESS IS UPDATING THE CLEANUP STATUS

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

Request is rejected.

Wait for restart and cleanup process to complete, then reissue the command.

EQQM632I

RESTART AND CLEANUP NOT APPLICABLE FOR A DELETED OPERATION

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

Request is rejected.

None.

EQQM633I

THE REQUEST TO DISCARD THE CLEAN UP ACTIONS HAS BEEN CANCELLED

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.

None.

None.

EQQM634I

THE CLEAN UP ACTIONS FOR THIS OPERATION ARE DISCARDED

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.

None.

None.

EQQM635E

VALID VALUES: A, I, M OR N

You have entered an incorrect cleanup type. Allowed values are:
A
Automatic
I
Immediate
M
Manual
N
None

The system waits for you to respond.

Enter the correct value.

EQQM636E

INSUFFICIENT AUTHORITY TO DO CLEAN UP ACTIONS

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

The system waits for you to respond.

Check if the CMAC fixed resource is defined and which type of authorization you assigned to CMAC.

EQQM637I

A JOBLOG IS NEEDED TO PROCESS THE COMMAND. IT HAS BEEN REQUESTED

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.

The panel is redisplayed with this information message.

Wait for the request to complete. Check the joblog retrieval status field or wait to get a TSO-broadcast that the request has completed. Re-enter your dialog request.

EQQM638I

JOBLOG IS NEEDED TO PROCESS THE COMMAND. IT IS NOT YET RETRIEVED

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

The panel is redisplayed with this information message.

Wait for the request to complete. Check the joblog retrieval status field or wait to get a TSO-broadcast that the request has completed. Re-enter your dialog request.

EQQM639E

A JOBLOG IS NEEDED TO PROCESS THE COMMAND. COULD NOT BE RETRIEVED

You tried to retrieve a joblog but it could not be located for the operation. This happens when the operation ends in error with one of the following error codes :
OSEQ
OSSS
OSUF
OSSC
OSUB
OFSI
OSUP
OFSQ
OJCV
OFSS
JCLI
OFSC
MCP
CLNO
OSSI
CLNA
OSSQ
It also happens when the operation defined in a fault-tolerant workstation ends in error.

No joblog is displayed.

None.

HCL Workload Automation for Z cannot browse the joblog. Check the error code explanation in the manuals.

EQQM640E

A JOBLOG IS NEEDED TO PROCESS THE COMMAND. LOG INFO NOT AVAILABLE

You tried to perform one of the following actions:
  • To retrieve the joblog of an operation.
  • To request a restart and cleanup action (Step restart, Job restart, Start cleanup, Display cleanup result).
  • To retrieve the recovery joblog for a not centralized job.
To process the command the scheduler needs to know the last job run id (jobname, jobid, start reader date, and time) but the records CP14 or CP24 that contain these data were not found.

The command is not processed.

As described in the Explanation section of this message, the scheduler was unable to retrieve the joblog of an operation. RCLEANUP=YES in the OPCOPTS initial parameter statement is mandatory to retrieve the OS/390 job log. Before proceeding in the analysis of this problem, check the message log for any message related to this error condition. Most common causes of the missing creation of the CP14 or CP24 records are:
  • The job did not actually run (for example if the operation is in waiting status)
  • The operation job name is different from the job name in the job card.

The scheduler cannot perform job log retrieval or restart and cleanup actions. Contact your system programmer to check why the records CP14 or CP24 were not created.

EQQM641I

OPERINFO FOR JOBN(JNUM) RETRIEVED

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

None.

Re-enter the restart and cleanup selected action.

EQQM642E

OPERINFO FOR JOBN (JID) CANCELLED. REISSUE REQUEST

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.

None.

Re-enter the restart and cleanup selected action.

EQQM643W

OPERINFO FOR JOBN (JNUM) NOT RETRIEVED. REASON: ERRC

Structured joblog info retrieval process failed for the job identified by JOBN and JOBID. The reason for the failure is explained by the ERRC variable value:
000A
OPERINFO is not correctly stored on the data files.
0001
Job was not found nor in JES queue, neither in database. The EQQUX013 user exit might be active.
0002
An internal error occurred during data base write phase.
0003
Data Store Reader was inactive.
0004
Timeout was reached for the request.
0005
Data Store Connection is down.
0006
Job Log destination not found in FLOPTS.

If you changed the datastore destination name, verify that both the old and new destination names are specified in the FLOPTS statement. For further information, refer to the tracker and data store considerations in the Migrating section of the Installation Guide.

0007
An internal error occurred during Data Base call phase.
0008
An internal error occurred during Data Base request phase.
9999
Reason unknown.

The message is displayed as a TSO broadcast message to the requesting user at the first interaction after the message is sent.

Check the reason of the failure from the Data Store Log and message reason, and take the appropriate action.

According to specified failure reason:
0001
Contact system programmer
0002
Retry later
0003
Contact system programmer to start Data Store Reader and retry
0004
Retry later
0005
Contact system programmer to activate Data Store communication and retry
0006
Contact system programmer to correct FLOPTS keyword and retry
0007
Contact system programmer
0008
Contact system programmer
9999
Contact system programmer

EQQM644I

THERE ARE NO CLEANUP RESULTS TO BE DISPLAYED

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

The panel is redisplayed.

None.

EQQM645I

PROTECTED DATA SET CANNOT BE INCLUDED

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.

The panel is redisplayed with protected data set action set to X (excluded).

None.

EQQM647I

RETRIEVAL OF EQQCLEAN JOBLOG IS IN PROGRESS

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.

Restart and cleanup action is interrupted.

Wait until the process is complete, then repeat the restart and cleanup action.

EQQM648W

SYSIN MERGE FAILED: REAS

While running a JR or SR command from dialog, the expanded jcl was required, but it could not be correctly restored merging the missing SYSIN DD *; statement from JS JCL. The REAS explain in detail the kind of problem occurred:
  • EXPANDED JCL MISSING
  • JS JCL SYSIN INFO MISSING
  • EXPANDED JCL SYSIN INFO MISSING
  • EXPANDED JCL AND JS SYSIN MISMATCH
  • ERROR DURING MERGED JCL CREATION
  • ERROR DURING MERGE SYSIN PROCESS

The scheduler will use the partial expanded jcl built.

Except number 4 and 2, the other reasons indicate internal errors. Reason 4 indicates that a mismatch was found between the expanded JCL and the JCL got from JS VSAM: a sysin DD found empty in the expanded JCL was not found at all in the JS JCL.One possible reason is that sysin were in external procedures. Reason 2 indicates that the JS JCL was not found (maybe it has been deleted from JS). For all other reasons contact system administrator.

Try to identify the origin of the problem from EQQMLOG and EQQDUMP messages. For number 2 and 4, if possible, set the sysin manually, using the edit command. For other reasons, contact the Software Support.

EQQM649I

THE EXPANDED JCL WAS COMPLETED WITH JS JCL SYSIN DD *.

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.

The scheduler will use the expanded jcl built.

None.

EQQM650E

REQUEST REJECTED

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.

The panel EQQMJCL is displayed.

Delete the Restart keyword from the jobcard and enter GO to save and continue. Remove also the SYSCHK DD statement, if any.

EQQM651W

THE JCL WAS BUILT USING THE JS JCL SYSIN DD*;.

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.

The scheduler will use the JCL built using the SYSIN DD* of the JCL in the JS file.

The scheduler found that the program name has been modified in a previous run. Check the SYSIN DD merge result before entering the GO command.

EQQM654I

RCLOPTS STEPRESCHK(NO) ALLOWS STEP RESTART FLEXIBILITY.

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.

Processing continues.

None.

EQQM655E

INVALID CCODE SET NUMERIC CCODE LENGTH IS ONLY 4 CHARS, JUSTIFIED TO LEFT.

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

TWS z/OS justify to left the value.

Check if the justified value is the correct one.

EQQM656E

INVALID CCODE SET ALPHA CCODE CAN BE ONLY FLUSH OR NORUN

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.

Value is rejected.

Correct the value.

EQQM657I

MISSING STEPINFO. STEP INFORMATION ARE NOT AVAILABLE.

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.

EQQMERSL is displayed.

None.

EQQM659E

STEP COMMAND IS ONLY APPLICABLE WHEN EXPANDED JCL IS USED..

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 request is rejected.

Repeat the request according to the above explanation.

EQQM660E

RECOVERY INFO FOR THIS OPERATION DOES NOT EXIST.

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

The request is rejected.

None.

EQQM661E

ACTION NOT ALLOWED FOR NON-FAULT-TOLERANT WORKSTATION.

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

The request is rejected.

None.

EQQM663E

ACTION NOT ALLOWED WHEN FT WORK STATION WITH CENTRALIZED SCRIPT.

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

The request is rejected.

None.

EQQM664E

ACTION NOT ALLOWED WHEN CENTRALIZED SCRIPT NOT SPECIFIED.

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

The request is rejected.

Enter the correct value.

EQQM665E

CLEANUP TYPE MUST BE MANUAL

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 request is rejected.

Select the Start Cleanup option.

EQQM666E

NO AR RESTART STEP IS AVAILABLE

The automatic recovery function did not detect any restart steps.

The request is rejected.

Select the Start Cleanup option.

EQQM667E

OPERATION STATUS DOES NOT ALLOW TO START CLEANUP WITH AR

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

The request is rejected.

Repeat your request when the operation status is compatible with the option requested.

EQQM668E

EXPANDED JCL VALUE FORCED TO NO WITH AR STATEMENTS

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

The panel is displayed again.

None.

EQQM669E

INVALID ACTION - OPERATION STATUS DOES NOT ALLOW TO UPDATE THE SE NAME.

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

None.

Wait for the operation to complete, before changing the name.

EQQM670E

OPERATION STATUS DOES NOT ALLOW FOR FAST STEP RESTART

You issued a Fast Step Restart for an operation with a status that does not allow for it:
  • If you are in a RERUN dialog, you can only do it for the operation selected as the restart operation (and therefore with status temporarily changed to READY).
  • Alternatively, you can only do it for operations that are READY, in error, or COMPLETE.

The request is rejected.

Repeat the request according to the above explanation.

EQQM671E

OPERATION STATUS DOES NOT ALLOW FAST JOB RESTART

You issued a Fast Job Restart for an operation with a status that does not allow it:
  • If you are in a RERUN dialog, you can only do it for the operation selected as the restart operation (and therefore with status temporarily changed to READY).
  • Otherwise you can only do it for operations that are READY, in error, or COMPLETE.

The request is rejected.

Repeat the request according to the above explanation.

EQQM672W

THE JCL WAS MODIFIED AFTER ACTUAL START OF OPERATION

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

The panel is displayed again.

You can ignore the message and continue by repeating the request, or return to the Editing JCL panel and verify the JCL changes.

EQQM673W

MANUAL CLEANUP IS REQUIRED TO RESTART THE OPERATION

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 panel is displayed again.

Issue a standalone cleanup if you confirm the SJR request.

EQQM675W

THE JCL IS BEING TAKEN FROM JOBLIB SINCE IT IS NO LONGER IN JS DSN

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 panel is displayed again.

You can ignore the message and continue by issuing the GO command.

EQQM676I

FAST STEP RESTART IS BEING PROCESSED

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

Processing continues.

None.

EQQM677I

FAST JOB RESTART IS BEING PROCESSED

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

Processing continues.

None.

EQQM678W

A MESSAGE FOR A DYNAMICALLY ALLOCATED GDG WAS BYPASSED

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

Panel is re-displayed.

Check if your JCL needs to be modified before entering the GO command on EQQMMJCL panel to avoid wrong GDG simulation on restart.

EQQM679I

OPERINFO RETRIEVAL PROCESS RESTARTED FOR JOBN (JID) APPL: APPL, IA, OPER

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.

This message might occur because the scheduler detected a pending OPERINFO retrieval process just after the FL task start or restart. In both cases, OPERINFO must be requested again from the data store.
Note: OPERINFO contains the job run information related to step execution and data set allocation and is retrieved from the data store. It is required to perform both a restart and cleanup of a job.
OPERINFO is automatically requested for jobs that end in error if one the following is true:
  • The RCLOPTS RESTARTINFORETRIEVAL(ONERROR) initial parameter is specified.
  • The job has cleanup type IMMEDIATE.

The OPERINFO retrieval process is restarted.

Check the status of the operation in the panel identified by application name APPL, Input arrival IA and operation number OPER. If a Retry is in progress, wait for it to complete to see if the process recovers automatically. If it does not recover automatically, or if the operation was already set to error CLNC or CLNO, try to manually recover the situation, as follows:
  • Check from Controller/Data Store EQQMLOG to determine why the retrieval process could have been failed.
  • Fix the problem if possible (for example: retrieval failed due to data store not active: restart it).
  • Run the display cleanup result to re-update OPERINFO with the latest information from the standalone cleanup.
  • Try the ARC command if applicable.
  • Run start cleanup from panel if needed.

EQQM680E

ACTION NOT VALID

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

The request is rejected.

None.

EQQM681E

CANNOT KILL UNLESS STATUS IS STARTED AND EXTENDED STATUS IS EXECUTING

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

The request is rejected.

None.

EQQM682E

INCONSISTENT OPTION WHEN SA WORKSTATION.

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

The request is rejected.

Enter a valid option.

EQQM683E

CONDITION COND ON OPERATION APPL IA OPER IS FALSE AND CANNOT BE MANUALLY DELETED.

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

The request is rejected.

Specify a valid selection.

EQQM684E

OPERATION APPL IA OPER IS SCHEDULED ON AN FTA NOT CENTRALIZED. CONDITIONS CANNOT BE DEFINED ON IT.

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

The request is rejected.

Specify a valid selection.

EQQM685E

STATUS CHANGE NOT ALLOWED FOR APPL IA OPER. A TRUE CONDITION POINTING TO IT AND DEFINED ON ONE OF ITS CONDITIONAL SUCCESSORS WOULD BECOME INCONSISTENT AS A CONSEQUENCE OF THIS STATUS CHANGE.

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

The request is rejected.

Specify a valid selection.

EQQM686E

THERE IS A TRUE SUCCESSOR CONDITION FOR THIS OPERATION.

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

The request is rejected.

Specify a valid selection.

EQQM687W

CONDITIONAL SUCCESSOR RESOLUTION CANNOT CREATE A NEW CONDITION ID ON OPERATION APPL IA OPER SINCE ALL POSSIBLE NUMBERS BETWEEN 1 AND 999 ARE USED IN AD/CP RECORDS FOR THIS OPERATION.

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

Processing continues, without resolving conditional successors that require to generate a new condition number.

Consider changing the conditional dependency definition.

EQQM688E

CONDITION COND ON OPERATION APPL IA OPER CANNOT BE CHANGED. IT HAS BEEN AUTOMATICALLY GENERATED

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

The request is rejected.

Specify a valid selection.

EQQM689W

THIS CONDITION HAS BEEN AUTOMATICALLY GENERATED.

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

The request is rejected.

Specify a valid selection.

EQQM691E

OPERATION STATUS DOES NOT ALLOW FAST START CLEANUP.

You issued a Fast Start Cleanup for an operation with one of the statuses listed below that does not allow it:
  • The operation status is deleted
  • The operation status is started
  • The operation is ready and a stand-alone cleanup has already been processed.

The request is rejected.

None.

EQQM692I

FAST START CLEANUP IS BEING PROCESSED.

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

Processing continues.

None.

EQQM693E

CLEANUP IN PROGRESS: CANNOT BE STARTED NOW.

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

Request is rejected.

Wait for cleanup process to complete.

EQQM694E

CLEANUP TYPE TypeDOES NOT ALLOW TO START CLEANUP.

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

Request is rejected.

Check the cleanup type value and change it so that a Fast Start Cleanup (FSC) request can be processed.

EQQM695E

MODIFY CP REQUEST FAILED.

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

The changes are discarded.

Check the controller message log for error messages to determine the cause of the error.

EQQM698E

OPTION FOR MANUALLY HOLD MUST BE Y OR N.

Data entry error; see Data entry errors.

EQQM699E

STEP LIST CAN BE SELECTED ONLY FOR z/OS JOBS.

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

The list of steps is not shown.

None.

EQQM900E

INVALID SUBSYSTEM REQUEST. SEE EQQDUMP DATA SET.

Validation of data has failed.

The request is rejected.

Contact the Software Support. The dump data set (ddname EQQDUMP) contains a snap dump of the attempted request. This is needed for diagnostics.

Contact your system programmer.

EQQM901E

STATUS CHANGE NOT ALLOWED FOR OPERATION APPL IA OPER. SHADOW JOB CAN BE SET ONLY TO COMPLETE OR READY STATUS.

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.

The request is rejected.

Do not change the status of shadow jobs to values different from Ready or Complete.

EQQM902E

SHADOW JOB STATUS CAN BE CHANGED ONLY TO COMPLETE OR READY.

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 request is rejected.

Do not change the status of shadow jobs to values different from Ready or Complete.

EQQM903E

BIND IS ALLOWED ONLY FOR SHADOW JOB IN READY STATUS.

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.

The request is rejected.

To issue this command, ensure that the shadow job is in Ready status.

EQQM904W

BIND IS ALLOWED ONLY FOR SHADOW JOBS IN READY STATUS.

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.

The bind request is rejected, and will be performed later.

To run the Bind command manually, ensure that the shadow job is in Ready status.

EQQM905W

CANNOT BIND OPERATION APPL IA OPER BECAUSE ISSUER OF THE COMMAND IS NOT AUTHORIZED FOR THIS REQUEST.

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.

The modify request is accepted, but the Bind command is not run.

To run the Bind command, ensure that you have the required authorization.