EQQC001 - EQQC501
EQQC001I
THE AUTOMATIC RECOVERY SUBTASK HAS STARTED
The automatic job recovery subtask has been successfully initialized.
Automatic job recovery processing is started.
None.
EQQC002E
THE AUTOMATIC RECOVERY INITIALIZATION FAILED
The automatic job recovery subtask was not initialized because there is an error in the AROPTS initialization statement.
Automatic job recovery initialization is terminated.
Correct the error in the AROPTS initialization statement and restart HCL Workload Automation for Z.
Contact your system programmer.
This message is preceded by a message in the HCL Workload Automation for Z message log giving the reason for this error message.
EQQC003I
THE AUTOMATIC RECOVERY SUBTASK HAS ENDED NORMALLY
This message is issued when the HCL Workload Automation for Z subsystem is being stopped by an operator command.
The HCL Workload Automation for Z termination processing continues.
None.
EQQC004E
STARTTIME OR ENDTIME OPTION TIME IN AROPTS STATEMENT IS NOT VALID
The STARTTIME or ENDTIME option in the AROPTS initialization statement is not specified in a valid HCL Workload Automation for Z time format. The option TIME must be a 4-digit decimal number in the format HHMM, where HH is from 00 through 23, and MM is from 00 through 59.
Automatic job recovery initialization is terminated.
Correct the STARTTIME or ENDTIME value in the AROPTS initialization statement. Stop HCL Workload Automation for Z and restart it.
EQQC005E
THE AUTOMATIC RECOVERY INITIALIZATION FAILED, MODULE EQQCASEM NOT FOUND
The initialization of the automatic job recovery subtask failed because the load module EQQCASEM could not be found in a library that can be accessed by HCL Workload Automation for Z.
Automatic job recovery initialization is terminated.
Make sure that the load module EQQCASEM is present in a library that can be accessed by HCL Workload Automation for Z. Stop the HCL Workload Automation for Z started task and restart it.
Contact your system programmer.
EQQC006E
HOUR AND MINUTE MUST BOTH BE TWO-DIGIT NUMBERS
A nonnumeric time value has been specified.
Processing continues.
Reenter a numeric time value.
EQQC007E
AN ABEND OCCURRED IN THE AUTOMATIC RECOVERY SUBTASK, IT IS RESTARTED
An error has caused the automatic job recovery subtask to end abnormally, but it has been able to restart.
Automatic job recovery resumes normal processing, but one or more requests for service may have been rejected.
Collect relevant information about the sequence of events leading to this error. Make sure that the dump data set and the HCL Workload Automation for Z message log are available for inspection. Contact your system administrator.
Inform your system programmer about the error and, if the error can be reproduced, of the sequence of dialog requests leading to the error.
At abend, a dump is written to the SYSxDUMP data set.
EQQC008E
HOUR MUST BE IN THE RANGE 0 TO 23
A time value has been specified where the hour number is not valid.
Processing continues.
Reenter the time value and specify an hour number in the range 0 through 23.
EQQC009E
MINUTE MUST BE IN THE RANGE 0 TO 59
A time value has been specified where the minute number is not valid.
Processing continues.
Reenter the time value and specify a minute number in the range 0 through 59.
EQQC011W
AUTOMATIC RECOVERY REQUEST FAILED, SERVICE INACTIVE
Automatic job recovery requires service from other HCL Workload Automation for Z subtasks. When automatic job recovery was initiated to determine whether or not recovery should be performed for the job that ended in error, the service SERVICE was down (not available).
No recovery attempt is made and the job remains ended in error.
Check why the service SERVICE was down.
Use the ended-in-error list of the Modify Current Plan dialog to decide whether or not a new automatic job recovery attempt should be made for the job that ended in error.
To determine why the service is not available, review the earlier messages in the HCL Workload Automation for Z message log. For job tracking, consider the messages that mention the normal mode manager.
EQQC012W
AUTOMATIC RECOVERY REQUEST FAILED, CANNOT OPEN FILE FILE
Automatic job recovery requires access to HCL Workload Automation for Z VSAM files. Failure to open one of these files prevented automatic job recovery from checking whether or not recovery should be performed for the job that ended in error. FILE is the name of the VSAM file that could not be opened.
No recovery attempt is made and the job remains ended in error.
Check with your system programmer why the file FILE could not be opened.
Use the ended-in-error list of the Modify Current Plan dialog to decide whether or not a new automatic job recovery attempt should be made for the job that ended in error.
To determine why the file cannot be opened, review the earlier messages in the HCL Workload Automation for Z message log.
EQQC013W
AUTOMATIC RECOVERY REQUEST FAILED, CANNOT ALLOCATE BUFFERS
A storage allocation error prevented automatic job recovery from checking whether or not recovery should be performed for the job that ended in error. This message may be followed by message EQQC045I with reason code 50, which identifies the job checked by automatic job recovery.
No recovery attempt is made and the job remains ended in error.
Stop HCL Workload Automation for Z and restart it in a larger region.
Use the ended-in-error list of the Modify Current Plan dialog to decide whether or not a new automatic job recovery attempt should be made for the job that ended in error.
EQQC014W
AUTOMATIC RECOVERY REQUEST FAILED DUE TO I/O ERROR
An I/O error prevented automatic job recovery from determining whether or not recovery should be performed for the job that has ended in error. This message may be followed by message EQQC045I with reason code 50, which identifies the job checked by automatic job recovery.
No recovery attempt is made and the job remains ended in error.
Refer to the associated I?O error message for guidance.
Use the ended-in-error list of the Modify Current Plan dialog to decide whether or not a new automatic job recovery attempt should be made for the job that ended in error.
Review the earlier messages in the HCL Workload Automation for Z message log for a message issued for the I?O error.
EQQC020E
NO AUTOMATIC RECOVERY BECAUSE INVALID CLEAN UP TYPE: CLNTYP FOR OPERATION OPNO IN APPLICATION ADID
An automatic recovery task was executed that has the cleanup type set to the value specified by CLNTYP. However, the only allowed values are None or Immediate.
The automatic recovery is not processed and the cleanup actions are not started
Check if the cleanup type can be changed to Immediate.
EQQC021W
NO AUTOMATIC RECOVERY TEST BECAUSE NO ERROR INFORMATION IN JNT RECORD
When a job fails, error information about the failing operation is saved in the job name table (JNT) record. Automatic job recovery was initiated but could not determine if recovery should be performed for the failed job because no error information was available in the JNT record. This message is followed by message EQQC045I with reason code 50, which identifies the job checked by automatic job recovery.
No recovery attempt is made and the job remains ended in error.
Check the HCL Workload Automation for Z message log for any messages issued at the time that the job ended in error to determine why no JNT record exists.
If any recovery actions by automatic job recovery were required for the job that failed, the actions must be initiated manually. Use the Modify Current Plan dialog to initiate the actions.
If you use automatic job recovery together with the restart and cleanup functions and have defined the RESSTEP parameter of the RECOVER statement, specify STEPEVENTS(ALL) on the EWTROPTS statement. Otherwise automatic job recovery and restart and cleanup are not invoked.
Review the HCL Workload Automation for Z message log for inconsistencies at the time that the job ended in error. Also review the event data set for the completion of the job. Refer to Diagnosis Guide and Reference for the layout of the record in the event data set.
EQQC022I
AUTOMATIC RECOVERY ACTION POSTPONED FOR OPERATION OPNO IN APPLICATION ADID. CLEANUP ACTIONS PENDING. CLEANUP TYPE IS TYPE
When the automatic recovery for this operation was about to start, the scheduler found that cleanup actions were in progress (for a cleanup type set to Immediate) or waiting to be started (for a cleanup type set to Manual).
The automatic recovery is postponed until the cleanup actions are complete. If the cleanup type is Immediate, the cleanup actions are started automatically by the scheduler. If the cleanup type is Manual, the cleanup actions must be requested in a dialog.
None.
EQQC023W
NO AUTOMATIC RECOVERY TEST BECAUSE NO JCL RECORD FOR THE OPERATION
The JCL record could not be read. This prevented automatic job recovery from determining whether or not recovery should be performed for the job that ended in error. This message is followed by message EQQC045I with reason code 50, which identifies the job checked by automatic job recovery.
No recovery attempt is made and the job remains ended in error.
Check the HCL Workload Automation for Z message log for any messages issued at the time that the job ended in error to determine why the JCL record could not be read.
If any recovery actions by automatic job recovery were required for the job that failed, the actions must be initiated manually. Use the Modify Current Plan dialog to initiate the actions.
Review the HCL Workload Automation for Z message log for inconsistencies at the time that the job ended in error.
EQQC024W
NO AUTOMATIC RECOVERY TEST BECAUSE OPERATION RECORD MODIFIED
Automatic job recovery could not determine whether or not recovery should be performed for the job that ended in error because the operation record indicates that the operation no longer has the error status.
No recovery attempt is made for the job that ended in error.
None.
EQQC025W
CLEAN UP ACTION NOT STARTED BECAUSE CP14 RECORD COULD NOT BE READ
An automatic recovery task was executed. The cleanup type was set to Immediate, so it tried to read the job log record in the current plan to start the cleanup actions. However, the record was not found
The recovery attempt stops.
Current plan job log information records (CP14) are created by the Controller or by non z/OS trackers when a job execution is completed. Check the EQQMLOG of the Controller to diagnose the problem.
EQQC026W
NO AUTOMATIC RECOVERY TEST BECAUSE JCL MEMBER IS BEING USED
Automatic job recovery could not determine whether or not recovery should be performed for the job that ended in error, because the member on the JCL repository file (ddname EQQJ1SDS and EQQJS2DS) was being used by another HCL Workload Automation for Z subtask. This message is followed by message EQQC045I with reason code 50, which identifies the job checked by automatic job recovery.
No recovery attempt is made and the job remains ended in error.
When the EQQJSxDS JCL member is free, you can initiate a new automatic job recovery attempt for the job that ended in error by using the ended-in-error list of the Modify Current Plan dialog.
EQQC027W
NO AUTOMATIC RECOVERY BECAUSE PROCLIB MEMBER NOT FOUND
No automatic job recovery could be performed for the job that ended in error because the RECOVER statement that matched the error specifies a procedure library member that could not be found. This message is followed by message EQQC045I with reason code 50, which identifies the job checked by automatic job recovery.
No recovery attempt is made and the job remains ended in error.
Check that the member name is correctly spelled and that it is available in the EQQPRLIB file. When you have found and corrected the error, edit the JCL and insert a % sign in column 4 of the RECOVER line so as to reconvert the line into a RECOVER statement. You can initiate a new automatic job recovery attempt for the job that ended in error by using the ended-in-error list of the Modify Current Plan dialog.
Review the JCL to determine the procedure library member name. The selected RECOVER statement is followed by a comment line that gives the member name.
EQQC028W
NO AUTOMATIC RECOVERY TEST BECAUSE ERROR IN RECOVER STATEMENT
While automatic job recovery was checking whether or not recovery should be performed for a job that ended in error, a RECOVER statement with a syntactical error was found. This message is followed by message EQQC045I with reason code 50, which identifies the job checked by automatic job recovery.
No recovery attempt is made and the job remains ended in error.
Check the RECOVER statements for syntactical errors. Make sure that the operation is separated from the operands by one or more blanks, and that the operands are separated by a comma. When you have found and corrected the error, you can initiate a new automatic job recovery attempt for the job that ended in error by using the ended-in-error list of the Modify Current Plan dialog.
Review the JCL of the identified operation.
EQQC029I
NO AUTOMATIC RECOVERY BECAUSE RECOVER STATEMENT DOES NOT MATCH THIS ERROR
While automatic job recovery was checking whether or not recovery should be performed for a job that ended in error, one or more RECOVER statements were found but none matched the current error. This message is followed by message EQQC045I with reason code 50, which identifies the job checked by automatic job recovery.
No recovery attempt is made and the job remains ended in error.
Consider if the error should be covered in the recovery scheme.
EQQC041W
JOBLOG INFORMATION COULD NOT BE RETRIEVED BECAUSE CP14 RECORD COULD NOT BE READ FOR APPL: ADIDDATE HH.MM, OP WSNOP
An automatic recovery task was executed and an attempt was made to read the job log record in the current plan to start the automatic recovery task actions, however, the record was not. The automatic recovery task was unable to locate the CP14 record in the current plan for the operation that ended in error and that is identified by application ADID DATE HH. MM, operation WSN OP, where DATE HH. MM is the occurrence input arrival time.
The specified automatic recovery actions are not carried out.
Save the message log (EQQMLOG) and contact IBM Software Support.
EQQC044I
AUTO RECOVERY OF APPL ADIDDATE HH.MM, OP WSNOPJNJID
Automatic job recovery actions have been taken for the specified occurrence (application ADID DATE HH. MM, operation WSN OP, where DATE HH. MM is the occurrence input arrival time). The specified JCL rebuild is made. Restart, application addition, and release of successors are in process as specified in the RECOVER statement.
The specified automatic recovery actions are started up.
None.
EQQC045I
AUTO RECOVERY INFO RS, APPL ADIDDATE HH.MM, OP WSNOPJNJID
Automatic job recovery is being performed for the job identified as application ADID DATE HH. MM, operation WSN OP, where DATE HH. MM is the occurrence input arrival time). This message is issued to keep track of a particular action taken during the recovery processing.
RS is a reason code that stands for a certain error or action, or both, related to automatic job recovery. Message EQQC047E has a list of the reason codes and their meanings.
The specified automatic recovery actions are started up.
Look up the meaning of reason code RS in the list given in message EQQC047E. Review the action taken and see if it matches the action requested. If necessary, take the appropriate action.
Review the JCL of the identified operation. Identify the recovery actions described in the RECOVER statement of the JCL.
EQQC046W
AUTO RECOVERY WARNING RS, APPL ADID DATEHH.MM, OP WSNOPJNJID
Automatic job recovery was attempted for the job identified as application ADID DATE HH. MM, operation WSN OP, where DATE HH. MM is the occurrence input arrival time. A problem was encountered that inhibited automatic job recovery.
RS is a reason code that stands for a certain error or action, or both, related to automatic job recovery. Message EQQC047E has a list of the reason codes and their meanings.
The operation is left unchanged by automatic job recovery.
Look up the meaning of reason code RS in the list given in message EQQC047E. Review what recovery actions are taken and see if they match the actions requested in the RECOVER statement. If necessary, use the Modify Current Plan dialog to perform the rest of the recovery actions.
Review the JCL of the identified operation. Identify the recovery actions described in the RECOVER statement of the JCL.
EQQC047E
AUTO RECOVERY ERROR RS, APPL ADIDDATE HH.MM, OP WSNOPJNJID
Automatic job recovery was attempted for the job identified as application ADID DATE HH. MM, operation WSN OP, where DATE HH. MM is the occurrence input arrival time. An error was encountered that inhibited the recovery actions.
RS is a reason code that stands for a certain error or action, or both, related to automatic job recovery (see Problem determination).
The job remains ended in error and the extended status of the operation is set to E. The JCL record on the JCL repository data set might have been updated with information about the error.
Check the RECOVER statements. Comment lines that describe the error in detail are added to the JCL. When you have found and corrected the error, you can use the ended-in-error list of the Modify Current Plan dialog to initiate a new automatic job recovery attempt.
- 1
- Misplaced HCL Workload Automation for Z recover statement.
- 2
- Incorrect parameter.
- 3
- Unbalanced parentheses.
- 4
- Invalid continuation line.
- 5
- Invalid length of parameter value.
- 6
- A parameter appears twice in same recover statement.
- 7
- Invalid return code from exit.
- 8
- Terminate return code from exit.
- 9
- Abandon return code from exit.
- 10
- Invalid restart parameter value. Set Y, YES, N, or NO.
- 11
- Procedure library member not found.
- 12
- I?O error.
- 13
- Unable to load exit routine.
- 14
- No job statement found.
- 15
- Incorrect job statement. Cannot add restart parameter.
- 16
- Invalid specification of generic code.
- 17
- Loop in the case code lists.
- 18
- Checkpoint name contains special characters.
- 19
- Missing stepname.
- 20
- Too many values specified in parameter.
- 21
- Failing OP is outside rerun or successor tree.
- 22
- External successor in rerun tree is not in the failing tree.
- 23
- Inconsistency with AD of failing occurrence (for example, AD no longer exists or is not active).
- 24
- AD of application to add could not be found.
- 25
- Error while using MCP (additional message by MCP).
- 26
- Unable to allocate virtual storage.
- 27
- Error detected and handled by other subtask.
- 28
- Improper naming of steps, give all unique names.
- 29
- Cannot add restart param. because no delimiter last job line.
- 30
- No information about error in job name table (JNT).
- 31
- Failing operation record could not be read.
- 32
- Invalid stepname or no step with that name.
- 33
- More than one step in JS record with the given name.
- 34
- JS data set in use. Recovery test canceled.
- 35
- JS data set member in use. Recovery test canceled.
- 36
- OP record has been changed. Recovery test canceled.
- 37
- Invalid range.
- 38
- No occurrence exists for the specified application.
- 39
- Recovery actions taken.
- 40
- No JS record.
- 41
- Restart step not present in the JCL.
- 42
- Step end entries missing in JNT record (CPLREC04). The error can
relate to:
- Nested procedures
- JCL INCLUDE statements
- JCL IF/THEN/ELSE/ENDIF statement constructs.
- 43
- Parameter not supported when STEPEVENTS(ABEND) specified.
- 44
- RESSTEP=% specified but error not related to a step.
- 45
- A required service function (NMM) has terminated.
- 46
- No free input arrival time for the application to add.
- 47
- Missing value for parameter.
- 48
- Authorization check requires user ID.
- 50
- Adding operation identifiers to message text in EQQMLOG file.
- 51
- Error in ALTWS parameter.
- 52
- Error in ALTJOB parameter.
EQQC048W
AUTO RECOVERY WARNING RS
Automatic job recovery was attempted for the job that ended in error, but was inhibited because of a problem with reason code RS. This message differs from EQQC046W in that automatic job recovery was not able to identify the application to be handled.
No recovery is made and the job remains ended in error.
Look up the meaning of reason code RS in the list given in message EQQC047E. Review what recovery actions are taken and see if they match the actions requested in the RECOVER statement. If necessary, use the Modify Current Plan dialog to perform the rest of the recovery actions.
Message EQQC047E has a list of the reason codes and their meanings. Review the JCL of the identified operation. Identify the recovery actions described in the RECOVER statement of the JCL.
EQQC049E
AUTO RECOVERY ERROR RS
Automatic job recovery was attempted for the job that ended in error, but was inhibited because of an error with reason code RS. This message differs from EQQC047E in that automatic job recovery was not able to identify the application to be handled.
No recovery is made and the job remains ended in error. The extended status of the operation is set to E.
Look up the meaning of reason code RS in the list given in message EQQC047E. Review what recovery actions are taken and see if they match the actions requested in the RECOVER statement. If necessary, use the Modify Current Plan dialog to perform the rest of the recovery actions.
Message EQQC047E has a list of the reason codes and their meanings. The JS record may have been updated with information about the error. Review the JCL of the identified operation. Identify the recovery actions described in the RECOVER statement of the JCL.
EQQC061E
AUTOMATIC RECOVERY FAILED, I/O ERROR
Automatic job recovery failed for the job that ended in error because an I?O error occurred. The I?O error occurred while the automatic job recovery subtask was determining whether recovery should be performed, or while the recovery actions were being activated or implemented.
This message is preceded by a message that describes the I?O error in more detail, and is followed by message EQQC045I with reason code 50, which identifies the job handled by automatic job recovery.
The job remains ended in error. Some of the intended recovery actions may have been started up or completed.
Review the HCL Workload Automation for Z message log for I?O errors that immediately precede this message.
When you have found and corrected the error, you can initiate a new automatic job recovery attempt for the job that ended in error by using the ended-in-error list of the Modify Current Plan dialog. You may have to initiate the recovery actions manually, or you may have to change the RECOVER statement to encompass only the remaining recovery actions.
Review the JCL of the identified operation. Identify the recovery actions described in the RECOVER statement of the JCL.
EQQC062E
AUTOMATIC RECOVERY FAILED, NOT ENOUGH VIRTUAL STORAGE - SIZE
Automatic job recovery failed for the job that ended in error because of insufficient virtual storage. The failure occurred while the automatic job recovery subtask was determining whether recovery should be performed, or while the recovery actions were being activated or implemented. SIZE is the amount of virtual storage requested.
This message is followed by message EQQC045I with reason code 50, which identifies the job checked by automatic job recovery.
The job remains ended in error. Some of the intended recovery actions may have been started up or completed.
Stop HCL Workload Automation for Z and restart it in a larger region.
When you have found and corrected the error, you can initiate a new automatic job recovery attempt for the job that ended in error by using the ended-in-error list of the Modify Current Plan dialog. You may have to initiate the recovery actions manually, or you may have to change the RECOVER statement to encompass only the remaining recovery actions.
Review the JCL of the identified operation. Identify the recovery actions described in the RECOVER statement.
EQQC500E
THE JCL LIBRARY, DDNAME EQQPRLIB, COULD NOT BE OPENED
Automatic job recovery could not open the JCL procedure library (ddname EQQPRLIB) to read a procedure specified in the ADDPROC parameter of the RECOVER statement. This message is followed by message EQQC045I with reason code 50, which identifies the job checked by automatic job recovery.
No recovery attempt is made and the job remains ended in error.
Check that the ddname EQQPRLIB is correctly specified and that the task started by HCL Workload Automation for Z is authorized to open the data set for input. When the error is corrected, stop HCL Workload Automation for Z and restart it.
Contact your system programmer. When your system programmer has fixed the problem, you can initiate a new automatic job recovery attempt for the job that ended in error by using the ended-in-error list of the Modify Current Plan dialog.
Review the earlier messages in the HCL Workload Automation for Z message log for a message describing an I?O error on the EQQPRLIB file.
EQQC501E
LOGICAL RECORD LENGTH FOR THE JCL LIBRARY, DDNAME EQQPRLIB, IS NOT VALID
Automatic job recovery could not read a procedure specified in the ADDPROC parameter of the RECOVER statement because the logical record length is not 80 bytes. This message is followed by message EQQC045I with reason code 50, which identifies the job checked by automatic job recovery.
No recovery attempt is made and the job remains ended in error.
Check that the ddname EQQPRLIB is correctly defined. When the error is corrected, stop HCL Workload Automation for Z and restart it.
Contact your system programmer. When your system programmer has fixed the problem, you can initiate a new automatic job recovery attempt for the job that ended in error by using the ended-in-error list of the Modify Current Plan dialog.
Check the definition of the ddname EQQPRLIB.