EQQM910 - EQQM999
EQQM910E
USER USER NOT AUTHORIZED TO ACCESS RESOURCE: RESOURCE
A modify current plan request attempted to access the resource RESOURCE, but the user USER making the request was not authorized to access the resource.
The request is rejected.
Try to locate the error in the message log and contact your system programmer.
EQQM911E
INVALID DEPENDENCY INFO FOR: APPL, OPER, PRED: PRED
A modify current plan request failed because dependency data has been changed during the dialog session. The request was attempted for application APPL and operation number OPER. The number of the predecessor operation is PRED.
The request is rejected and message EQQM025E is issued.
If the error recurs, investigate the failing occurrence to see if any abnormal activities have been associated with it. Report the error to IBM Software Support.
The request contained a reference to a dependency that HCL Workload Automation for Z could not find or that was invalid. The operation and predecessor numbers are given in hexadecimal form. Use HEX ON when browsing the HCL Workload Automation for Z message log.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM912E
INVALID DEPENDENCY PRED TO: APPL, OPER
A modify current plan request failed because dependency data has been changed during the dialog session. The application for which the request was attempted is APPL and the operation number is OPER. The number of the predecessor operation is PRED.
This message is also issued when deletion of a mandatory predecessor is requested by a PIF program, but not all the required parameters have been set.
The request is rejected and message EQQM025E or EQQM027E is issued.
If the error recurs, investigate the failing occurrence to see if any abnormal activities have been associated with it. Report the error to IBM Software Support.
The request contained a reference to a dependency that HCL Workload Automation for Z could not find or that was invalid. The operation and predecessor numbers are given in hexadecimal form. Use HEX ON when browsing the HCL Workload Automation for Z message log.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM913E
INVALID OPERATION DETAIL REQUEST DETAILED REQUEST: MTD TOTAL REQUEST: MT0
A modify current plan request failed because the detailed information for an operation update was invalid.
The failing requests are printed in hexadecimal form. Use HEX ON when browsing the HCL Workload Automation for Z message log.
The request is rejected and message EQQM027E is issued.
If the error recurs, investigate the failing occurrence to see if any abnormal activities have been associated with it.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM914E
REQUEST TO DELETE OPERATION THAT DOES NOT EXIST OPERATION: APPL, IA, OPER
A modify current plan request to delete an operation failed because the requested operation did not exist in the occurrence.
The application ID, input arrival date and time, and operation number are listed.
The request is rejected and message EQQM025E is issued.
Check the EQQMLOG file to understand what could cause the problem.
If the error recurs, investigate the failing occurrence to see if any abnormal activities have been associated with it. 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 http://www.ibm.com/software/sysmgmt/products/support.
Dependency data has probably been changed during the dialog session.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM915E
DELETION OF OPERATION OPER IN APPL SPLITS NETWORK
A modify current plan request to delete an operation failed because the deletion would have split the occurrence network. The operation to be deleted is identified as application ID APPL and operation number OPER.
The request is rejected and message EQQM025E is issued.
If the error recurs, investigate the failing occurrence to see if any abnormal activities have been associated with it. Report the error to IBM Software Support.
Dependency data has probably been changed during the dialog session.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM916E
REQUEST TO ADD SPECIAL RESOURCE THAT ALREADY EXISTS OPERATION: APPL, OPER SPECIAL RESOURCE: SPR
A modify current plan request to add a special resource failed because the requested special resource already exists in the operation. The application ID and operation number are listed together with the special resource name.
The request is rejected and message EQQM025E is issued.
Check that the correct special resources are defined for the operation.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM919E
PREDECESSOR IS ALSO SUCCESSOR PREDECESSOR: PREDA, PREDO SUCCESSOR : SUCCA, SUCCO
A modify current plan request would have caused a loop in the network.
The application IDs and operation number are listed. The operation number is given in hexadecimal form. Use HEX ON when browsing the HCL Workload Automation for Z message log.
The request is rejected and message EQQM025E is issued.
If the error recurs, investigate the failing occurrence to see if any abnormal activities have been associated with it. Report the error to IBM Software Support.
Dependency data has probably been changed during the dialog session.
EQQM920E
EXTERNAL DEPENDENCY ALREADY EXISTS APPLICATION: APPLOPERATION: OPER PREDECESSOR: PREDAOPERATION: PREDO
A modify current plan request attempted to add a dependency that already exists.
The application IDs and operation numbers are listed. The operation numbers are given in hexadecimal form. Use HEX ON when browsing the HCL Workload Automation for Z message log.
The request is rejected and message EQQM025E is issued.
If the error recurs, investigate the failing occurrence to see if any abnormal activities have been associated with it. 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 http://www.ibm.com/software/sysmgmt/products/support.
Dependency data has probably been changed during the dialog session.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM921E
DELETE OF INTERNAL PREDECESSOR CONNECTION FAILED, REASON: RS APPLICATION: APPL, IA, OPERATION: OPER, DEPENDENCY: PREOP
- 921
- The last internal dependency cannot be deleted.
- 922
- The delete would have resulted in a split into two networks.
- 923
- The predecessor specification is not found.
The request is rejected and the requestor is notified of the error with a message.
If the error recurs, investigate the failing occurrence to see if any abnormal activities have been associated with it. Report the error to IBM Software Support.
The last line of the message identifies the occurrence and the internal dependency that was to be deleted.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM922E
REQUEST TO DELETE SPECIAL RESOURCE THAT DOES NOT EXIST OPERATION: APPL, OPER SPECIAL RESOURCE: SPR
A modify current plan request to delete a special resource failed because the requested special resource does not exist in the operation. The application ID and operation number are listed together with the special resource name.
The request is rejected and message EQQM025E is issued.
Check that the correct special resources are defined for the operation.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM923I
JOBLOG FOR JOBN (JOBNUM) ARRIVED FOR OPERATION: APPL, IA, OPER
You have made a browse-joblog request on a HCL Workload Automation for Z subsystem.
The message is displayed as a TSO broadcast message to the requesting user at the first interaction after the message is sent.
Enter the browse-joblog command.
EQQM924E
INVALID REQUEST TO MCP - REQUEST FOLLOWS REQUEST
A modify current plan request was invalid.
The request is given in hexadecimal form. Use HEX ON when browsing the HCL Workload Automation for Z message log.
The request is rejected and message EQQM025E is issued.
If the error recurs, investigate the failing occurrence to see if any abnormal activities have been associated with it. 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 http://www.ibm.com/software/sysmgmt/products/support.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM925E
PRINT OPERATION HAS NO PREDECESSOR OPERATION: APPL, IA, OPER
A modify current plan request would have caused a print operation to have no predecessors.
The application ID, input arrival date and time, and operation number are listed. The operation number is given in hexadecimal form. Use HEX ON when browsing the HCL Workload Automation for Z message log.
The request is rejected and message EQQM025E is issued.
If the error recurs, investigate the failing occurrence to see if any abnormal activities have been associated with it. 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 http://www.ibm.com/software/sysmgmt/products/support.
Dependency data has probably been changed during the dialog session.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM926E
PRINT OPERATION HAS MORE THAN 1 PREDECESSOR OPERATION: APPL, IA, OPER
A modify current plan request would have caused a print operation to have more than one predecessor.
The application ID, input arrival date and time, and operation number are listed. The operation number is given in hexadecimal form. Use HEX ON when browsing the HCL Workload Automation for Z message log.
The request is rejected and message EQQM025E is issued.
If the error recurs, investigate the failing occurrence to see if any abnormal activities have been associated with it. 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 http://www.ibm.com/software/sysmgmt/products/support.
Dependency data has probably been changed during the dialog session.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM927E
PRINT OPERATION HAS NO CPU PREDECESSOR OPERATION: APPL, IA, OPER
A modify current plan request would have caused a print operation to have no computer operation predecessor.
The application ID, input arrival date and time, and operation number are listed. The operation number is given in hexadecimal form. Use HEX ON when browsing the HCL Workload Automation for Z message log.
The request is rejected and message EQQM025E is issued.
If the error recurs, investigate the failing occurrence to see if any abnormal activities have been associated with it. 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 http://www.ibm.com/software/sysmgmt/products/support.
Dependency data has probably been changed during the dialog session.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM928E
SETUP OPERATION HAS INVALID SUCCESSOR OPERATION: APPL, IA, OPER
A modify current plan request would have caused a job setup operation to have no valid computer operation successor.
The application ID, input arrival date and time, and operation number are listed. The operation number is given in hexadecimal form. Use HEX ON when browsing the HCL Workload Automation for Z message log.
The request is rejected and message EQQM025E is issued.
If the error recurs, investigate the failing occurrence to see if any abnormal activities have been associated with it. 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 http://www.ibm.com/software/sysmgmt/products/support.
Dependency data has probably been changed during the dialog session.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM929W
JOBLOG FOR JOBN (JNUM) NOT FOUND
You have made a browse—joblog request on an HCL Workload Automation for Z subsystem.
The message is displayed as a TSO broadcast message to the requesting user at the first interaction after the message is sent.
If the end- to- end feature check the connection is present or joblog is on workstation.
EQQM930E
CP MAY BE DESTROYED DUE TO ERRORS DURING MCP UPDATE
An error occurred while updating the current plan, causing it to be partially updated.
Processing is terminated for the current request and message EQQM025E is issued.
See message EQQM936E.
Previous error messages in the HCL Workload Automation for Z message log contain additional information about this error.
EQQM931W
JOBLOG FOR JOBN (JNUM) IN ERROR
You have made a browse-joblog request on an HCL Workload Automation for Z subsystem, but there has been an error when retrieving the joblog.
The message is displayed as a TSO broadcast message to the requesting user at the first interaction after the message is sent.
Check the server log for additional messages (connection problems). Check the STDLIST directory on the HCL Workload Automation workstation where the job ran.
EQQM932E
OPERATION OPNUM IS TOO LARGE - MCP UPDATE NOT POSSIBLE
A modify current plan request was rejected because it would have caused a current plan record to become larger than the maximum record size in the current plan data set.
The current plan is not updated and message EQQM164E is issued.
If the maximum record size for the current plan is too small, reallocate the current plan data sets with a larger record size: stop HCL Workload Automation for Z, copy the current plan data sets, and restart with the new data sets.
If the failing operation contains many special resources or dependencies, simplify the definition of the operation and retry the modify current plan request. If the error recurs, investigate the failing occurrence to see if any abnormal activities have been associated with it. 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 http://www.ibm.com/software/sysmgmt/products/support.
Determine if the maximum record size of the current plan is smaller than recommended, or if the failing operation contains too many special resources or too many dependencies.
EQQM933E
WORK STATION WSNAME NOT FOUND FOR OPERATION: APPL: APPL, IA, OPER
A modify current plan request specifies an operation on a workstation (WSNAME) that is not defined to the current plan.
The application ID, input arrival date and time, and operation number are listed. The operation number is given in hexadecimal form. Use HEX ON when browsing the HCL Workload Automation for Z message log.
The request is rejected and message EQQM025E is issued.
If the error recurs, investigate the failing occurrence to see if any abnormal activities have been associated with it. 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 http://www.ibm.com/software/sysmgmt/products/support.
Dependency data has probably been changed during the dialog session.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM934E
JOBLOG FOR jobn (jid) CANCELLED. REISSUE REQUEST.
A Joblog or operinfo retrieval request has been initiated but an error occurred (for example connection lost and then resumed among Controller and Data Store).
The request status is reset so that it can be issued again.
The message is displayed as a TSO broadcats message to the requesting user at the first interaction after the message is sent.
Reissue the request from the dialog.
EQQM935E
WORK STATION WSNAME NOT FOUND IN WQA
A modify current plan request attempts to update a workstation (WSNAME) that is not defined to the current plan in the workstation queue area.
The request is rejected and message EQQM025E is issued.
None.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM936E
NORMAL MODE MANAGER WILL RESTART FROM CHECKPOINT
A serious error related to the current plan data set has occurred.
The normal mode manager (NMM) subtask restarts and re-creates the current plan data set.
If the recovery procedure fails, that is, the NMM is unable to restart, HCL Workload Automation for Z should be canceled (not stopped). If the subsystem is stopped, the error extends to the alternative current plan data set. If the recovery procedure is successful, HCL Workload Automation for Z normal processing can continue.
Use the HCL Workload Automation for Z message data set to investigate the cause of the original error.
EQQM937E
TURNOVER IN PROCESS AND OCCURRENCE HAS STATUS COMPLETE APPLICATION: APPL
An attempt to modify an occurrence with status complete during a turnover has been rejected.
The request is rejected and either message EQQM027E or message EQQM028I is issued.
To rerun the occurrence or any of its operations, use the Modify Current Plan dialog to add a new occurrence. This is necessary because HCL Workload Automation for Z does not copy a completed occurrence to the new current plan. If the error recurs, investigate the failing occurrence to see if any abnormal activities have been associated with it. 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 http://www.ibm.com/software/sysmgmt/products/support.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM938W
JOBLOG JOBN (JNUM) NOT RETRIEVED. REASON: ERRC
- 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 database 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.
- 0007
- An internal error occurred during database call phase.
- 0008
- An internal error occurred during database request phase.
- 0009
- Data store parameter STOUNSD(N) does not allow retrieval.
- 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.
- 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 corect FLOPTS keyword and retry
- 0007
- Contact system programmer
- 0008
- Contact system programmer
- 0009
- Change parameter STOUNSDS value to Y
- 9999
- Contact system programmer
EQQM940E
THE NUMBER OF USER FIELDS FOR APPL, OPNUM EXCEEDS THE MAXIMUM LIMIT. MCP UPDATE NOT POSSIBLE.
An attempt to modify the user field for application APPL, operation OPNUM has been rejected, because the number of user fields is higher than 120, which is the maximum allowed.
The request is rejected.
To correct the error, delete a user field and submit the request again.
EQQM941E
USER FIELD NAME IS BLANK FOR APPL, OPNUM
A modify current plan request failed because the user filed name is blank. The request was attempted for application APPL and operation number OPNUM.
The request is rejected and message EQQM025E is issued.
Ensure that a name is specified for each user field related to the specified application and operation.
EQQM942E
MAX NUMBER OF USER FIELDS REACHED FOR APPL, OPNUM
A modify current plan request failed because the number of user fields exceed the maximum number allowed. The request was attempted for application APPL and operation number OPNUM.
The request is rejected and message EQQM025E is issued.
Ensure that the user fields defined for the specified application and operation do not exceed the maximum allowed.
EQQM943E
USER FIELD UFNAME ALREADY PRESENT FOR APPL, OPNUM
A modify current plan request failed because the user field UFNAME already exists for application APPL and operation number OPNUM.
The request is rejected and message EQQM025E is issued.
Ensure that the correct user fields are defined for the specified application and operation.
EQQM944E
USER FIELD UFNAME FOR APPL, OPNUM DOES NOT EXIST
A modify current plan request failed, because the user field UFNAME is not defined for application APPL and operation number OPNUM.
The request is rejected and message EQQM025E is issued.
Specify a user field name that is defined for the specified application and operation.
EQQM945I
JOBLOG RETRIEVAL PROCESS RESTARTED FOR JOBN (JID) APPL: APPL, IA, OPER
- The
RCLOPTS JOBLOGRETRIEVAL(ONERROR)initial parameter is specified. - The
HTTOPTS JOBLOGRETRIEVAL(ONERROR)initial parameter is specified.
The JOBLOG retrieval process is restarted.
EQQM946I
JOBLOG REQUEST FOR JOBN (JNUM) WAS SUSPENDED BECAUSE THE DESTINATION DEST IS OFFLINE. APPL: APPL, IA, OPER
The scheduler suspended the JOBLOG Retrieval process for the job identified by Job Name JOBN and Job ID JNUM because the related destination is OFFLINE. This message applies only to z-centric and dynamic workstations.
The JOBLOG retrieval process is suspended.
Determine why the destination is set OFFLINE and try to set it back ONLINE.
EQQM947E
OPER IS LAST OPERATION OF APPL
The operation is the last one of the application.
The operation will not be deleted.
Consider to delete the entire occurrence.
EQQM949I
OCCURRENCE NOT ADDED: SET AUTOMATIC DEP TO Y
You requested to add to the plan an application specifying AUTOMATIC DEP to No, meaning that all conditions on it had to be deleted. To confirm the request, panel EQQMCADC was displayed informing you about conditions deletion. In that confirmation panel you selected No so the application was not added to the plan and the message EQQM949I was prompted.
None.
If you want to add the application keeping its conditions make sure AUTOMATIC DEP is set to Y.
EQQM950E
INPUT ARRIVAL NOT WITHIN CURRENT PLAN, ENDS CPE REQUEST
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. The request type is given by REQUEST.
The request is terminated with an error return code.
If necessary, extend the current plan to get the failing function to work.
This message should be followed by another message from the function requesting the current plan modification.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM951E
FAILED TO ADD APPLICATION ADID REASON: CANNOT READ CURRENT PLAN RECORD
A request to create an occurrence on the current plan failed due to an I/O error.
The request is terminated and the processing continues with the next request.
Review the message log of the HCL Workload Automation for Z subsystem to determine the cause of the error. If you cannot determine the cause and the error persists, contact the Software Support.
Resubmit the job when the problem causing the I/O error has been corrected.
The message log contains the I/O error message.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM952E
FAILED TO ADD APPLICATION ADID REASON: NO UNIQUE INPUT ARRIVAL TIME LEFT IN CP FOR THIS APPLICATION
A request to create an occurrence on the current plan failed because the occurrence already exists- In the request, no input arrival time was given, which implies that a default input arrival time should be selected. This default 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.
The request is terminated and processing continues with the next request.
If necessary, extend the current plan to get the failing function to work.
This message should be followed by another message from the function requesting the current plan modification.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM953E
FAILED TO ADD APPLICATION ADID REASON: 'ADD' TIME LATER THAN CURRENT PLAN END TIME
A request to create an occurrence on the current plan failed because the current plan end time has passed. In the request, no input arrival time was given, which implies that a default input arrival time should be used. This default is the current time, consisting of the current date, current hour, and current minute. The request is rejected because the current plan ends before current time.
The request is terminated and processing continues with the next request.
If necessary, extend the current plan to get the failing function to work.
This message should be followed by another message from the function requesting the current plan modification.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM954E
FAILED TO ADD APPLICATION ADID NO ACTIVE VERSION OF THE APPLICATION DESCRIPTION IN THE DATA BASE
The HCL Workload Automation for Z subsystem has received a request to add an occurrence of application ADID to the current plan. The application description in the EQQADDS file could not be read (record not found).
The request to add the current plan occurrence is rejected.
Correct the errors.
If the attempt to add an application was caused by an event-triggered tracking (ETT) triggering event, check the ETT triggering criteria. Make sure that the triggering event points to an active application description.
If the attempt to add an application was caused by a program interface request, check the application name given in the program interface request.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM955E
FAILED TO ADD APPLICATION ADID CAN NOT READ THE APPLICATION DESCRIPTION FILE
The HCL Workload Automation for Z subsystem has received a request to add an occurrence of application ADID to the current plan. The application description file was not open.
The request to add the current plan occurrence is rejected.
To rerun the occurrence or any of its operations, use the Modify Current Plan dialog to add a new occurrence. This is necessary because HCL Workload Automation for Z does not copy a completed occurrence to the new current plan. If the error recurs, investigate the failing occurrence to see if any abnormal activities have been associated with it. 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 http://www.ibm.com/software/sysmgmt/products/support.
The message log should contain a previous message giving the reason why the file is not open.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM956E
FAILED TO ADD/MODIFY APPLICATION ADID. OCCURRENCE WITH SAME APPLICATION ID AND INPUT ARRIVAL EXISTS IN THE LONG-TERM PLAN
A request to create or modify an occurrence in the current plan failed because the request specified an application ID and input arrival date and time that are the same as an existing occurrence in the long-term plan.
The request to create or modify the occurrence in the current plan is rejected.
To rerun the occurrence or any of its operations, use the Modify Current Plan dialog to add a new occurrence. This is necessary because HCL Workload Automation for Z does not copy a completed occurrence to the new current plan. If the error recurs, investigate the failing occurrence to see if any abnormal activities have been associated with it. 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 http://www.ibm.com/software/sysmgmt/products/support.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM957W
JOBLOG FOR RECOVERY JOB JNUM NOT FOUND
You have made a Browse Recovery Job Joblog request on an HCL Workload Automation for Z subsystem. The message is sent if the joblog is not in the SDTLIST directory of the HCL Workload Automation for Z CPU where the recovery job ran.
The message is displayed as a TSO broadcast message to the requesting user at the first interaction after the message was sent.
EQQM958I
JOBLOG FOR RECOVERY JOB JNUM ARRIVED
You have made a Browse Recovery Job Joblog request on an HCL Workload Automation for Z subsystem. The message is displayed when the joblog is available for browsing.
The message is displayed as a TSO broadcast message to the requesting user at the first interaction after the message was sent.
Enter the Browse Joblog command.
EQQM959W
JOBLOG FOR RECOVERY JOB JNUM IN ERROR
You have made a Browse Recovery Job Joblog request on an HCL Workload Automation for Z subsystem, but there has been an error in the retrieval of the job log.
The message is displayed as a TSO broadcast message to the requesting user at the first interaction after the message was sent.
Check the server log for additional messages (such as for connection problems). Check the SDTLIST directory of the HCL Workload Automation for Z CPU where the recovery job ran.
EQQM960E
OPERATION APPL IA OPER IS NOT IN STATUS R/*/A/W. CONDITIONS CANNOT BE ADDED ON IT.
A request to add the indicated condition in the current plan failed because it is inconsistent with the processed operation status.
The request is rejected.
Check the operation status before repeating the request.
EQQM961E
MODIFY CURRENT PLAN REQUEST FAILED, INSUFFICIENT STORAGE. REASON: RS
A request to create or modify an occurrence on the current plan failed due to storage allocation failure. The reason code provides debugging information.
The request is terminated and processing continues with the next request.
Allocate a larger region to the HCL Workload Automation for Z subsystem and restart the subsystem. If the error persists, contact the Software Support.
This message should be followed by another message from the function requesting the current plan modification.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM962E
COMMAND TEXT HAS NO VALUE IN SYSTEM AUTOMATION DATA FOR APPLICATION APPL, INPUT ARRIVAL IA, OPERATION OPER
Command text is required when system automation information is specified. The related operation is identified by the application ID, input arrival date and time, and operation number.
HCL Workload Automation for Z does not complete the operation.
Specify the command text in the system automation information for the operation.
EQQM964E
AUTOMATED FUNCTION IS NOT ALPHANUMERIC IN SYSTEM AUTOMATION DATA FOR APPLICATION APPL, INPUT ARRIVAL IA, OPERATION OPER
Automated function is optional when system automation information is specified. If you specify it, ensure that it is an alphanumeric value, uppercase. The related operation is identified by the application ID, input arrival date and time, and operation number.
HCL Workload Automation for Z does not complete the operation.
Specify a valid value for the automated function in the system automation information for the operation.
EQQM965E
WORK STATION WSNAME DOES NOT SUPPORT SYSTEM AUTOMATION. APPL: APPL, IA BEING ADDED OR MODIFIED HAS SYSTEM AUTOMATION DATA DEFINED FOR OPERATION OPER
A current plan operation is added or modified and System Automation data is defined for the operation but the workstation is not for Automation.
The action cannot be continued and the modification cannot be saved.
Check that the workstation used has the Automation option set to Y. If you are trying to change the workstation from Automation to non Automation, change it back or use an Automation workstation. If you no longer need this operation to be a System Automation operation, you must delete it and create a new one.
EQQM966E
WORK STATION WSNAME IS FOR SYSTEM AUTOMATION. APPL: APPL, IA BEING ADDED OR MODIFIED HAS NO SYSTEM AUTOMATION DATA DEFINED FOR OPERATION OPER
The definition or modification of an application 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 information is appropriately defined.
Ensure that you are using the correct workstation. If you are trying to change the workstation from non Automation to Automation, change it back or specify the required system automation information (command text, at least).
EQQM967E
OPERATION PREDAD PREDIA PREDNO CANNOT BE ADDED AS A CONDITIONAL PREDECESSOR FOR OPERATION OPERAD OPERIA OPERNO, SINCE IT IS ALREADY A NORMAL PREDECESSOR.
You cannot define the same job as both conditional and normal predecessor.
The request is rejected.
Specify a valid selection.
EQQM968E
OPERATION PREDAD PREDIA PREDNO CANNOT BE ADDED AS A NORMAL PREDECESSOR FOR OPERATION OPERAD OPERIA OPERNO, SINCE IT IS ALREADY A CONDITIONAL PREDECESSOR.
You cannot define the same job as both conditional and normal predecessor.
The request is rejected.
Specify a valid selection.
EQQM969E
CONDITION COND DEFINED ON OPERATION APPL IA OPER IS EVALUATED OR DOES NOT EXIST. CHANGES ARE NOT ALLOWED.
A request to modify the indicated condition in the current plan failed because it is inconsistent with the condition status.
The request is rejected.
Specify a valid selection.
EQQM970W
THE POTENTIAL PREDECESSOR RECORD FOR APPLICATION APPL COULD NOT BE UPDATED THE MAXIMUM NUMBER (3000) OF POTENTIAL SUCCESSOR OPERATIONS HAS BEEN REACHED SUCC.
The modify current plan (MCP) service processor was unable to add any more successor operation entries to a potential predecessor record. Since the record could not be updated as intended, it now does not define all potential successors for application APPL. If new occurrences of this application are added by program interface (PIF) programs or by the event-triggered tracking (ETT) function it is no longer possible to add all possible successor dependencies automatically.
The MCP processor continues processing the current add occurrence request.
Use the Modify Current Plan dialog to add new occurrences of the application defined by this message and use the DEP primary command to verify that successor dependencies have been set up correctly.
This message indicates that many different operations in different applications have defined operations of one application as external predecessors. If the message is unexpected, review the contents of the application description database and remove old applications that are no longer used.
EQQM971E
FAILED TO ADD APPLICATION ADID. REQUESTING FUNCTION IS FUNC REASON: MAXIMUM NUMBER OF OCCURRENCES OF THIS APPLICATION REACHED
No more occurrences of this application can be added. HCL Workload Automation for Z can handle approximately 870 occurrences of each application.
- E
- Event-triggered tracking
- A
- Automatic recovery
- D
- Dialog
The create request is rejected.
Change the criteria for event-triggered tracking. Complete or delete occurrences of this application that are no longer needed. These occurrences are removed from the plan when a new plan is produced.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM972E
MCP WAS UNABLE TO ADD APPLICATION APPL BECAUSE AN MCP CONTROL BLOCK (MT0) COULD NOT CONTAIN ALL SUCCESSOR DEPENDENCIES TO APPLICATION SUCC
The modify current plan (MCP) service processor was unable to add any more successor dependencies to the MT0 block that is used to define MCP processing. The maximum size of an MT0 block is 32768 bytes.
The MCP processor abandons the attempt to add current occurrence.
Use the Modify Current Plan dialog to add new occurrences of the application defined by this message, but do not request MCP to automatically add successor dependencies. The same recommendation applies if the occurrence is being added as a result of event-triggered tracking (ETT) trigger processing or by a program interface (PIF) program. Instead, add successor dependencies to the occurrence after it has been added to the plan.
This message indicates that many different operations in different applications have defined operations in current application as external predecessors. If the message is unexpected, review the contents of the application description database and remove old predecessor definitions that should no longer be used.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM975E
FAILED TO ADD APPLICATION ADID BECAUSE MAXIMUM NUMBER OF OCCURRENCES REACHED. REQUESTING FUNCTION IS FUNC.
- A
- Automatic recovery
- D
- Dialog
- E
- Event-triggered tracking
- P
- Program interface
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, or gradually increasing the value of MAXOCCNUM until EQQM975E is no longer issued.
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.
If the message is not in the controller message log, review the dump data set (ddname EQQDUMP) for more information.
EQQM976W
ONE OR MORE OF THE EXTERNAL DEPENDENCIES OF OPER OPER IN APPLICATION ADID WERE NOT RESOLVED WITHIN THE GROUP
Dependency loops in an occurrence group have been detected and eliminated.
At least one of the external dependencies for the operation has not been resolved within the group. If there are other occurrences, external to the group, in the current plan that matches the operations dependency definitions, the dependencies have been resolved for those occurrences. Message EQQM358W is issued.
Check how the dependencies have been resolved and, if appropriate, modify them. So as to avoid this situation, modify also the application descriptions for this group.
EQQM977E
STATUS CHANGE FAILED FOR OPERATION APPL, IA, OPER. CONDITION COND IS NOT TRUE FOR THE OPERATION.
The current status of the indicated operation is different from waiting. It is not consistent with the requested status change.
The request is rejected.
Verify the specified input.
EQQM979E
STATUS CHANGE NOT ALLOWED FOR OPERATION APPL, IA, OPER. NEW OR OLD STATUS IS SUPPRESSED BY COND (X).
Only an occurrence rerun request or internal scheduler actions can produce this kind of change.
The request is rejected.
Consider rerunning the occurrence.
EQQM980E
DUPLICATE CONDITION COND ON OPERATION: APPL, IA, OPER.
You defined the same condition twice.
The request is rejected.
Remove the duplicate entry.
EQQM981E
DUPLICATE CONDITION DEPENDENCY: SIMP ON CONDITION COND ON OPERATION: APPL, IA, OPER.
You defined the same condition dependency twice.
The request is rejected.
Remove the duplicate entry.
EQQM982E
COND ID NOT VALID FOR CONDITION COND ON OPERATION APPL, IA, OPER.
The processed condition number does not exist or is not valid. Valid values are in the range 1-999.
The request is rejected.
Check the specified value.
EQQM984E
DEPENDENCY TYPE NOT VALID IN CONDITION DEPENDENCY: SIMP ON CONDITION COND ON OPERATION: APPL, IA, OPER .
Condition type must be P or S.
The request is rejected.
Specify a valid value.
EQQM985E
CHECK TYPE NOT VALID IN CONDITION DEPENDENCY: SIMP ON CONDITION COND ON OPERATION: APPL, IA, OPER .
Condition type must be RC or ST.
The request is rejected.
Specify a valid value.
EQQM986E
PREDECESSOR NOT FOUND IN CONDITION DEPENDENCY: SIMP ON CONDITION COND ON OPERATION: APPL, IA, OPER.
The modify current plan failed when processing APPL, IA, OPER as predecessor data in the indicated condition dependency.
The request is rejected.
Verify the specified input.
EQQM987E
OPERATOR NOT VALID IN CONDITION DEPENDENCY: SIMP ON CONDITION COND ON OPERATION: APPL, IA, OPER.
The modify current plan process detected an incorrect logical operator. Valid values are GE, GT, LE, LT, EQ, NE, and RG. With condition type ST, valid values are EQ or NE only.
The request is rejected.
Verify the specified input.
EQQM988E
STATUS VALUE NOT VALID IN CONDITION DEPENDENCY: SIMP ON CONDITION COND ON OPERATION: APPL, IA, OPER .
The modify current plan process detected an incorrect value as predecessor status. Valid values are C (complete), E (ended-in-in-error), S (started), or X (suppressed by condition). If you use the NE operator, specify a final status (C, E or X).
The request is rejected.
Verify the specified input.
EQQM989E
RC VALUES NOT VALID IN CONDITION DEPENDENCY: SIMP ON CONDITION COND ON OPERATION: APPL, IA, OPER.
The modify current plan process detected that one or both the specified return codes are incorrect. They must be numeric values in the range 0-9999, or string values in the form Uxxx amd Sxxx.
The request is rejected.
Verify the specified input.
EQQM990E
MCP UPDATE FAILED. FAILING MTD BELOW: MTD
A modify current plan request failed because of an error.
The request is given in hexadecimal form. Use HEX ON when browsing the HCL Workload Automation for Z message log.
The request is rejected and another message explaining the error is issued.
Look at the other messages explanations for the cause of the error. If the error re-occurs, investigate the failing occurence to see if any abnormal activities have been associated with it. Report the error to IBM Software Support.
EQQM991E
ERROR DURING MCP UPDATE. FAILING MODULE: MODULE
A modify current plan request failed. Look for further messages that describe the error message reported by the modify current plan module MODULE. If message EQQM028I is issued, no additional message is issued.
The request is rejected and a further message is issued in the controller message log.
Look at the other messages explanations for the cause of the error. If you report the error message following this message to IBM Software Support, the information in this message is also required by IBM Software Support to diagnose the error.
EQQM992E
WRONG JOB DEFINITION FOR THE FOLLOWING OCCURRENCE: APPL, IA
The occurence identified by application name APPLand input arrival time IAcould not be added: a job definition referenced by an operation in this ocurrence is not correctly defined in the EQQSCLIB library.
The request is rejected.
Check the message log. Message EQQ3077E identifies the EQQSCLIB member in error.
EQQM993E
THE END-TO-END FEATURE IS NOT ACTIVE. CANNOT ADD OPERATIONS ON FTW FOR OCCURRENCE:APPL, IA
The occurence identified by application name APPL and input arrival time IA could not be added: it 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.
Install and configure the End-to-End feature. Assure 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.
EQQM994E
OPERATION APPL IA OPER ALREADY HAS A CONDITION COND DEFINED.
A request to add the indicated condition in the current plan failed because the condition already exists.
The request is rejected.
Specify a valid selection.
EQQM995E
OPERATION APPL IA OPER DOES NOT HAVE A CONDITION COND.
A request to process the indicated condition in the current plan failed because the condition does not exist.
The request is rejected.
Specify a valid selection.
EQQM996E
CONDITION COND ON OPERATION APPL IA OPER DOES NOT HAVE THE CONDITION DEPENDENCY: SIMP.
A request to process the indicated condition dependency in the current plan failed because the condition dependency does not exist.
The request is rejected.
Specify a valid selection.
EQQM997E
CONDITION COND ON OPERATION APPL IA OPER ALREADY HAS THE CONDITION DEPENDENCY: SIMP.
A request to add the indicated condition dependency in the current plan failed because the condition dependency already exists.
The request is rejected.
Specify a valid selection.
EQQM998E
AN ATTEMPT HAS BEEN MADE TO DEFINE OPERATION APPL IA OPER AS CONDITIONAL PREDECESSOR OF ITSELF.
An operation cannot depend on itself.
The request is rejected.
Specify a valid selection.
EQQM999E
INCONSISTENT DATA IN CONDITION COND ON OPERATION APPL IA OPER. NUMBER OF CONDITION DEPENDENCIES LESS THAN CONDITION SUBSET.
The number specified as condition rule exceeds the number of defined condition dependencies.
The request is rejected.
Specify a valid selection.