EQQ0014 - EQQ9986
EQQ0014E
DBCS FORMAT SPECIFIED BUT ADID NOT VALID BRACKETED DBCS: NAME
The application ID NAME is specified to be in DBCS format, that is, it must start with a shift-out character (X'0E') and end with a shift-in character (X'0F'). Either the shift-out or the shift-in character, or both, are missing.
Processing is terminated.
Correct the error and resubmit the job.
EQQ0015W
DBCS FORMAT SPECIFIED BUT INPUT NOT VALID BRACKETED DBCS: NAME
The application ID NAME is specified to be in DBCS format, that is, it must start with a shift-out character (X'0E') and end with a shift-in character (X'0F'). Either the shift-out or the shift-in character, or both, are missing.
The failing operator instruction is rejected.
Correct the error and resubmit the job or use the HCL Workload Automation for Z panel to submit the job.
EQQ0016E
ITEM TOO SHORT: NAME
The application ID NAME has an invalid syntax.
If the error is detected during batch processing of operator instructions, the failing instruction is rejected. If the error is detected during long-term planning, the job is terminated.
Correct the error and resubmit the job or use the HCL Workload Automation for Z panel to submit the job.
EQQ0017E
FIRST CHARACTER NOT ALPHABETIC IN NAME: NAME
The application ID NAME has an invalid syntax. The first character in NAME must be an alphabetic character.
If the error is detected during batch processing of operator instructions, the failing instruction is rejected. If the error is detected during long-term planning, the job is terminated.
Correct the error and resubmit the job or use the HCL Workload Automation for Z panel to submit the job.
EQQ0018E
INVALID ALPHABETIC CHARACTER : NAME
The character displayed in the message is not a valid alphabetic character.
If the error is detected during batch processing of operator instructions, the failing instruction is rejected. If the error is detected during long-term planning, the job is terminated.
Correct the error and resubmit the job or use the HCL Workload Automation for Z panel to submit the job.
EQQ0019W
INVALID NUMERIC : NUMBERIN SEQ FILE
When processing sequential operator instruction files, an invalid digit appears in NUMBER.
The failing operator instruction is rejected and correct instructions are accepted.
Correct the error and resubmit the job or use the HCL Workload Automation for Z panel to submit the job.
EQQ0020E
INVALID YEAR IN DATE : DATE
The value for year in the SYSIN statement of the batch program is incorrect. Year must be a number in the range 00 to 99.
The job is terminated.
Correct the year and resubmit the job or use the HCL Workload Automation for Z panel to submit the job.
EQQ0021E
INVALID MONTH IN DATE : DATE
The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel. The month is invalid in DATE.
The job is terminated.
Correct the error and resubmit the job or use the HCL Workload Automation for Z panel to submit the job.
EQQ0022E
INVALID DAY IN DATE : DATE
The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel. The day is invalid in DATE.
The job is terminated.
Correct the error and resubmit the job or use the HCL Workload Automation for Z panel to submit the job.
EQQ0023E
INVALID HOUR IN TIME : TIME
The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel. The hour is invalid in TIME.
The job is terminated.
Correct the error and resubmit the job or use the HCL Workload Automation for Z panel to submit the job.
EQQ0024E
INVALID MINUTE IN TIME : TIME
The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel. The minute is invalid in TIME.
The job is terminated.
Correct the error and resubmit the job or use the HCL Workload Automation for Z panel to submit the job.
EQQ0025E
VALID RANGE FOR TIME IS 00.00 - 24.00 : TIME
The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel. The time specified is outside the valid range for time.
The job is terminated.
Correct the error and resubmit the job or use the HCL Workload Automation for Z panel to submit the job.
EQQ0026E
VALID RANGE FOR DURATION IS 00.00 - 99.59 : EXTVAL
The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel.
The job is terminated.
Correct the error and resubmit the job or use the HCL Workload Automation for Z panel to submit the job.
EQQ0027I
INCORRECT ARGUMENT VALUE IN PIF REQUEST: VAL
- hh
- A number in the range 00–24
- mm
- A number in the range 00–59
- hhmm
- A number not greater than 2400
If the time argument includes a comparative operator (>, <, ¬), processing continues.
Check all time values in your PIF application, correct, and rerun if necessary.
EQQ0100E
APPLICATION DESCRIPTION DATA SET IN USE, TRY LATER
You have attempted to access the application description data set, but it is being used by another user.
The job is terminated.
Try again later.
EQQ0105W
APPLICATION DESCRIPTION ADID NOT FOUND
You have attempted to read the application description ADID, but this application description ID does not exist in the application description database.
The job continues processing.
Enter an existing application description ID or use the Application Description panel to create a new application description, and resubmit the job. If the message was issued from a batch job, create the application description, and resubmit the job.
EQQ0170W
APPL: APPL- VALIDATION FAILED. REASON REASON, POSITION POSITION
During mass update of the application description database, the changes that were made have caused application description APPL to become invalid. REASON indicates the reason why validation of the application description failed. and POSITION indicates the failing position in hexadecimal form within the record.
APPL is not updated. The job continues with the next application description.
Analyze the reason for the error. (See Reason codes for a list of the reason codes and their meanings.) If necessary, use the Application Description panel to correct the application description.
EQQ0172W
APPL: APPL- PREDECESSOR OPID NOT FOUND
The internal predecessor OPID could not be found for the application description APPL.
The application description APPL is not activated. The daily planning program continues processing, but without planning this application. The job continues processing, but without planning this application.
Use the Application Description panel to check and correct the dependencies between operations.
EQQ0175W
APPL: APPL- OPERATION OPID IS ISOLATED FROM OTHER OPS IN NET
There is more than one network. This is not allowed.
The application description APPL is not activated. The daily planning program continues processing, but without planning this application. The job continues processing, but without planning this application.
Use the Application Description panel to check and correct the dependencies between operations.
EQQ0176W
APPL: APPL- OPERATION OPID IS INVOLVED IN A DEPENDENCY LOOP
There is a dependency loop in the network. This message is issued for all operations involved in the dependency loop and for all operations preceding the loop.
The application description APPL is not activated. The daily planning program continues processing, but without planning this application. The job continues processing, but without planning this application.
Use the Application Description panel to check and correct the dependencies between operations.
EQQ0183W
APPL: APPL- PREP OP OPID HAS NO SUCCEEDING CPU OP
You have specified an operation at a workstation that uses the job setup function, but the operation OPID does not have an immediately succeeding processor operation with the same job name.
The application description APPL is not activated. The daily planning program continues processing, but without planning this application.
Use the Application Description panel to check and correct the dependencies between operations.
EQQ0196E
ERRORS ENCOUNTERED WHILE SORTING
Errors were encountered from the sort program.
The job is terminated.
Check the sort program messages to determine the cause of the error. Correct the errors and resubmit the job.
Contact your system programmer.
EQQ0300E
LTP DATA SET IN USE - TRY LATER
The long-term plan data set is being used by another HCL Workload Automation for Z function.
The job is terminated.
Try again later.
EQQ0301E
PERIOD START SDATESTIME>= PERIOD END EDATEETIME
The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel. The end of the planning period must be later than the start of the period.
The daily planning program is terminated.
Correct the error and resubmit the job or use the HCL Workload Automation for Z panel to submit the job.
EQQ0302E
PERIOD SDATESTIME- EDATE ETIME OUTSIDE LONG TERM PLAN
The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel. The planning period SDATESTIME- EDATEETIME is outside the current range of the long-term plan.
The daily planning program is terminated.
Correct the error and resubmit the job or use the HCL Workload Automation for Z panel to submit the job.
EQQ0303E
SPECIFIED PARAMETER FIELD TOO SHORT
The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel. The parameter field is shorter than the required length.
The job is terminated.
Correct the error and resubmit the job, or use the HCL Workload Automation for Z panel to submit the job.
EQQ0304E
OLD CP MIGHT BE WRONG, CP BACKUP DID NOT COMPLETE NORMALLY
The last backup of the active current plan to the backup current plan failed. The current plan input to daily planning could therefore be incomplete or out-of-date.
The daily plan batch process terminates.
If there is no error indication in the controller message log, make sure that the daily planning job is executed on the same z/OS system where the controller is started or on an z/OS system in the same GRS ring. In the BATCHOPT statement, use the CHECKSUBSYS parameter to ensure that the batch job is not started unless it can communicate with the controller via an ENQ lock. If an error has caused the controller to terminate before completing the backup process, solve that error and restart the controller before attempting to rerun the failed daily planning processing.
The following solution should be used only if the controller cannot be restarted successfully. When the daily planning job is submitted with CHECKSUBSYS(NO) specified in the BATCHOPT statement, the validity check causing this message is bypassed. The active current plan is used as input to daily planning instead of the backup plan. Make sure that the value for CHECKSUBSYS is reset to YES when the daily planning job completes.
Review the controller message log (EQQMLOG), to determine why the current plan backup process failed. If the HCL Workload Automation for Z backup process failed due to an open error, the reason could be that another job was using the file.
EQQ0305W
PRE OP TO OPERATION IN APPL APPL NOT FOUND
An external predecessor to the operation OPERATION for the application description APPL does not exist in the application description database.
The dependency is ignored. The daily planning program continues processing.
Use the Application Description and the Long-Term Planning panels to verify and correct the dependencies.
EQQ0306W
WORKSTATION WS IN OPERATION OPERATION IS UNDEFINED
An operation (OPERATION) is defined for a workstation (WS) that does not exist.
The daily planning program continues processing, but without planning this application.
Use the Application Description panel to verify and correct the operations or use the Workstation Description panel to add the workstation description to the workstation description database.
EQQ0307W
APPL APPL TOO OLD - NOT IN CURRENT PLAN
An occurrence in the long-term plan data set or an undecided occurrence in the old current plan data set, which has a deadline previous to the latest backup time, is assumed to be completed.
The occurrence is marked completed in the long-term plan data set except in the trial plans. The daily planning program continues processing.
If the occurrence should be included in the current plan, use the Modify Current Plan panel to add the occurrence.
EQQ0310E
SUBSYSTEM SUBSYS NOT ACTIVE OR NOT REACHED
The BATCHOPT statement specifies that the daily plan is to be produced for an active subsystem defined by the parameter CHECKSUBSYS. However the subsystem cannot be reached by the daily planning program.
The daily planning program is terminated.
Check that the correct subsystem name is specified in the parameter SUBSYS of the BATCHOPT statement.
If the subsystem is stopped, the daily planning program can be executed after specifying CHECKSUBSYS(NO) in the BATCHOPT statement.
If the subsystem is active, make sure that the daily planning program is executed either on the same processor or on a processor connected via GRS to the processor where the subsystem is executing.
If CHECKSUBSYS(NO) is specified, ensure the parameter is reset before starting the next daily plan for an active subsystem.
EQQ0311E
DAILY PLAN PERIOD START DAY AND TIME MUST BE SPECIFIED
When no current plan exists, you must specify the period start date and time.
The daily planning program is terminated.
Enter start date and time.
EQQ0312E
PERIOD LENGTH IS GREATER THAN 21 DAYS
A daily plan period must not extend beyond 21 days. Either the SYSIN parameters were specified outside the HCL Workload Automation for Z panel or an extension length was specified in work days, and calculated elapsed time exceeds 21 days.
The daily planning program is terminated.
Use the Daily Planning panel to correct the parameters or to reduce the extension length, or use the HCL Workload Automation for Z panel to submit the job.
EQQ0313E
NO CURRENT PLAN EXISTS
Daily planning requires an old current plan data set as input, but that data set does not exist.
The daily planning program is terminated.
Extend the current plan period before using any daily planning function that requires an old current plan as input.
EQQ0314E
WRONG OLD CURRENT PLAN SELECTED AS INPUT
The old current plan data set used as input when extending or replanning the current plan period is not the correct data set. The data set may have been restored from a backup copy.
The daily planning program is terminated.
Make sure that the daily planning batch JCL is referring to the same current plan and long-term plan data sets as the controller subsystem. If you have restored the current plan incorrectly, set the CURRPLAN(NEW) parameter in the JTOPTS statement and restart the controller to restore the current plan from the new current plan data set.
Refer to Customization and Tuning for information about restoring HCL Workload Automation for Z data sets. Resubmit the daily planning batch job when the error has been corrected.
EQQ0315E
WORK STATION WSN DOES NOT EXIST
The workstation WSN, which has work planned for it in the current plan, has been deleted from the workstation description database.
The daily planning program is terminated.
Use the Workstation Description panel to create the workstation description. Use the Daily Planning panel to resubmit the job.
EQQ0316E
WORK STATION WSN TYPE HAS BEEN CHANGED
The workstation WSN type in the workstation description database has been changed for a workstation that is part of the current plan.
The daily planning program is terminated.
Use the Workstation Description panel to change the workstation type to its previous value. Use the Daily Planning panel to resubmit the job.
EQQ0317W
APPLICATION APPL DOES NOT EXIST
An application occurrence has been read in the long-term plan data set, but there is no valid application description.
The application is not included in the daily plan and the application occurrence is marked deleted in the long-term plan data set. The daily planning program continues processing.
Use the Application Description panel to create the application description or to change the validation period. Use the Modify Current Plan panel to add the application occurrence to the current plan.
EQQ0318E
PERIOD START SDATESTIME CANNOT BE CHANGED
The period start date and time cannot be changed when extending the current plan period.
The daily planning program is terminated.
Use the Daily Planning panel to get the correct start period value and resubmit the job.
EQQ0319E
WRONG LTP DATA SET SELECTED AS INPUT
The long-term plan data set used as input when extending or replanning the current plan period is not the correct data set. The data set may have been restored from a backup copy.
The daily planning program is terminated.
Make sure that the daily planning batch JCL is referring to the same current plan and long-term plan data sets as the controller subsystem. If you have restored the long-term plan incorrectly, restore it from the EQQLTBKP data set.
Refer to Customization and Tuning for information about restoring HCL Workload Automation for Z data sets. Resubmit the daily planning batch job when the error has been corrected.
EQQ0320E
THE STATUS RECORD CONTAINS INCORRECT VALUES
The status record (in the checkpoint data set) does not contain the value that the daily planning program expects when the backup completion signal is received. The data set may have been restored from a backup copy.
The daily planning program is terminated.
Resubmit the daily planning program.
EQQ0321W
START DATE/TIME ENTERED IGNORED. CURRENT PLAN END DATE/TIME IS USED
A start date and time was entered when running a trial extend of the current plan. The start date and time is ignored and replaced by the current plan end date and time.
The trial daily planning program continues processing.
None.
EQQ0322E
NO WS OPEN TIMES FOR PERIOD ******** **.** - ******** **.**
All workstations are closed during the period START– END.
The daily planning program is terminated.
Use the Workstation Description panel or the Calendar panel to update the open intervals.
EQQ0323W
WS ACTIVITY REPORT OPTION MUST BE 0 OR 1 - SET TO 1
The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel.
- 0
- For workstation activity report not required
- 1
- For workstation activity report required.
The value is set to 1 and the daily planning program continues processing.
Change the parameter value for the workstation activity report option to 0 or 1 in the SYSIN statement for the daily planning program.
EQQ0324W
DAILY OP PLAN REPORT OPTION MUST BE 0 OR 1 - SET TO 1
The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel.
- 0
- For daily operating plan report not required
- 1
- For daily operating plan report required.
The value is set to 1 and the daily planning program continues processing.
Change the parameter value for the daily operating plan report option to 0 or 1 in the SYSIN statement for the daily planning program.
EQQ0325W
ALL WS PLAN REPORT OPTION MUST BE 0 OR 1 - SET TO 1
The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel.
- 0
- For all workstation plan report not required
- 1
- For all workstation plan report required.
The value is set to 1 and the daily planning program continues processing.
Change the parameter value for the all workstation plan report option to 0 or 1 in the SYSIN statement for the daily planning program.
EQQ0326W
INPUT ARR LIST REPORT OPTION MUST BE 0 OR 1 - SET TO 1
The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel.
- 0
- For input arrival list report not required
- 1
- For input arrival list report required.
The value is set to 1 and the daily planning program continues processing.
Change the parameter value for the input arrival list report option to 0 or 1 in the SYSIN statement for the daily planning program.
EQQ0327W
NON-REP WS PLAN REPORT OPTION MUST BE 0 OR 1 - SET TO 1
The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel.
- 0
- For nonreporting workstation plan report not required
- 1
- For nonreporting workstation plan report required.
The value is set to 1 and the daily planning program continues processing.
Change the parameter value for the non-reporting workstation plan report option to 0 or 1 in the SYSIN statement for the daily planning program.
EQQ0328W
CURRENT PLAN REPORT OPTION MUST BE 0 OR 1 - SET TO 1
The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel.
- 0
- For current plan reports not required
- 1
- For current plan reports required.
The value is set to 1 and the daily planning program continues processing.
Change the parameter value for the current plan report option to 0 or 1 in the SYSIN statement for the daily planning program.
EQQ0329E
A NEW CURRENT PLAN ALREADY EXISTS
This message is issued by one of the DP batch programs (print, trial, extend, or replan) when a previous DP batch program (that is, an extend or replan) has created a new current plan (message EQQ3105I A NEW NCP WAS CREATED was logged), but the controller has not completed processing the plan.
The daily planning program is terminated.
No action if the DP batch program was submitted by mistake.
- EQQN051I
- A current plan backup process has started. Trigger was: DP END
- EQQN090I
- The job tracking log data set defined by DDNAME EQQJTXX has been copied to the job tracking log archive data set and then resubmit the job which failed.
If the DP batch program was submitted intentionally and the controller was down, start the controller and wait until either message EQQN051I or EQQN090I is issued in the EQQMLOG. Then resubmit the DP batch program that failed.
EQQ0330W
PLANNED RESOURCE UTILIZATION REPORT OPTION MUST BE 0 OR 1 - SET TO 1
The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel.
- 0
- For planned resource utilization report not required
- 1
- For planned resource utilization report required
The value is set to 1 and the daily planning program continues processing.
Change the parameter value for the planned resource utilization report option to 0 or 1 in the SYSIN statement for the daily planning program.
EQQ0331W
ACTUAL RESOURCE UTILIZATION REPORT OPTION MUST BE 0 OR 1 - SET TO 1
The batch program has an incorrect SYSIN statement, most likely because the batch program was not submitted using the panel.
- 0
- For actual resource utilization report not required
- 1
- For actual resource utilization report required
The value is set to 1 and the daily planning program continues processing.
Change the parameter value for the actual resource utilization report option to 0 or 1 in the SYSIN statement for the daily planning program.
EQQ0332W
NO DEP IN **************** ******** **.**, **************** ******** **.**
No external dependency has been found between operations in the occurrences OCCURRENCE and OCCURRENCE as defined in the application description database and in the default rules. This message is followed by message EQQ0333W or EQQ0334W.
The two specified occurrences are planned without dependencies.
Use the Application Description panel to verify and correct the dependency or use the Modify Current Plan panel to add the dependency to the current plan, or use both panels.
EQQ0333W
NO DEFAULT SUCC OP FOUND IN APPL APPL
No default successor operation, as defined in the installation options, has been found for the application APPL.
The daily planning program continues processing.
If a dependency is required, try to change the default successor operation in the installation option.
Use the Application Description panel to verify and correct the dependency or use the Modify Current Plan panel to add the dependency to the current plan, or use both panels. Or, contact your system programmer.
EQQ0334W
NO DEFAULT PRED OP FOUND IN APPL APPL
No default predecessor operation, as defined in the installation options, has been found for the application APPL.
The daily planning program continues processing.
If a dependency is required, try to change the default predecessor operation in the installation option.
Use the Application Description panel to verify and correct the dependency or use the Modify Current Plan panel to add the dependency to the current plan, or use both panels. Or, contact your system programmer.
EQQ0335W
AUTO WS VERIFICATION FAILED FOR APPL APPL
The rules for automatic workstations were not satisfied for the application APPL. This message is always issued together with one of the messages EQQ0337W through EQQ0341W.
The application in the long-term plan data set
is marked deleted
when the current plan period is extended.
The application is not included in the new current plan or in the
printed plans. The daily planning program continues processing.
See the message issued together with this message for the required action.
EQQ0336W
OP ** IN **************** ****** **** DEFINES OP ** IN **************** ****** **** AS PRED USING WRONG WS NAME
An operation uses the wrong workstation name when defining an operation that belongs to another application as its predecessor.
The dependency is created to the correct workstation. The daily planning program continues processing.
Use the Application Description panel to correct the predecessor definition.
EQQ0337W
NOT THE SAME JOB NAME IN OP ******** AND ********
An operation at an automatic printer workstation and an operation at an automatic computer workstation do not have the same job name.
The application in the long-term plan data set
is marked deleted
when the current plan period is extended.
The application is not included in the new current plan or in the
printed plans. The daily planning program continues processing.
Use the Application Description panel to update the application description on the application description database. Use the Modify Current Plan panel to add the application description to the current plan.
EQQ0338W
PRED OP ******** TO PRINT OP ******** NOT ON A CPU WS
An automatic printer workstation operation has a predecessor on a workstation that is not an automatic computer workstation. This is not allowed.
The application in the long-term plan data set
is marked deleted
when the current plan period is extended.
The application is not included in the new current plan or in the
printed plans. The daily planning program continues processing.
Use the Application Description panel to update the application description on the application description database. Use the Modify Current Plan panel to add the application description to the current plan.
EQQ0339W
OP ******** IS NOT AN INT PRED TO PRINT OP ********
An automatic printer workstation operation must not have an external predecessor operation.
The application in the long-term plan data set
is marked deleted
when the current plan period is extended.
The application is not included in the new current plan or in the
printed plans. The daily planning program continues processing.
Use the Application Description panel to update the application description on the application description database. Use the Modify Current Plan panel to add the application description to the current plan.
EQQ0340W
PRINT OP ******** HAS NO PREDECESSORS
An automatic printer workstation operation has no predecessors.
The application in the long-term plan data set
is marked deleted
when the current plan period is extended.
The application is not included in the new current plan or in the
printed plans. The daily planning program continues processing.
Use the Application Description panel to update the application description on the application description database. Use the Modify Current Plan panel to add the application description to the current plan.
EQQ0341W
PRINT OP ******** HAS MORE THAN ONE PREDECESSOR
An automatic printer workstation operation has more than one internal predecessor. This is not allowed.
The application in the long-term plan data set
is marked deleted
when the current plan period is extended.
The application is not included in the new current plan or in the
printed plans. The daily planning program continues processing.
Use the Application Description panel to update the application description on the application description database. Use the Modify Current Plan panel to add the application description to the current plan.
EQQ0342W
JOBNAME SHOULD BE GIVEN FOR PREP OP ********
An operation on a workstation using the HCL Workload Automation for Z job setup facility must have a job name to combine it with a computer operation in the same application.
This application cannot be used in job tracking and is not added to the current plan.
Use the Application Description panel to update the application description on the application description database. Use the Modify Current Plan panel to add the application description to the current plan.
EQQ0343W
PREP OP ******** HAS JOBNAME ********.NO SUCC CPU OP HAS IT
An operation on a workstation using the HCL Workload Automation for Z job setup facility must have a job name to combine it with a computer operation in the same application. A preparation (job setup) operation is found, but no corresponding computer operation immediately succeeding it is found.
This application cannot be used in job tracking and is not added to the current plan.
Use the Application Description panel to update the application description on the application description database. Use the Modify Current Plan panel to add the application description to the current plan.
EQQ0344E
INVALID TRIAL TYPE
- N
- For Extending Current Plan Period - Trial
- C
- For Replanning Current Plan Period -Trial
- F
- For Producing Daily Plan -Trial.
The daily planning program is terminated.
Change the parameter value for the trial type in the SYSIN statement of the daily planning program.
EQQ0345W
PREP VERIFICATION FAILED FOR APPL APPL
An operation on a workstation using the HCL Workload Automation for Z job setup facility must have a job name to combine it with a computer operation in the same application. The computer operation must be an immediate successor to the preparation (job setup) operation.
This application cannot be used in job tracking and is not added to the current plan.
Use the Application Description panel to update the application description on the application description database. Use the Modify Current Plan panel to add the application description to the current plan.
EQQ0346W
DEPENDENCY **************** ***, FROM **************** ****** **** *** IS LEFT UNRESOLVED, BEFORE PLAN START
A dependency could not be resolved because the predecessor occurrence is not in the current plan.
The occurrence is scheduled without considering the unresolved dependency.
Check the unresolved occurrence. If necessary, add a predecessor occurrence to the current plan.
EQQ0347E
PERIOD START SDATESTIME EARLIER THAN CURRENT PLAN END
When producing a trial daily plan extension, the period start time must be equal to the current plan end.
The daily planning program is terminated.
Change the parameter value for the trial type in the SYSIN statement for the daily planning program. Use the Daily Planning panel to get the current value for period start on the Producing Trial Daily Plan panel.
EQQ0348I
APPL APPL ASSUMES FOLLOWING PRED COMPL
When producing a trial daily plan extension, all predecessor applications with the input arrival time earlier than the period start time are assumed to be completed. This message is followed by EQQ0349I.
The daily planning program continues processing.
EQQ0349I
APPL APPL COMPLETED
The application is assumed to be completed. See also message EQQ0348I.
The daily planning program continues processing.
EQQ0350E
PERIOD START LATER THAN LAST BACKUP TIME
Reporting can only be requested for time periods less recent than the last old current plan. The old current plan is a backup copy of the current plan and is updated either after every certain number of events (specified at installation time) or during daily planning.
The daily planning program is terminated.
Change the parameter value for the trial type in the SYSIN statement for the daily planning program. Use the Daily Planning panel to get the current value for period start on the Producing Trial Daily Plan panel.
EQQ0351W
PERIOD END LATER THAN ******** **.** LAST BACKUP TIME
Reporting can only be requested for time periods less recent than the last old current plan. The old current plan is a backup copy of the current plan and is updated either after every certain number of events (specified at installation time) or during daily planning.
The daily planning program is terminated.
Change the parameter value for the trial type in the SYSIN statement for the daily planning program. Use the Daily Planning panel to get the current value for period end on the Producing Trial Daily Plan panel.
EQQ0352W
NO DEP IN ******** **************** **.** FOR ******** **************** **.**
- Is already completed or deleted
- No longer exists
- Has the corresponding successor dependency marked as
deleted
.
The daily planning program prints a dump of the
erroneous long-term plan file records on the EQQDUMP file, issues
an error message, marks the dependency on the long-term plan file
as completed
, and continues processing.
Collect the dump, the error message, and other relevant information for this occurrence. Contact the Software Support.
Document the prior actions concerning the involved occurrences and contact your system programmer.
EQQ0353I
APPL APPL NOT IN SUMMARY OF COMPL APPL
The application had an invalid completion date and could not be added to the summary table of completed applications (maximum 28 days). The reason may be an incorrect day given at IPL of the system.
The daily planning program continues processing.
None.
EQQ0354W
NUMBER OF OPEN INTERVALS EXCEEDS MAXIMUM FOR WORKSTATION WS PLANNING MAY BE AFFECTED
The current plan record is larger than 32 KB (kilobytes).
The daily planning program continues processing, and ignores the extra open intervals.
Use the Work Station Description panel to decrease the number of open intervals.
EQQ0355W
PREDECESSOR ******** **************** **.** FOR ******** **************** **.** MISSING
A predecessor could not be found as expected. It is probably caused by an error in the long-term plan (LTP) or the current plan (OCP), or both.
The job continues
Collect documentation and contact the Software Support. The following documentation is required: long-term plan, current plan, job-tracking logs. Both the long-term plan and the current plan should reflect the status BEFORE the job was run during which the message was issued.
Check the flagged occurrences and contact your system programmer.
EQQ0356E
VIRTUAL FLAG CHANGED FOR WORKSTATION WSN.
A workstation was deleted from the database EQQWSDS and then redefined with the same name but with a different value for the VIRTUAL flag. The workstation results as incorrectly defined.
DP batch ends in error with return code 12.
Delete and redefine the workstation with the same value for the VIRTUAL flag as the one present in the current plan.
EQQ0357W
WORKSTATION WSN DESTINATION DEST HAS BEEN REMOVED FROM DATA BASE BUT STILL USED IN PLAN.
The destination has been removed from the database EQQWSDS but the current plan still contained some started operations for this destination when the DP batch was run. At the next DP extend or re-plan, if no started operation is still present for this destination, it will be deleted from the current plan.
The DP batch run continues.
None.
EQQ0358E
NO WSO CHAIN HAS BEEN BUILT FOR VIRTUAL WORKSTATION ****
An internal error on the open interval merge occurred. Open intervals have not been correctly calculated for a virtual workstation.
DP batch ends in error with return code 12.
Contact the Software Support.
EQQ0359W
COND DEP **************** ***, FROM **************** ****** **** *** IS LEFT UNRESOLVED, BEFORE PLAN START.
A conditional dependency could not be resolved because the predecessor occurrence is not in the current plan.
The occurrence is scheduled without considering the unresolved dependency.
Check the unresolved occurrence. If necessary, add a predecessor occurrence to the current plan.
EQQ0370W
THE POTENTIAL PREDECESSOR RECORD FOR APPLICATION APPL COULD NOT BE UPDATED. THE MAXIMUM NUMBER (3000) OF POTENTIAL SUCCESSOR OPERATIONS HAS BEEN REACHED SUCC.
The daily planning program was unable to add any more successor operation entries to a potential predecessor record. Since the record could not be updated as intended, it 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 not possible to add all possible successor dependencies automatically.
The daily planning program continues normal processing.
Use the Modify Current Plan panel to add new occurrences of the application defined by this message, making sure that you 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.
EQQ0371I
FTA OR Z-CENTRIC AGENT INFO HAS BEEN CHANGED FOR WORKSTATION WSNAME.
DP batch informs that the new plan contains the workstation WSNAME updated accordingly with the changes that were applied to the definition of the fault-tolerant or z-centric agent, in the workstation database.
DP batch continues normal processing and the plan is created.
None.
EQQ0372W
STATUS OF OPERATION ADID IA OPNO HAS BEEN CHANGED FROM STARTED TO INTERRUPTED AS A CONSEQUENCE OF WORKSTATION WSNAME CHANGE.
As a consequence of the change described by message EQQ0372I, the indicated operation, which had status S, has been interrupted by DP batch and its status set to I.
DP batch continues processing and the plan is created.
Manually restart the interrupted operation.
EQQ0386I
APPL **************** ******** **.** OP ******** WILL MISS DEADLINE
The plan indicates that the operation specified in the message cannot meet its deadline. Possible reasons for this could be: insufficient workstation resources, priority too low, and late predecessors.
HCL Workload Automation for Z plans the operation so that it is completed as close to the deadline as possible.
If it is not acceptable that the operation be late, identify and modify the factor that is causing the delay.
EQQ0387I
APPL APPL WILL MISS APPL DEADLINE
The plan indicates that the operation specified in the message cannot meet its deadline. Possible reasons for this could be: insufficient workstation resources, priority too low, and late predecessors.
HCL Workload Automation for Z plans the operation so that it is completed as close to the deadline as possible.
If it is not acceptable that the application be late, identify and modify the factor that is causing the delay.
EQQ0388I
APPL **************** ******** **.** OP ******** START> TAIL END
The operation specified in this message cannot be planned to start until after the end of period. Possible reasons for this could be: insufficient workstation resources or special resources, priority too low, and late predecessors.
The operation is planned to start at the end of period.
Check the flagged operations and successors. If unacceptable, extend the planning period or alter the resource levels.
EQQ0389I
APPL **************** ******** **.** OP ******** END> TAIL END
The operation specified in this message cannot be planned to start until after the end of period. Possible reasons for this could be: insufficient workstation resources, priority too low, and late predecessors.
The operation is given an end time equal to the tail end time plus the operation duration. Potential delays due to resource limitations are not considered.
Check the flagged operations and successors. If unacceptable, extend the planning period or alter the resource levels.
EQQ0390E
TURNOVER ALREADY IN PROGRESS. BATCH CANNOT BE STARTED.
The controller is still handling a turnover process or waiting for end-to-end synchronization. In this condition a new batch cannot be started.
Processing is terminated.
Retry later to start a new batch, after the batch that probably is still running has ended or the Controller turnover process has been completed.
EQQ0391W
REMOTE JOB INFORMATION FOR APPL **************** OP *** IS MISSING
An operation defined on a remote engine workstation has not remote job information specified.
The application is not added to the plan and the daily plan processing continues.
Use the Application Description panel to verify and correct the operation.
EQQ0392W
REMOTE JOB INFORMATION FOR APPL **************** OP *** IS INCOMPLETE
An operation is defined on a remote engine workstation, but the remote job information is incomplete.
The daily planning program continues processing, but without adding this application to the plan.
Use the Application Description panel to verify and correct the operation.
EQQ0393I
MISSING DEPENDENCY FOR **************** ******** **.** OP ********
The operation occurrence has an internal or external predecessor (or successor) that does not have as its successor (or predecessor) this operation occurrence. This message is issued together with message EQQ0394I, which provides information about the predecessor (or successor).
No new current plan is produced.
If you cannot find a valid reason for the error, contact the Software Support.
Use the Long-Term Planning panel to check the involved dependencies.
EQQ0394I
MISSING DEPENDENCY IN **************** ******** **.** OP ********
The operation occurrence has an internal or external successor (or predecessor), but does not see this dependency. This message is issued together with message EQQ0393I, which provides information about the successor (or predecessor).
No new current plan is produced.
If you cannot find a valid reason for the error, contact the Software Support.
Use the Long-Term Planning panel to check the involved dependencies.
EQQ0395W
SYSTEM AUTOMATION DATA FOR APPL **************** OP *** IGNORED
The operation occurrence has system automation information defined in the application. The information is ignored, because the workstation is not Automation.
The system automation information is ignored and the action continues.
Ensure that you are using the correct workstation for the application and operation indicated in the message.
EQQ0396W
REMOTE JOB INFORMATION FOR APPL **************** OP *** IS IGNORED
The operation occurrence has remote job information defined in the application.
The remote job information is ignored, because the workstation type is not remote engine.
The remote job information is ignored and the daily plan processing continues.
Ensure that you are using the correct workstation for the application and operation indicated in the message.
EQQ0397E
REMOTE ENGINE TYPE WAS CHANGED FOR WORKSTATION WSN.
The remote engine type of the workstation WSN, already present in the plan, was changed.
The daily plan batch program failed.
EQQ0398E
UNSUCCESSFUL PUT SYNAD1
An error occurred while writing to an intermediate work file or the track log file used by daily planning. The SYNAD routine extracted the following information: job name, stepname, unit address, device type, ddname, operation, error description, phys-DA, and access method.
The daily planning program is terminated. A new current plan and reports may have been produced.
If no new current plan was produced, correct the error and resubmit the job. If a new current plan was produced but not the reports, correct the error and use the Replanning Current Plan Period panel to produce the reports.
The SYNAD routine collects information such as jobname, stepname, unit address, device type, ddname, operation, error description, and access method. The SYNADAF macro is used to extract this information. For a detailed description of the layout refer to the appropriate documentation for the MVS/DFP product installed on this system.
EQQ0399I
SYNAD2
This message is a continuation of message EQQ0398E.
The daily planning program is terminated. A new current plan and reports may have been produced.
If no new current plan was produced, correct the error and resubmit the job. If a new current plan was produced but not the reports, correct the error and use the Replanning Current Plan Period panel to produce the reports.
EQQ0401E
INVALID DATES GENERATED FOR APPLICATION ADID RULE RULE
The long-term plan batch programs encountered invalid dates when trying to generate occurrence run dates for a rule-based run cycle. Most likely, this is an internal processing error.
If the run cycle is based on a regular rule, dates after the failure point are missing. If it is based on an exclusion rule, dates after the failure point are not excluded by this run cycle. Dates generated for the other run cycles of the application are valid and appear in the plan.
The job stops processing the current rule-based run cycle and continues with the next belonging to the application.
Debugging information written to the dump data set (EQQDUMP) should be forwarded to your system administrator.
EQQ0405E
DATE DATE PRIOR TO CURRENT DATE
A date specified to HCL Workload Automation for Z is prior to the current date.
The job is terminated.
Correct the date and rerun the job.
EQQ0412E
SPECIFIED TIME SPAN IS GREATER THAN 4 YEARS
The time span, from current date to end date, may not exceed four years.
If this message is issued from a batch job, the submit request is terminated. If it is issued in the panel, the system waits for you to respond.
Specify an end date less than four years from the current date.
EQQ0420E
CALENDAR ID NOT SPECIFIED
This message is issued from a batch job. The submit request is terminated.
Specify a valid calendar ID.
EQQ0421E
CALENDAR CALNAME NOT FOUND IN DATA BASE
This message is issued from a batch job. The submit request is terminated.
Specify the ID of an existing calendar.
EQQ0422E
PRINT END DATE NOT SPECIFIED
This message is issued from a batch job. The submit request is terminated.
Specify an end date for the calendar/period print program.
EQQ0423I
NO CALENDAR FOUND IN DATA BASE
This message is issued from a batch job. The submit request is terminated. There is no calendar stored in the database.
Create a valid new calendar in the database.
EQQ0430W
ADIDDAYTIME HAS BEEN CHANGED ON-LINE
The operations or dependencies of the occurrence have been changed using the Long-Term Planning panel.
The job continues processing and the occurrence is copied as is to the new long-term plan. However, changes made to the application description, fpor example, changed input arrival, are not considered.
If changes have been made to the application, verify that the occurrence has correct run date and time, deadline date and time, priority, dependencies, and operation data. If they are incorrect, use the Long-Term Planning panel or the Modify Current Plan panel to correct them.
EQQ0431W
LTP RUN CONTAINS WORK STATIONS NOT DEFINED IN WS DESCRIPTION DATA BASE. NO STATISTICS GENERATED FOR WORK STATION WSID
The long-term plan data set contains references to workstations that no longer exist in the workstation description database. Most likely, the workstation descriptions were deleted after the last update of the long-term plan data set.
The job continues processing, but no statistics are generated for the identified workstation.
None.
EQQ0451W
NO SUCCESSOR ADIDDATETIME TO ADIXDATXTIMX
While modifying the long-term plan, a successor to an occurrence could not be found. This is probably due to some abnormal situation that occurred either in an earlier long-term plan run or during an update using the Long-Term Planning panel. This resulted in some inconsistency in the long-term plan data set.
The job continues processing.
Check the flagged applications.
EQQ0452W
NO PREDECESSOR ADIDDATETIME TO ADIXDATXTIMX
While modifying the long-term plan, a predecessor to an occurrence could not be found. This is probably due to some abnormal situation which occurred either in an earlier long-term plan run or during an update using the Long-Term Planning panel. This resulted in some inconsistency in the long-term plan data set.
The job continues processing.
Check the flagged applications.
EQQ0453W
NO OCCURRENCES FOUND FOR PRINT PERIOD STARTDAT- ENDDAT
There are no occurrences in the long-term plan for the print period specified when requesting a print out of the long-term plan.
No occurrences are listed and the job is terminated.
Check that the print period is correct.
EQQ0454W
NO OCCURRENCES FOUND FOR APPLICATION LTADINID
No occurrences for a specific application description ID are printed because no occurrences were found.
No occurrences are listed and the job is terminated.
Check that the application description ID is valid.
EQQ0455I
LTP REPORT PERIOD PARTLY OUTSIDE LTP PERIOD
Either one or both long-term plan (LTP) report limits, specified when requesting a printout of the long-term plan, are outside the LTP range.
The job continues processing.
Check that the print period is correct.
EQQ0458I
NO PREDECESSOR PRAID FOUND FOR SUAID SAIADSAIAT
There is no occurrence that can be defined as a predecessor to the occurrence listed.
The job continues processing, but no predecessor is defined for the occurrence.
None.
EQQ0459I
RCTEXT02RCDATA02 CANCELS: ADID DATETIMERCTEXT01RCDATA01
- RCTEXT02
- NEGATIVE RUNCYCLE, for period-based run cycles. EXCEPTION RULE, for rule-based run cycles.
- RCDATA02
- NPERNSGNNOFS for period-based run cycles. NPER for rule-based run cycles.
- RCTEXT01
- NORMAL RUNCYCLE, for period-based run cycles. REGULAR RULE, for rule-based run cycles.
- RCDATA01
- PNAMSIGNOFFS for period-based run cycles. PNAM for rule-based run cycles.
The negative run cycle defined by NPERNSGNNOFS, or the exception rule defined by NPER, cancels the occurrence ADIDDATETIME defined by the normal run cycle PNAMSIGNOFFS, or the regular rule defined by PNAM.
The job continues processing.
None.
EQQ0460W
ALL CHANGED DEPENDENCIES TO ADIDDATE TIME REMOVED
The indicated occurrence does not exist in the new long-term plan.
The job continues processing. All dependencies to the occurrence are deleted.
Make sure that this occurrence should not exist.
EQQ0461W
ADIDDAYTIME DELETED. AD MISSING
During a modify all run of the long-term plan, the application description for the indicated occurrence/run date/run time could no longer be found.
The job continues processing. The occurrence in the long-term plan data set is deleted.
Make sure that this application description should not exist.
EQQ0466W
INCONSISTENT DOUBLE DEPENDENCY FOUND: THE PREDECESSOR DEPENDENCY ADDED WITH LOOK FORWARD MECHANISM HAS BEEN REMOVED BETWEEN:PRED: yymmdd pred_application_name hhmm SUCC: yymmdd succ_application_name hhmm
The LTP batch program found a repeated dependency between the two occurrences identified by the yymmdd pred_application_name hhmm and yymmdd succ_application_name hhmm LTP keys: this will start a loop at DP batch run time, making it fail. The double dependency was added with the Look Forward mechanism and is removed from the LTP to avoid the loop. This situation can occur when you create the LTP for the first time and have an application with a dependency on itself that runs several times during the day and has resolution criteria set to the same day.
The double dependency is removed leaving only one dependency.
Check if this resolution criteria responds to your needs.
EQQ0467W
INCONSISTENT DOUBLE DEPENDENCY FOUND: THE SUCCESSOR DEPENDENCY ADDED WITH LOOK FORWARD MECHANISM HAS BEEN REMOVED BETWEEN:PRED: yymmdd pred_application_name hhmm SUCC: yymmdd succ_application_name hhmm
The LTP batch program found a repeated dependency between the two occurrences identified by the yymmdd pred_application_name hhmm and yymmdd succ_application_name hhmm LTP keys: this will start a loop at DP batch run time, making it fail. The double dependency was added with the Look Forward mechanism and is removed from the LTP to avoid the loop. This situation can occur when you create the LTP for the first time and have an application with a dependency on itself that runs several times during the day and has resolution criteria set to the same day.
The double dependency is removed leaving only one dependency.
Check if this resolution criteria responds to your needs.
EQQ0500E
END DATE PRIOR TO CURRENT DATE
An end date specified for a create or extend run of the long-term plan, should be later than or the same as the current date.
The job is terminated.
Specify a valid date.
EQQ0501E
INVALID REPORT TYPE TYPE
The report type specified for a long-term plan print request is invalid. Valid report types are F for full report, and D for dependencies only.
The job is terminated.
Specify a correct report type.
EQQ0502E
START DATE AND TIME AFTER END DATE AND TIME
The start date and time for the report interval in a long-term plan print request must be earlier than the end date and time.
The job is terminated.
Specify a correct time interval.
EQQ0503E
SPECIFIED PERIOD OUTSIDE LIMITS OF THE LONG TERM PLAN
Extension of the long-term plan is determined by specific start and end dates in the long-term plan header record. Dates outside the range specified by these dates for updating, printout, or display, are not allowed.
The job is terminated.
Correct the invalid dates.
EQQ0504E
INVALID SORT ORDER ORDER
The sort order specified is not valid. Valid sort orders are I, O, and A.
The job is terminated.
Specify a valid sort order.
EQQ0505E
APPLICATION ADID DOES NOT EXIST IN THE AD DATA BASE
The application (ADID) specified in the long-term plan occurrence is no longer found in the application description database. Most likely, the specified application description has been deleted from the application description database while the corresponding occurrences in the long-term plan data set have not been deleted.
The job is terminated.
Check why the application description cannot be found. If it has been inadvertently deleted, it should be reentered.
EQQ0506W
APPLICATION ADID REFERS TO UNDEFINED CALENDAR CALID DEFAULT CALENDAR DEFCAL WILL BE USED
This message is issued from a long-term plan (LTP) batch program. The calendar specified in the application description could not be found in the database. The default calendar is used.
Processing continues.
Specify a valid calendar in the application description.
EQQ0508W
APPLICATION ADID REFERS TO UNDEFINED CALENDAR CALID DEFAULT CALENDAR DEFCAL NOT FOUND. ALL DAYS TREATED AS WORKDAYS
This message is issued from a long-term plan (LTP) batch program. The calendar specified in the application description could not be found in the database or the calendar specified in the CALENDAR parameter of BATCHOPT could not be found. The DEFAULT calendar is used. If there is no DEFAULT calendar, all days are treated as work days.
The job continues processing.
- Specify a valid calendar in the application description.
- Ensure that the CALENDAR parameter in BATCHOPT is set to a valid value.
EQQ0509W
APPLICATION ADID REFERS TO UNDEFINED DEFAULT CALENDAR CALID ALL DAYS TREATED AS WORKDAYS
This message is issued from a long-term plan (LTP) batch program. The calendar specified in the application description could not be found in the database and the CALENDAR parameter is not defined on BATCHOPT. The DEFAULT calendar is used. If there is no DEFAULT calendar, all days are treated as work days.
The job continues processing.
Ensure that the CALENDAR parameter in BATCHOPT is set to a valid value.
EQQ0511W
ADIDDATE MOVED OUTSIDE RANGE OF AD. RUNCYCLE: PNAMSIGNOFFS FREE DAY RULE: RULE
An occurrence has been generated and moved to the date shown. The move resulted in a date outside the validity limits specified in the application description or resulted in a date after the end date of the long-term plan. If the reason was that the occurrence was moved after the end date of the long-term plan, then the occurrence is included in the next extend of the long-term plan.
The job continues processing, but the occurrence is not included in the long-term plan data set.
Check if the occurrence should be included. If it should, use the Long-Term Planning panel to add the occurrence.
EQQ0512W
GROUP DEFINITION GADID FOR ADID CANNOT BE FOUND FOR PERIOD LOWDATE TO HIGHDATE
A group definition is specified for this application, but the group definition cannot be found in the application description database.
The job continues processing, but no occurrence is included in the long-term plan data set for the application ADID.
Create the requested group definition, or change the name in the group definition ID field, or erase the group definition ID.
EQQ0513W
GROUP DEFINITION GADID FOR ADID CONTAINS NO RUN CYCLES FOR PERIOD LOWDATE TO HIGHDATE
The group definition specified for this application has no run cycle information.
The job continues processing, but no occurrence is included in the long-term plan data set for the application ADID.
If applications that reference the group definition should be scheduled by HCL Workload Automation for Z, include run cycle information in the group definition.
EQQ0514W
THE REPEAT END TIME FOR APPLICATION APPL, RUN CYCLE RUNC WAS LIMITED TO REPET BECAUSE IT IS NOT CONSISTENT WITH THE WORK DAY END TIME IN CALENDAR CAL
The long-term plan batch job has detected that for the application APPL, the run cycle RUNC specifies a REPEAT END TIME that is not consistent with the application calendar work day end time. The REPEAT END TIME must be a value between the input arrival time of the run cycle and the calendar work day end time of the application.
The value REPET, which is one minute before the calendar work day end time, is used as the REPEAT END TIME for the run cycle. The processing continues with this value. The batch job ends with return code 4, at least.
Modify the application description by setting the REPEAT END TIME to a value that is consistent with the work day end time and modify the long-term plan for this application.
EQQ0515E
INVALID INPUT LONG TERM PLAN DATA SET. A NEW LTP IS NOT CREATED. THE BACKUP LTP DATA SET IS VALID BUT THE INPUT LTP IS NOT
The long-term plan (LTP) batch program has found that the input LTP file does not contain a valid long-term plan, but the LTP backup file is valid. The most likely cause of this message is that the previous execution of the LTP batch program failed before the new LTP file was successfully built.
The LTP batch program ends without updating the input LTP file or the backup LTP file.
Copy the backup LTP file into the LTP file and reexecute the LTP batch program.
EQQ0516E
APPLICATION APPL, IA = IA, REFERENCES MORE OCCURRENCES THAN CAN BE CONTAINED IN LARGEST POSSIBLE RECORD IN THE LD WORK FILE
The long-term plan (LTP) batch program determined that the current occurrence referenced more occurrences than the maximum possible defined by the maximum size of a record in the LD work file.
The LTP batch program uses only those dependencies that can be contained in the maximum LD record. Remaining dependencies for this occurrence are not used.
Redefine the LD work file to use a larger maximum record size and reexecute the LTP batch program.
EQQ0517W
ADIDDATE MOVED OUTSIDE GENERATING SPAN. REGULAR RULE: PNAMFREE DAY RULE: RULE
An occurrence has been generated and moved to the date shown. The move resulted in a date outside the generating span. Span start is defined as the highest date of the application description (AD) valid-from date, run cycle in-effect date and long-term plan (LTP) start date. Span end is defined as the lowest date of AD valid-to date, run cycle out-of-effect date minus 1, and LTP end date.
The job continues processing, but the occurrence is not included in the LTP data set.
Check if the occurrence should be included. If it should, use the Long-Term Planning panel to add the occurrence.
EQQ0519W
BACKUP OF THE LONG TERM PLAN DATA SET FAILED
The long-term plan (LTP) batch program or the daily planning batch program was unable to copy the LTP file to the LTP backup file.
The batch program continues normally.
Determine the reason for the backup failure from earlier messages in the message log data set. Take appropriate action to correct the problem and reexecute the batch program.
EQQ0520W
LTP HAS NO OCCURRENCES NOR AN HEADER, ONLY END OF FILE
- Specific application not found
- No valid applications in the period
- No matching period definition.
For the long-term plan (LTP) create function, the job is terminated, and if a LTP exists, it is not replaced. For other LTP functions, the job continues processing.
Check the LTP data set and the application description and calendar databases.
EQQ0521E
SORT FAILURE FOR WORK DATA SET: DDN
Sort was invoked to sort on a long-term plan data set, but the program issued a return code of 16.
The job is terminated.
Investigate the reason for the incorrect sort and rerun the job.
Make the SORT program diagnostic messages on SYSOUT available to your system programmer.
EQQ0522I
MAXIMUM NUMBER OF LTP DEPENDENCIES PER OCCURRENCE IS MAXDEP
This message indicates the maximum number of predecessors and successors that can be created per occurrence using the maximum record sizes specified for the VSAM files defined by the EQQLDDS and EQQLTDS DD statements.
The long-term plan (LTP) batch job continues processing.
Verify that the maximum number of dependencies is not too small. If necessary, reallocate the EQQLDDS and EQQLTDS files to support a larger maximum record size and resubmit the LTP batch job.
EQQ0523W
END DAY DATE ASSUMED WORKDAY FOR CORRECT LTP-CREATION
When you create or extend the long-term plan, the end date must be a work day.
DATE is assumed as a work day and processing continues.
Check the reason why DATE is a free day. If the long-term plan produced is incorrect, specify a new end date as the nearest work day prior to this date, and rerun the job.
EQQ0524W
PERIOD/RUN CYCLE GROUP PNAM IN APPLICATION ADID NOT FOUND
The period or run cycle group specified in the application description database does not exist in the calendar database.
The job continues processing, but the job bypasses this run cycle and generates long-term plan occurrences for the next run cycle.
Add the period or run cycle group to the calendar, or remove the application run cycle, or change the period name in the run cycle description.
EQQ0525W
OFFSET > PERIOD LENGTH AD: ADID RUNCYCLE: PNAM SIGNOFFS
For a given application/run cycle number, the offset is greater than the period length for the specified period.
The job continues processing, but no occurrences are created for the displayed offset.
Correct either the offset or the period length in the calendar.
EQQ0527W
ADIDDATE HAS OFFSET > NONCYCLIC PERIOD LENGTH RUNCYCLE: PNAMSIGNOFFS- NOT PLANNED.
The occurrence ADIDDATE has an offset that is greater than the length of closed interval of the noncyclic period PNAM. (A closed interval has both origin and interval end dates defined.)
The job continues processing, but the occurrence is not planned.
Correct either the specified offset or the interval length of the noncyclic period.
EQQ0528W
ADIDDATE MOVED OUTSIDE NONCYCLIC PERIOD INTERVAL RUNCYCLE: PNAMSIGNOFFS FREE DAY RULE: RULE- PLANNED
The occurrence ADIDDATE has been moved by free-day rule RULE. The moved date is outside the closed interval of a noncyclic period. (A closed interval has both origin and interval end dates defined.)
The job continues processing, but the occurrence is not planned.
Correct either the free-day rule or the interval length of the noncyclic period.
EQQ0529W
ADID DATE TIME FROM RUNCYCLE PNAM HAS DEADLINE BEFORE INPUT ARRIVAL TIME. DEADLINE MOVED TO 24.00 OF THE SAME DAY.
The deadline is set before the input arrival time, therefore is moved to 24:00.
Processing continues.
Change the deadline, if required.
EQQ0531I
GENERATED DUP OMITTED: ADIDDATETIME RCTEXT01RCDATA01
- RCTEXT01
- NORMAL RUNCYCLE, for offset-based run cycles. REGULAR RULE, for rule-based run cycles.
- RCDATA01
- PNAMSIGNOFFS, for offset-based run cycles. PNAM, for rule-based run cycles.
One occurrence is selected and the others are bypassed. The selected occurrence is the one added using the Long-Term Planning panel (if one exists) or the one with the lowest run cycle number.
Check if the application should really run more than once at the same time. If it should, add it but make it a unique occurrence, for example, by altering the input arrival time by one minute.
EQQ0532I
ADIDDAYTIME SUPPRESSED DUE TO ONLINE DELETE
The indicated occurrence cannot be created because the old long-term plan contains the same occurrence, but is marked as deleted.
The job continues processing, but the indicated occurrence is not created.
To create the occurrence, use the Long-Term Planning panel to add it again.
EQQ0534W
ORIGIN DATE MAY BE MISSING FOR PERIOD PNAM APPLICATION ADID
To be sure of the correct use of the calendar database, for a noncyclic period, you must have at least one origin date beyond the specified end date of the long-term plan. This ensures that no work remains unplanned for the period in question.
The job continues processing.
Investigate whether the noncyclic period PNAM should be extended further into the future.
EQQ0535W
COULD NOT MOVE ADIDDATETIME RUNCYCLE: PNAMSIGNOFFS NOT PLANNED
The run date calculated using the run cycle information identified in the message for the occurrence ADID DATETIME is a free day, and the specified free-day rule is 1 (run on the closest work day before the free day). However, HCL Workload Automation for Z could not move the occurrence prior to the free day because the closest work day is before the current plan end date.
The occurrence is not included in the long-term plan (LTP).
If the occurrence should be scheduled, add it manually to the current plan, or change the run cycle or calendar information and rerun the LTP batch job.
EQQ0536W
CAN NOT MOVE, MODIFY OR DELETE ADID DATE TIME. OCCURRENCE HAS SUCCESSOR IN THE CURRENT PLAN.
The occurrence indicated cannot be moved, modified, or deleted because it has at least one successor in the current plan. It occurs in the current plan as a pending predecessor. This message is followed by message EQQ0537I, which identifies the successor occurrence.
Long-term planning continues processing. The indicated occurrence is not moved, modified, or deleted.
If required, use the Long-Term Planning panel to modify or delete the occurrence.
EQQ0537I
ADID DATE TIME
This message identifies the successor to a pending occurrence in the current plan. This message is issued together with message EQQ0536W.
Long-term planning continues processing.
Review message EQQ0536W to determine the reason for this message.
EQQ0538W
ADID DATE RUN CYCLE: PNAM MOVED OUTSIDE GENERATING PLAN BECAUSE OF SHIFT PROCESSING
Due to the application of the SHIFT option, the execution of the occurrence takes place on a date that is beyond the extent of the LTP.
The occurrence is not planned.
If this is not the result you expected, modify the value in the SHIFT option.
EQQ0539W
ADID DATE TIME RUN CYCLE GROUP: PNAM FOR VARIABLE DURATION AND DEADLINE NOT FOUND. OCCURRENCE GENERATING RUN CYCLE WILL BE USED.
In the Application Description, a variable duration or variable deadline is associated with a run cycle group, but the LTP cannot find the run cycle group.
The LTP batch processing continues, and the run cycle that generated the occurrence is used to set the variable duration or deadline.
Verify if the run cycle group PNAM was deleted or if you have a PERIOD with the same name, then update the Application Description accordingly.
EQQ0540E
SPECIFIED PRINTOUT PERIOD GREATER THAN 4 YEARS
You are requesting a printout of the long-term plan data set for a period of longer than four years, but the long-term plan can have a span of up to four years only.
The job is terminated.
Request a printout for a period of less than four years.
EQQ0541E
LONG TERM PLAN EMPTY - NO HEADER RECORD
A long-term plan batch function is trying to reference a long-term plan data set that has no header. The long-term plan is either empty or in error.
The job is terminated.
Use the Long-Term Planning panel to create a long-term plan.
EQQ0542W
OCCURRENCE FOR APPLICATION AD WITH RUNDAY RUNDAY AND INPUT ARRIVAL RTIME COULD NOT BE FOUND IN THE LONG TERM PLAN. PREDECESSORS / SUCCESSORS FOR THE APPLICATION MAY HAVE TO BE MANUALLY COMPLETED
The actual occurrence has been deleted from the long-term plan, probably by a non-HCL Workload Automation for Z function.
A new current plan is created, but the daily planning program ends with a return code of 4.
To make the current plan consistent, check the current plan that is created and complete or delete dependencies.
EQQ0543E
LTP END DATE - LTP START DATE > 4 YEARS
A long-term plan must not be longer than four years.
The job is terminated.
Specify the long-term plan end date again.
EQQ0544E
LTP EXISTS - OCCURRENCES SELECTED BY DAILY PLAN
Occurrences in the long-term plan have been selected by daily planning and might have been included in the current plan. It is not possible to create the long-term plan without first refreshing it using the Service Function panel.
The job is terminated.
Select another long-term plan function.
EQQ0545E
START DATE AFTER END DATE
The start date must be earlier than the end date.
The job is terminated.
Specify correct dates and resubmit the job.
EQQ0546W
THE PREDECESSOR PRED WITH RUNDAY PREDAY AND INPUT ARRIVAL PTIME, FOR APPLICATION AD IN THE LONG TERM PLAN COULD NOT BE FOUND. THE APPLICATION AD WITH RUNDAY RUNDAY AND INPUT ARRIVAL RTIME MAY HAVE TO BE MANUALLY COMPLETED OR DELETED
The actual occurrence has been deleted from the long-term plan, probably by a non-HCL Workload Automation for Z function.
A new current plan is created, but the daily planning program ends with a return code of 4.
To make the current plan consistent, check the current plan that is created and complete or delete the occurrence for the application.
EQQ0547W
THE SUCCESSOR SUC WITH RUNDAY SUCDAY AND INPUT ARRIVAL STIME, FOR APPLICATION AD IN THE LONG TERM PLAN COULD NOT BE FOUND. THE APPLICATION AD WITH RUNDAY RUNDAY AND INPUT ARRIVAL RTIME MAY HAVE TO BE MANUALLY COMPLETED OR DELETED
The actual occurrence has been deleted from the long-term plan, probably by a non-HCL Workload Automation for Z function.
A new current plan is created, but the daily planning program ends with a return code of 4.
To make the current plan consistent, check the current plan that is created and complete or delete the occurrence for the application.
EQQ0549E
MAX CP16 RECORD NUMBER HAS BEEN REACHED. USE REMDSREC PARM TO REMOVE THEM.
Too many CP16 records accumulated. This might happen when the RCLEANUP parameter of BATCHOPT and RCLEANUP parameter of OPCOPTS are set to different values.
The job is terminated.
Use the BATCHOPT REMDSREC parameter to delete the accumulated CP16 records, and ensure that the RCLEANUP parameter of BATCHOPT and RCLEANUP parameter of OPCOPTS are set to the same value.
EQQ0550E
UNDEFINED RECORD FORMAT NOT ALLOWED, DDNAME = ADUSERDS
The record format for the user input data set in the application print program should be either fixed or variable. Undefined is not supported.
The application print program is terminated.
Use a correct input data set and resubmit the job.
EQQ0551E
REPORT TYPE MUST BE FROM 1 TO 4
- 1
- Detailed
- 2
- Internal dependencies
- 3
- Operations using particular workstations
- 4
- Owners.
The job is terminated.
Ensure that the parameter is correctly set and resubmit the job.
EQQ0552E
INPUT TYPE MUST BE 1, 2, OR 3
- 1
- The input includes all application description IDs, owners, or workstation IDs.
- 2
- A list of up to 12 applications.
- 3
- Application description IDs are to be read from a user-supplied data set.
The job is terminated.
Ensure that the parameter is correctly set and resubmit the job.
EQQ0553E
RECORD LENGTH IS LESS THAN 16 FOR USER-DATASET, DDNAME = ADUSERDS
When the record format was fixed, the user data set in the application print program had a record length of less than 16.
The application print program is terminated.
Use a data set with a record length of 16 or more and resubmit the job.
EQQ0554W
AD STARTING WITH ADID IS INVALID, TOO LONG
The specified application ID contains more than 16 characters.
The job continues processing.
Specify the correct application ID and resubmit the job.
EQQ0555W
WS ID WSID NOT FOUND WITHIN ANY APPLICATION
When printing an operations using particular
work stations
report during an application description PRINT,
the specified workstation name does not appear in any application
description.
The job continues processing.
Specify the correct workstation name and resubmit the job.
EQQ0556W
ADID ADID< 16 CHARACTERS, IT WAS PADDED WITH BLANKS
The indicated application ID was read from the user data set and was found to be less than 16 characters. It is padded with blanks up to the sixteenth character. This message is issued only if the input data set has a variable record length.
The application print program continues processing.
Check if all wanted applications were printed.
EQQ0557W
OWNER ID OWID NOT FOUND WITHIN ANY APPLICATION
When printing an owner ID
report type or
displaying the long-term plan for one owner, the specified owner ID
does not appear in any application description.
The job continues processing.
Specify the correct owner ID and resubmit the job.
EQQ0558W
NO AD RECORDS FOUND THAT MEET THE REQUIRED SPECIFICATIONS
No application description records were found that met the required specifications.
The job is terminated.
Check that the application description database is not empty, that if a date is specified it is correct, and that the specified IDs are correct. Correct the errors and resubmit the job.
EQQ0559E
SORT OUT OF SEQUENCE
The application print program found a record that was not sorted in the proper sequence.
The job is terminated.
Check the sort program messages to determine the cause of the error. If you cannot determine the cause of the error, and if the error persists, contact the Software Support.
Contact your system programmer.
EQQ0560E
SORT FAILED
Sort was invoked on a work data set for an application description printout, but the program issued a return code of 16.
The job is terminated.
Check the sort program messages to determine the cause of the error. Correct the error and resubmit the job.
Contact your system programmer.
EQQ0561W
APPLICATION ADID NOT VALID ON DATE
A detailed application description printout is requested for a specific application, valid on a specific date, but no such description exists in the application description database.
The job continues processing.
Check if the date is correctly specified and if an application description that is valid on that date should exist.
EQQ0562E
INVALID COMBINATION OF INPUT PARAMETERS
It is not possible to select input type 3 when report type 3 or 4 has been chosen.
The job is terminated.
Ensure that the parameters are correctly set and resubmit the job.
EQQ0563E
INVALID NUMBER OF ITEMS IN INPUT PARAMETERS
The number of items is greater than 12 or does not equal the number of items in the list.
The job is terminated.
Ensure that the parameters are correctly set and resubmit the job.
EQQ0564W
RECORD IS BLANK OR APPLICATION ID DOES NOT START IN POSITION ONE
A record in the user input data set was found that was blank or the application ID did not start in position one.
The record is ignored.
Check if the record in the input user data set is blank or if the application ID starts in position one.
EQQ0567W
APPLICATION ADID HAS INVALID RULE RULE IN RUNCYCLE
The internal representation of rule RULE in application ADID is invalid and the corresponding rule command cannot be derived from it.
The job continues processing with the next run cycle or application description.
Use the Application Description panel to check the rule definition. If necessary, redefine the rule.
EQQ0585I
NO CHANGES PERFORMED FOR THIS SELECTION
You have specified that a certain field should be changed by the mass update function, but no field in the application description database matched the specifications.
The job continues processing. The application description database is not updated for this selection.
Check the input specifications, correct any errors, and retry the mass update of this field.
EQQ0588E
OCCURRENCE OCCADOCCDAYOCCTIME HAS TOO MANY PREDECESSORS. CURRENT PREDECESSOR APPLICATION IS DEPADDEPDAYDEPTIME.
An occurrence has been found that has too many predecessors to be saved in the long-term plan (LTP) dependency work file defined by the EQQLDDS DD statement.
The LTP batch job terminates processing. No new LTP is created.
Verify that external predecessors have been correctly defined in the Application Description file for this application. If necessary, reallocate the EQQLDDS and EQQLTDS files to support a larger maximum record size. After making corrections, resubmit the failing LTP batch job.
EQQ0589W
ERROR DETECTED WHEN PROCESSING AN OPERATIONS NETWORK FOR OCCURRENCE OCCID
When building a network for operations within a single application, a loop or an inconsistency was found. This message indicates that an error in the application description was introduced after the application description was created.
The job continues processing. No occurrences are generated for the application.
Check the application description.
EQQ0590W
OCCURRENCE OCCADOCCDAYOCCTIME HAS TOO MANY SUCCESSORS. CURRENT SUCCESSOR APPLICATION IS DEPADDEPDAYDEPTIME. NSUC SUCCESSOR DEPENDENCIES COULD NOT BE CREATED
An occurrence has been found that has too many successors to be saved in the long-term plan (LTP) dependency work file defined by the EQQLDDS DD statement.
The LTP batch job continues processing. No dependency is created between the current occurrence and the current successor occurrence or any other occurrence with a later input arrival time.
Verify that external predecessors have been correctly defined in the Application Description file for thecurrent successor application. Use the information given by message EQQ0522 to determine the maximum number of dependencies that is supported by the EQQLDDS and EQQLTDS files. If necessary, reallocate the EQQLDDS and EQQLTDS files to support a larger maximum record size and resubmit the LTP batch job.
EQQ0591E
WRONG INPUT PARAMETERS TO BATCH JOB
Parameters in the SYSIN statement are specified incorrectly. The error can arise, for example, when the alignment of parameters is wrong or when there is an extra parameter.
The job is terminated.
Ensure that the parameters are correctly set and resubmit the job.
EQQ0592E
THE SPECIFIED PERIOD CAN NOT BE HANDLED BY THE LTP BATCH PROGRAM
When creating a long-term plan (LTP), HCL Workload Automation for Z builds a calendar that begins four years before the start of the LTP period and ends four years after the end of the LTP period. HCL Workload Automation for Z cannot handle dates later than 31 December 2071. The specified LTP time period would result in an LTP calendar extending beyond 2071.
The job is terminated.
Redefine the LTP period and resubmit the job.
EQQ0593E
NO INPUT PARAMETERS TO BATCH JOB
No parameters were specified in the SYSIN statement for a batch job.
The job is terminated.
Specify the necessary parameters and resubmit the job.
EQQ0594W
THE RUN CYCLE GROUP RUN_CYCLE_GROUP_NAME DID NOT GENERATE DATES BECAUSE OF RULE ERRORS
No dates are generated for this run cycle group in the LTP because of rule errors. This message is preceded by another message that explains the error in the rule.
No occurrences are created in the LTP for this run cycle group.
See the associated message to resolve the error in the rule.
EQQ0597E
UNABLE TO OPEN SEQUENTIAL FILE DDNAME
The data set with the ddname DDNAME could not be opened.
The job is terminated.
Check that the indicated data set is defined by a DD statement and that it is available.
Contact your system programmer.
EQQ0599E
DD-STATEMENT MISSING FOR FILE DDNAME
The DD statement for the file with ddname DDNAME is missing.
The job is terminated.
Add the missing DD statement in the JCL and rerun the job.
EQQ0600E
EITHER AN END DATE OR AN EXTENSION LENGTH MUST BE GIVEN
You must specify either a new end date or an extension length, not both.
The long-term plan (LTP) batch job terminates processing.
Check the JCL of the LTP batch job, update the SYSIN statement, and resubmit the job.
EQQ0601E
THE EXTENSION LENGTH SHOULD BE A NUMERIC VALUE FROM 0001 TO 1461
The extension length must be not longer than 4 years, that is, 1461 days.
The long-term plan batch job terminates processing.
Update the extension length on the SYSIN statement and resubmit the job.
EQQ0602E
AN EXTENSION LENGTH AND A START DATE CANNOT BE ENTERED TOGETHER
You must specify either an extension length or a start date and an end date.
The long-term plan batch job terminates processing.
Update the SYSIN statement and resubmit the job.
EQQ0603E
A START DATE REQUIRES AN END DATE TO BE SPECIFIED
To simulate the long-term plan (LTP) create function you must specify both a start date and an end date.
The LTP batch job terminates processing.
Specify both a start date and an end date on the SYSIN statement and resubmit the job.
EQQ0613I
NO RESFILTER VALUES. REASON IS NOREASON
- NO RESFILTER DATASET NAME GIVEN
- RESFILTER DATASET COULD NOT BE OPENED
- DATASET DOES NOT CONTAIN ANY RESFILTER STATEMENTS.
The DP batch job continues processing. There are no reports of any kind produced for resources.
- The DP batch program SYSIN, if the name of the RESFILTER data set was omitted.
- The allocation of the data set or PDS to be a FB 80 data set. For this message reason, the data set name given in the DP SYSIN can be invalid or misspelled.
- The name given in the DP SYSIN. If the name is correct, provide filter values as RESFILTER statements in this data set.
EQQ0614W
RES RES: USAGE COUNTER WAS RESET
The DP batch job continues processing. The usage counter is reset to 0 to be coherent with the maximum limit function deactivation.
Check if the maximum limit deactivation is really what you want: a usage counter greater than 0 means that one or more operations used the special resource with the maximum limit function active.
EQQ0615W
RES RES: MAX LIMIT WAS APPLIED
The DP batch job continues processing. The global availability of the special resource is changed according to the maximum limit type that is set in the RD database, because the maximum usage limit was reached. The usage counter is reset.
Verify if resetting the global availability of the special resource is really what you want.
EQQ0617I
*******************
- Special Resource is not available. The special resource is not available at the time indicated by the planned start time. Either an interval specifies that the resource should be unavailable or, if no interval exists for this time, the default values specify that the resource is not available.
- The Workstation is not connected to this resource. The workstation on which the operation is defined is not in the workstation connect table at the planned start time.
- Resource contention. The resource could not be allocated because it was already allocated by another operation.
The DP batch job continues processing.
Use the reason to decide if you should change the special resource definition or the application description.
EQQ0618W
RES: **************** LAST IVL USED ****** ****
This message is issued by the daily planning (DP) batch programs to the DP report data set when the default segment of a special resource differs from what is defined in the special resource database.
The DP batch job continues processing. The default interval of the special resource is reset to the values specified in the special resource database.
If the default values have been changed in the special resource monitor log, update the values again or update the defaults set in the database.
EQQ0619W
RESOURCE RES, DEFAULTS WERE RESET
- Default quantity
- Default availability
- Default number of workstations connected.
The DP batch job continues processing. The default fields for that interval maintain the values saved in the dynamic CX data set.
Check the reason for which the message was issued and undertake the proper corrective actions if the difference turns out to be the result of a mistake.
EQQ0820E
APPLICATION NAME, OPNUMBER NO DOES NOT EXIST
The indicated application name or operation number, or both, for which you want to create an operator instruction, cannot be found in the application description database.
The job is terminated.
Check a printout of the applications in your installation.
EQQ0821E
PROGRAM INTERFACE INITIALIZATION REQUEST TO SUBSYSTEM SUBSYS FAILED
A program interface (PIF) initialization request to subsystem SUBSYS was a failure. When the job does not allocate the EQQOIDS file, HCL Workload Automation for Z uses the PIF to retrieve or update operator instructions.
The job is terminated.
Check that the correct subsystem name is specified in the SUBSYS parameter of the BATCHOPT statement. Also check the message log and the SYSLOG for additional messages. If EQQDUMP has been allocated, it might contain additional diagnostic information, for example, a message indicating that PIF was unable to allocate a message log.
If the controller is not active, specify the EQQOIDS DD statement in the JCL and resubmit the job.
EQQ0822E
PROGRAM INTERFACE REQUEST TO SUBSYSTEM SUBSYS FAILED
A program interface (PIF) request to subsystem SUBSYS was a failure. When the job does not allocate the EQQOIDS file, HCL Workload Automation for Z uses the PIF to retrieve or update operator instructions.
The job is terminated.
See the message log to determine the cause of the error. If EQQDUMP has been allocated, it might contain additional diagnostic information. Also ensure that the correct subsystem name is specified in the SUBSYS parameter of the BATCHOPT statement or in the INIT statement.
EQQ0831E
RECORD FORMAT MUST BE FIXED IN INPUT DATASET, DDNAME = EQQOPIN
When doing a mass update of operator instructions, the record format must be fixed for the sequential input data set.
The job is terminated.
Use a correct input data set and resubmit the job.
EQQ0832E
RECORD LENGTH IS NOT 80 IN INPUT DATASET, DDNAME = EQQOPIN
When doing a mass update of operator instructions, the record length must be 80 for the sequential input data set.
The job is terminated.
Use a correct input data set and resubmit the job.
EQQ0834E
INVALID REPLACE PARAMETER: REPL
- Y
- In the operator instructions database, replace the operator instructions whose search key matches a key in the sequential input file, and add the operator instructions whose search key is not found in the operator instructions database.
- N
- Add only the operator instructions whose search key is not found in the operator instructions database.
The job is terminated.
Enter a valid replace attribute.
EQQ0836E
INVALID OPERATOR INSTRUCTION FUNCTION TYPE
- 5
- Print the OI in application description ID order.
- 6
- Print the OI in workstation order.
- 7
- Purge old OIs.
- 8
- Process sequential input.
The job is terminated.
Enter a valid function type.
EQQ0837W
FIRST INPUT RECORD NOT HEADER RECORD
The first record encountered while creating operator instructions from a sequential input file is not a header record.
The job continues processing. All records up to the first valid header record are bypassed.
Correct your input and resubmit the job so that the bypassed instructions are also created or use the Operator Instruction panel to create the instructions.
EQQ0838W
INVALID INPUT SYNTAX. NO KEY FIELD SPECIFIED
A header record is encountered, but no key field is specified.
The job continues processing. All records up to the first valid header record are bypassed.
Correct your input and resubmit the job so that the bypassed instructions are also created or use the Operator Instruction panel to create the instructions.
EQQ0839W
INVALID LENGTH LEN OF KEY FIELD. KEY: NAMENO
You specified a key field for the key NAMENO, but the length of the value that you gave to it is too large.
The job continues processing. All records up to the first valid header record are bypassed.
Correct your input and resubmit the job so that the bypassed instructions are also created or use the Operator Instruction panel to create the instructions.
EQQ0840W
INVALID LENGTH LEN OF VALFROM FIELD. INSTR.: NAMENO
You specified a valid-from field (for operator instruction NAME) that is less than 10 characters long.
The job continues processing. All records up to the first valid header record are bypassed.
Correct your input and resubmit the job so that the bypassed instructions are also created or use the Operator Instruction panel to create the instructions.
EQQ0841W
NO APPLICATION NAME FOUND FOR OPERATOR INSTRUCTION
An operator instruction must contain a valid application name and operation number corresponding to an existing application.
The job continues processing, but the instruction is not created. All records up to the next header statement are bypassed.
Add the corresponding application description or if the application name is misspelled, change it.
EQQ0844W
OPERATOR INSTRUCTION NAMENO ALREADY EXISTS
The operator instruction (NAME) that you attempted to add already exists in the operator instructions database.
The job continues processing, but the instruction is not created. All records up to the next valid header statement are bypassed.
Use the Operator Instruction panel to modify the operator instruction.
EQQ0845W
VALFROM > VALID TO DATE+TIME. INSTR.: NAMENO
The valid-from date that you specified in the operator instruction NAME is later than the valid-to date and time. The valid-from date must be earlier than the valid-to date.
The job continues processing, but the instruction is not created. All records up to the next valid header statement are bypassed.
Enter valid dates.
EQQ0846W
BOTH DATE AND TIME MUST BE SPECIFIED. INSTR.: NAMENO
Either the date or the time was omitted. Both are required.
The job continues processing, but the instruction is not created. All records up to the next valid header statement are bypassed.
Correct your input.
EQQ0847W
EMPTY OPERATOR INSTRUCTION IN SEQ INPUT FILE
The operator instruction has no instruction text.
The job continues processing, but the operator instruction is not added to the operator instructions database.
Add text to the operator instruction in the sequential input file.
EQQ0848W
PERIOD OVERLAPPING FOR INSTR: NAMENO
Temporary operator instructions for application NAME have periods that overlap. Temporary operator instructions with overlapping periods are not allowed.
The job continues processing, but the operator instruction is not added to the operator instructions database.
Change the valid-from and valid-to periods in the operator instructions so that they do not overlap.
EQQ0849W
AD NOT VALID AT SAME TIME AS INSTR: NAMENO
The specified operator instruction is not within the valid-from and valid-to time period for the application description.
The job continues processing, but the operator instructions database is not updated with the specified operator instructions.
Correct the valid-from and valid-to times for the specified operator instruction in the sequential input file.
EQQ0911E
THE OUTPUT DATA SET, DDNAME = EQQOSLCO, COULD NOT BE OPENED
The EQQUOTOP program failed to open the data set referenced by the EQQOSLCO DD statement. The statement was incorrectly specified, or it is missing.
The EQQUOTOP program ends with RC=8. No encryption action is performed.
Check the EQQOSLCP job and ensure that the data set name specified in the EQQOSLCO DD statement is correctly specified. Correct the submitted JCL and resubmit it.
EQQ0912E
THE INPUT DATA SET, DDNAME = EQQOSLCI, COULD NOT BE OPENED
The EQQUOTOP program failed to open the data set referenced by the EQQOSLCI DD statement. The statement was incorrectly specified, or it is missing.
The EQQUOTOP program ends with RC=8. No encryption action is performed.
Check the EQQOSLCP job and ensure that the data set name specified in the EQQOSLCI DD statement is correctly specified. Correct the submitted JCL and resubmit it.
EQQ0913E
LOGICAL RECORD SIZE FOR THE DDNAME = EQQOSLCO IS NOT VALID
The EQQUOTOP program failed to read the contents of the data set referenced by the EQQOSLCO DD statement. The logical record length is not equal to 80 bytes.
The EQQUOTOP program ends with RC=8. No encryption action is performed.
Check that the EQQOSLCO DD statement is correctly specified in the EQQOSLCP job.
EQQ0914E
LOGICAL RECORD SIZE FOR THE DDNAME = EQQOSLCI IS NOT VALID
The EQQUOTOP program failed to read the contents of the data set referenced by the EQQOSLCI DD statement. The logical record length is not equal to 80 bytes.
The EQQUOTOP program ends with RC=8. No encryption action is performed.
Check that the EQQOSLCI DD statement is correctly specified in the EQQOSLCP job
EQQ0917E
OBJ LOAD MODULE COULD NOT BE LOADED
The scheduler could not locate the load module shown in the message text for the OSLC integration function.
The EQQOSLCP job ends.
Ensure that the job references a library that contains the load module shown in the message text, and then resubmit the job.
EQQ0918E
THE EQQOSLCI DATA SET IS EMPTY
The EQQOSLCI DD statement in the EQQOSLCP job references an empty data set.
The EQQOSLCP job ends.
Check that the EQQOSLCI DD statement is correctly defined and uses the correct data set name. Correct the submitted JCL and resubmit it.
EQQ0919E
I/O ERROR READING EQQOSLCI DATA SET
The data set referenced by the EQQOSLCI DD statement could not be read, an I/O error occurred.
The EQQOSLCP job ends.
Correct the submitted JCL and resubmit it.
Review any preceding messages in the output of the job or in the system log to determine the exact reason for this error.
EQQ0922W
AN ERROR OCCURRED WHILE WRITING DATA TO THE EQQOSLCO DATA SET
An I/O error occurred in the routine performing the encryption of the password contained in the PASSWORD parameter.
The EQQOSLCP job processing continues.
Correct any error present in the job and resubmit it. If the problem persists, generate a dump by defining a slip trap based on this message and contact the Software Support.
Review any preceding messages in the output of the job and check the resulting contents of the EQQOSLCO data set.
EQQ0924E
EQQUOTOP PROGRAM TERMINATED BECAUSE OSLCOPTS STATEMENT CONTAINS SYNTAX ERRORS
The EQQUOTOP program found a syntax error in the OSLCOPTS statement.
The EQQOSLCP job ends.
Correct any syntax error present in the OSLCOPTS statement then resubmit the EQQOSLCP job.
Review any preceding messages in the output of the job.
EQQ0936E
I/O ERROR ON MESSAGE DATA SET FOR MESSAGE MSG
HCL Workload Automation for Z was not able to display message MSG. The message is not in the HCL Workload Automation for Z message log data set.
See the system action documented in message MSG.
Check that the latest version of the HCL Workload Automation for Z message library (ddname EQQMLIB) is installed. You may have installed the code for a new fix, but not the corresponding level of the message library.
Contact your system programmer and see message MSG.
EQQ0937W
MESSAGE MSG IS LONGER THAN 120 CHARACTERS
The indicated message is longer than 120 characters.
The job continues processing, but ignores the invalid message.
Check that the latest version of the HCL Workload Automation for Z message library (ddname EQQMLIB) is installed and that the indicated message has not been changed at your installation. If you cannot fix the problem, contact the Software Support.
Contact your system programmer.
EQQ0953E
OCCURRENCE ANAME AT ATIME VSAM KEY: OPKEY HAS AN INVALID OPERATION
An operation record was detected with a zero operation number.
The daily planning batch job is stopped with a return code of 12.
This is a HCL Workload Automation for Z error. Create an APAR tape, use IDCAMS to delete the operation with the given VSAM key, and contact the Software Support.
Contact your system programmer.
EQQ0954E
FUNC FAILED FOR FILE LOGICAL FILE, CALLING MODULE IS MODULE
A batch program attempted to perform the function FUNC against the VSAM file FILE, but the attempt failed. The I/O request is from module MODULE.
The job is terminated.
Review the HCL Workload Automation for Z message log for I/O errors that immediately precede this message. This message usually comes with another error message that describes the error in more detail. If you cannot fix the problem, contact the Software Support.
Contact your system programmer.
EQQ0955E
FUNC REQUESTED FOR FILE FILE WHICH IS NOT OPEN CALLING MODULE IS MODULE
A batch program attempted to perform the function FUNC against the file FILE, but the file had not been opened. The I/O request is from module MODULE.
The job is terminated.
Review the HCL Workload Automation for Z message log for I/O errors that immediately precede this message. If you cannot fix the problem, contact the Software Support.
Contact your system programmer.
EQQ0956E
FUNC FAILED FOR FILE, CALLING MODULE IS MODULE REASON FOR FAILURE IS WRONG RECORD LENGTH
A batch program attempted to perform the function FUNC against the file FILE, but the attempt failed. The I/O request is from module MODULE. The program forces the failure because of a mismatch among the allowed record length and the one specified in the JCL submitting the batch. This might happen if you used the old LTP batch skeleton after migrating to version 8.5.1.
The job is terminated.
Check the correct record length to be used, set it in the JCL submitting the batch and rerun it.
Contact your system programmer.
EQQ0957E
LOGICAL END OF FILE ON FILE-DS: FUNC,KEY
A batch program attempted to read a record in the data set FILE, but the record no longer exists in the data set.
The job is terminated.
Review the HCL Workload Automation for Z message log for I/O errors that immediately precede this message. If you cannot fix the problem, contact the Software Support.
Contact your system programmer.
EQQ0958E
FUNC FAILED FOR FILE, CALLING MODULE IS MODULE
A batch program attempted to perform the function FUNC against the file FILE, but the attempt failed. The I/O request is from module MODULE.
The job is terminated.
Review the HCL Workload Automation for Z message log for I/O errors that immediately precede this message.If you cannot fix the problem, contact the Software Support.
Contact your system programmer.
EQQ0959E
FUNC FAILED FOR FILE MSG: SYNADMSG CALLING MODULE IS MODULE
A batch program attempted to perform the function FUNC against the file FILE, but the attempt failed. The I/O request is from module MODULE.
The job is terminated.
Determine the cause of the error and take the appropriate action.
Contact your system programmer.
The SYNAD routine collects information such as jobname, stepname, unit address, device type, ddname, operation, error description, and access method. The SYNADAF macro is used to extract this information. For a detailed description of the layout refer to the appropriate documentation for the MVS/DFP product installed on this system.
EQQ0971E
MAXIMUM NUMBER OF OCCURRENCES HAS BEEN REACHED FOR APPLICATION ADID
No more occurrences of this application can be added. The current plan can contain approximately 970 occurrences of each application.
When the HCL Workload Automation for Z panel is used to add occurrences, a lower limit (approximately 870) is used.
The daily planning batch program ends, but no new current plan is created.
Complete or delete occurrences of this application that are no longer needed. This prevents these occurrences from being included if the daily plan is rerun. If necessary, use a shorter planning period. Resubmit the daily planning job.
EQQ0972E
MAXIMUM NUMBER OF OCCURRENCES REACHED
No more occurrences can be added to the current plan because the maximum number of occurrences has been reached.
The daily planning batch program ends, but no new current plan is created. If a current plan existed prior to the running of the daily planning job, HCL Workload Automation for Z continues to use the existing current plan.
Check the value specified in the MAXOCCNUM parameter of BATCHOPT. If no value is specified, HCL Workload Automation for Z defaults the value to 32767.
Review problem determination and take any appropriate actions. Resubmit the daily planning job.
Check the long-term 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. If the current plan contains a significant number of completed or deleted occurrences, submit a daily plan REPLAN.
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.
When you specify PREVRES(YES) in 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.
EQQ0981E
THE INPUT DATA SET, DDNAME = EQQUSRIN, COULD NOT BE OPENED.
The EQQUPTOP program failed to open the data set referenced by the EQQUSRIN DD statement. The statement was incorrectly specified, or it is missing.
The EQQUPTOP program ends with RC=8. No encryption action is performed.
- The data set name in the EQQUSRIN DD statement is correctly specified.
- The data set name includes the member name.
EQQ0982E
THE INPUT DATA SET, DDNAME = SYSIN, COULD NOT BE OPENED.
The EQQUPTOP program failed to open the data set referenced by the SYSIN DD statement. The statement was incorrectly specified, or it is missing.
The EQQUPTOP program ends with RC=8. No encryption action is performed.
Check the EQQE2EPW job and ensure that the data set name specified in the SYSIN DD statement is correctly specified. Correct the submitted JCL and resubmit it.
EQQ0983E
LOGICAL RECORD SIZE FOR THE DDNAME = EQQUSRIN IS NOT VALID.
The EQQUPTOP program failed to read the contents of the data set referenced by the EQQUSRIN DD statement. The logical record length is not equal to 80 bytes.
The EQQUPTOP program ends with RC=8. No encryption action is performed.
Check that the EQQUSRIN DD statement is correctly specified in the EQQE2EPW job. Correct the submitted JCL and resubmit it.
EQQ0984E
LOGICAL RECORD SIZE FOR THE DDNAME = SYSIN IS NOT VALID.
The EQQUPTOP program failed to read the contents of the data set referenced by the SYSIN DD statement. The logical record length is not equal to 80 bytes.
The EQQUPTOP program ends with RC=8. No encryption action is performed.
Check that the SYSIN DD statement is correctly specified in the EQQE2EPW job. If necessary, copy the SYSIN data to a file with record size equal to 80 bytes. Correct the submitted JCL and resubmit it.
EQQ0985I
DDNAME SYSIN IS MISSING OR SPECIFIES DD DUMMY.
The EQQE2EPW password encryption job does not specify any SYSIN DD statement or specifies a DUMMY DD statement.
The processing continues without reading the SYSIN data set, and encrypts only the passwords contained in the specified member of the EQQUSRIN data set.
No action is requested if you do not need to specify a SYSIN data set, otherwise add the proper SYSIN DD statement and resubmit the EQQE2EPW job. Check that the SYSIN DD statement is correctly specified in the EQQE2EPW job.
EQQ0986E
EQQUPTOP PROGRAM TERMINATED BECAUSE OF UNRECOVERABLE ERRORS.
A severe error occurred during the execution of the EQQUPTOP program.
The EQQUPTOP program ends.
Review the EQQMLOG data set and the SYSUDUMP data set to determine the cause of the error. Correct the submitted JCL and resubmit it. If you cannot determine the cause of the error and if the error persists, contact the Software Support, providing message log and system dump.
EQQ0987E
END-TO-END EQQZTWST LOAD MODULE COULD NOT BE LOADED.
The scheduler could not locate the load module shown in the message text for the end-to-end function.
The EQQE2EPW job ends.
Ensure that the job references a library that contains the load module shown in the message text, and then resubmit the job.
EQQ0988E
THE SYSIN DATA SET IS EMPTY.
The SYSIN DD statement in the EQQE2EPW job references an empty data set.
The EQQE2EPW job ends.
Check that the SYSIN DD statement is correctly defined and uses the correct data set name. Correct the submitted JCL and resubmit it.
EQQ0989E
I/O ERROR READING SYSIN.
The data set referenced by the SYSIN DD statement could not be read, an I/O error occurred.
The EQQE2EPW job ends.
Correct the submitted JCL and resubmit it.
Review any preceding messages in the output of the job or in the system log to determine the exact reason for this error.
EQQ0991E
KEYWORD IS A MISSING USRREC KEYWORD.
The error occurred while processing the SYSIN data referenced by the EQQE2EPW JCL. The EQQUPTOP program expects to find a sequence of triplets, each one containing the USRCPU, USRNAM, and USRPSW parameters, combined without repetition. Each of the triplets must correspond to a consistent set of parameters for a USRREC statement. All the three parameters must be present in the SYSIN, and only one parameter per row is allowed. The message variable shows the parameter that is missing.
The EQQE2EPW job ends.
Correct the SYSIN data and resubmit the EQQE2EPW job.
The error might have been caused by processing stopped due to a previous syntax error (for example, duplicate parameters or more than one parameter on a row). Review the SYSIN and any previous message in the output of the job or in the system log, to determine the exact reason for this error.
EQQ0992W
AN INTERNAL ERROR OCCURRED WHILE PERFORMING ENCRYPTION OF CARD .
An internal error occurred in the routine performing the encryption of the password contained in the USRPSW parameter CARD.
The EQQE2EPW job processing continues.
Correct EQQE2EPW job and resubmit it. If the problem persists, generate a dump by defining a slip trap based on this message and contact the Software Support.
Review any preceding messages in the output of the job and check the resulting contents of the EQQUSRIN data set.
EQQ0993W
AN ERROR OCCURRED WHILE WRITING DATA TO THE EQQUSRIN DATA SET.
An I/O error occurred in the routine performing the encryption of the password contained in the USRPSW parameter.
The EQQE2EPW job processing continues.
Correct any error present in the job and resubmit it. If the problem persists, generate a dump by defining a slip trap based on this message and contact the Software Support.
Review any preceding messages in the output of the job and check the resulting contents of the EQQUSRIN data set.
EQQ0994I
AN OLD USRREC STATEMENT HAS BEEN REPLACED BY A NEWER ONE. USRCPU = CPU, USRNAM = NAM.
A duplicate USRREC statement was found in the SYSIN data set, in the specified member of the EQQUSRIN data set, or while copying the SYSIN data to the EQQUSRIN data set member. The last statement was kept while the oldest one was removed. CPU and NAM correspond to the statement key.
The EQQE2EPW job processing continues.
If you are not replacing statements due to password change, review the output of the job and check the resulting contents of the EQQUSRIN data set.
EQQ0995I
USRPSW KEYWORD SPECIFIES AN EMPTY VALUE. IT IS NOT ENCRYPTED.
When processing the USRPSW parameter of the USRREC statement, the EQQE2EPW JCL detected that no password was supplied. USRPSW(‘’) was specified.
The statement processing continues. The USRPSW parameter is stored as it is in the specified member of the EQQUSRIN data set. The result is the same as having a user ID with no password assigned.
No action is requested. If you want to specify a password for encryption, set it in the USRPSW parameter and resubmit the EQQE2EPW JCL.
EQQ1457E
NO OUTPUT FILE COULD BE OPENED. PLEASE CHECK JCL
The daily planning print program could not open any output data set.
The job is terminated.
Check the JCL. There must be at least a SYSPRINT DD statement present. Resubmit the job.
EQQ1458I
DAILY PLANNING REPORT USER EXIT IS ACTIVE FOR THIS PRINTOUT
The exit for daily planning print is activated.
The job continues processing.
None.
EQQ1459I
DAILY PLANNING REPORT USER EXIT IS NOT ACTIVE FOR THIS PRINTOUT
The exit for daily planning print is not activated.
The job continues processing.
None
EQQ1594E
INVALID PARAMETER SPECIFIED IN SYSIN
Parameters in the SYSIN statement must be a character string. Valid values are 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12, 13, and 14.
The job is terminated.
Check the batch job submit panels and make sure that the HCL Workload Automation for Z input field verification logic has not been removed or changed. If the panels were not removed or changed, contact the Software Support.
If the job was submitted outside HCL Workload Automation for Z, correct the parameters and resubmit the job. If the job was submitted from the Application Description panel, contact your system programmer.
EQQ1595I
OUTPUT FIELDS HAVE BEEN TRUNCATED
Lines longer than 120 characters have been truncated in the report.
The run cycle description and special resource fields are truncated.
None.
EQQ1596E
NO PARAMETERS SPECIFIED
No parameters were specified in the SYSIN statement for a batch job.
The job is terminated and a return code of 8 is issued.
Specify the necessary parameters and resubmit the job.
EQQ2010E
DAILY PLAN ENDS DUE TO ERRORS IN INPUT DATA. REFER TO DIAGNOSTIC FILE EQQDUMP FOR MORE INFORMATION
The daily planning program has detected an error in the input data. The validation error action specified in the BATCHOPT statement is to end the daily planning program.
The daily planning program ends. No new current plan is created.
If necessary, use the HCL Workload Automation for Z panel to remove incorrect records. After making corrections, resubmit the daily planning job.
Refer to the preceding validation error message and data in the dump data set, EQQDUMP, to determine the cause of the error.
EQQ2011W
A PREDECESSOR TO APPLICATION APPLIADATEIATIME WAS NOT FOUND
The daily planning program was unable to find a predecessor to the occurrence defined by this message.
The daily planning program takes the action defined by the VALEACTION parameter of the BATCHOPT statement.
If no new plan is produced, resubmit the daily planning job with VALEACTION(W) specified in the BATCHOPT statement. If a new plan has been created, use the HCL Workload Automation for Z panel to verify that dependencies have been correctly created for the identified occurrence. The panel can be used to repair the inconsistency in the current plan or long-term plan records. It may be necessary to delete and add again the predecessor occurrence or the identified occurrence. In some instances it may be sufficient to delete a predecessor specification.
Refer to the data in the dump data set, EQQDUMP, to determine the cause of the error.
EQQ2012W
A SUCCESSOR TO APPLICATION APPLIADATEIATIME WAS NOT FOUND
The daily planning program was unable to find a successor to the occurrence defined by this message.
The daily planning program takes the action defined by the VALEACTION parameter of the BATCHOPT statement.
If no new plan is produced, resubmit the daily planning job with VALEACTION(W) specified in the BATCHOPT statement. If a new plan has been created, use the HCL Workload Automation for Z panel to verify that dependencies have been correctly created for the identified occurrence. The panel can be used to repair the inconsistency in the current plan or long-term plan records. It may be necessary to delete and add again the successor occurrence or the identified occurrence. In some instances it may be sufficient to delete a successor specification.
Refer to the data in the dump data set, EQQDUMP, to determine the cause of the error.
EQQ2013W
A RERUN RECORD WITHOUT A MATCHING OCCURRENCE RECORD WAS FOUND
The daily planning program was unable to find an occurrence record for an occurrence referenced in a rerun record (record type 09).
The daily planning program takes the action defined by the VALEACTION parameter of the BATCHOPT statement.
If no new plan is produced, resubmit the daily planning job with VALEACTION(W) specified in the BATCHOPT statement.
Refer to the data in the dump data set, EQQDUMP, to determine the cause of the error.
EQQ2014W
A READY LIST ENTRY WITHOUT A MATCHING OCCURRENCE RECORD WAS FOUND FOR WORK STATION WSNAME
The daily planning program was unable to find an occurrence record for an occurrence referenced in a ready list record (record type 11).
The daily planning program takes the action defined by the VALEACTION parameter of the BATCHOPT statement.
If no new plan is produced, resubmit the daily planning job with VALEACTION(W) specified in the BATCHOPT statement.
Refer to the data in the dump data set, EQQDUMP, to determine the cause of the error.
EQQ2015W
AN INTERNAL PREDECESSOR IN APPLICATION APPLIADATEIATIME WAS NOT FOUND
The daily planning program was unable to find an operation record for an operation defined as an internal predecessor to an operation in the occurrence defined by this message.
The daily planning program takes the action defined by the VALEACTION parameter of the BATCHOPT statement.
If no new plan is produced, resubmit the daily planning job with VALEACTION(W) specified in the BATCHOPT statement. If a new plan has been created, use the HCL Workload Automation for Z panel to verify that dependencies have been correctly created for the identified occurrence.
Refer to the data in the dump data set, EQQDUMP, to determine the cause of the error.
EQQ2016E
OPERATION OPERNR IN APPLICATION APPLID IS TOO LARGE TO BE SAVED IN THE NEW CURRENT PLAN DATA SET. THE FAILING OPERATION CONTAINS PREDNR DEPENDENCIES AND SPECNR SPECIAL RESOURCES
The daily planning program was unable to create an operation record because it would be too large for the output data set defined by the EQQNCPDS DD statement.
The daily planning program terminates processing.
Reduce the number of dependencies or special resources for the failing application until all operations in the application can be saved in the new current plan data set. Resubmit the daily planning batch job.
EQQ2017W
AN OCCURRENCE WITH JOBNAME JOBNAME AND JOBNUMBER JOBNUMB FOR OPERATION OPNUM IS MISSING IN THE CURRENT PLAN RECORD TYPE 05 WITH INDEX NUMBER OCCNUM
The daily planning program was unable to find an index entry in the current plan record type 05 for the occurrence with the specified operation.
For occurrences that have been completed or deleted, the daily planning program takes the action defined by the VALEACTION parameter of the BATCHOPT statement. In other instances, the daily planning program is terminated with a return code of 08.
If no new plan is produced and the occurrence causing the problem is completed or deleted, resubmit the daily planning job with VALEACTION(W) specified in the BATCHOPT statement. In other instances, save the EQQDUMP output, create an APAR tape and contact the Software Support.
Refer to the data in the dump data set, EQQDUMP, to determine the cause of the error.
EQQ2018W
SPECIAL RESOURCE ERROR, REASON RSN
The daily planning program found an error when processing special resources.
The daily planning program takes the action defined by the VALEACTION parameter of the BATCHOPT statement.
If no new plan is produced, resubmit the daily planning job with VALEACTION(W) specified in the BATCHOPT statement. If a new plan has been created, use the HCL Workload Automation for Z panel to verify that the special resource and operations using the special resource are correct. The panel can be used to repair the inconsistency in the current plan or current plan extension records. Take a copy of the EQQDUMP. If VALEACTION(A) was specified, save the dump and contact the Software Support.
Contact your system programmer.
Refer to the data in the dump data set, EQQDUMP, to determine the cause of the error.
EQQ2019E
ADID: ADID, WS: WSID, OP: OPNO, JOBNAME: JOBNAME, IA: IAD1IAT1 HAS AN INVALID DEPENDENCY TO OPERATION ADID: ADI2, WS: WSI2, OP: OPN2, JOBNAME: JOBNAM2, IA: IAD2IAT2
The daily planning program found an invalid external dependency in an operation.
The daily planning program is terminated with a return code of 08 without creating a new current plan.
Use the Modify Current Plan panel to validate the external dependencies in the operation that is indicated first in the message.
EQQ2020W
AN INTERNAL CONDITIONAL PREDECESSOR IN OCCURRENCE APPLIADATEIATIME WAS NOT FOUND
The daily planning program was unable to find an operation record for an operation defined as an internal conditional predecessor to an operation in the occurrence defined by this message.
The daily planning program takes the action defined by the VALEACTION parameter of the BATCHOPT statement.
If no new plan is produced, resubmit the daily planning job with VALEACTION(W) specified in the BATCHOPT statement. If a new plan has been created, use the HCL Workload Automation for Z panel to verify that dependencies have been correctly created for the identified occurrence.
Refer to the data in the dump data set, EQQDUMP, to determine the cause of the error.
EQQ2021W
A CONDITIONAL SUCCESSOR TO OCCURRENCE APPLIADATEIATIME WAS NOT FOUND
The daily planning program was unable to find a conditional successor to the occurrence defined by this message.
The daily planning program takes the action defined by the VALEACTION parameter of the BATCHOPT statement.
If no new plan is produced, resubmit the daily planning job with VALEACTION(W) specified in the BATCHOPT statement. If a new plan has been created, use the HCL Workload Automation for Z panel to verify that dependencies have been correctly created for the identified occurrence. The panel can be used to repair the inconsistency in the current plan or long-term plan records. It may be necessary to delete and add again the successor occurrence or the identified occurrence. In some instances it may be sufficient to delete a successor specification.
Refer to the data in the dump data set, EQQDUMP, to determine the cause of the error.
EQQ2022E
NO CONDITION DEPENDENCY REFERRING TO CONDITIONAL PREDECESSOR APPL IADATE IATIME OPNUM WAS FOUND IN CONDITION COND FOR OPERATION OWNAP OWNIAD OWNIAT OWNOP.
While processing internal control blocks, the daily planning program was unable to find the indicated condition dependency.
The daily planning program ends without producing a new current plan.
Keep the EQQDUMP data and contact the Software Support.
Refer to the data in the dump data set, EQQDUMP, to determine the cause of the error.
EQQ2022W
NO CONDITION DEPENDENCY REFERRING TO CONDITIONAL PREDECESSOR APPL IADATE IATIME OPNUM WAS FOUND IN CONDITION COND FOR OPERATION OWNAP OWNIAD OWNIAT OWNOP.
While processing internal control blocks, the daily planning program was unable to find the indicated condition dependency.
The daily planning program tries to bypass detected errors. If the errors can be bypassed, the daily planning program produces a new current plan that might contain inconsistencies, for example unresolved dependencies.
If the daily planning program produced a new current plan, check the resulting data.
Refer to the data in the dump data set, EQQDUMP, to determine the cause of the error.
EQQ2023E
INCONSISTENT DEPENDENCY DATA BETWEEN OPERATIONS APPL IADATE IATIME OPNUM AND APP2 IADAT2 IATIM2 OPNU2.
While trying to add a default dependency, the daily planning program detected an inconsistent conditional dependency already present for the current operation.
The daily planning program ends without producing a new current plan.
Check for dependencies manually added to the LTP for the indicated occurrences and verify the original dependencies definition in the database.
EQQ2024E
CONDITION CONDID IN OPERATION OPERNR FOR APPLICATION APPLID IS TOO LARGE TO BE SAVED IN THE NEW CURRENT PLAN DATA SET.
A daily plan extend request failed because the record containing the all information on condition CONDID for application APPLID and operation number OPERNR is out of size.
The daily plan batch fails with RC=12 and message EQQ2024E is issued in MLOG.
Check that the amount of information about the condition dependencies contained in that specific condition does not make the condition record exceed the 32 KB size, which is the maximum size for a VSAM record. If it does, rework the condition to prevent the failure from occurring again.
EQQ2025E
TOO MANY USER FIELDS IN OPERATION OPERNR FOR APPLICATION APPLID .
A daily plan extend request failed, because the user field record for application APPLID and operation number OPERNR exceeds the maximum size.
The daily plan batch fails with RC=12 and message EQQ2025E is logged in MLOG.
Check that the number of user fields for the specified operation does not exceed the maximum limit.
EQQ3000W
DOMAIN DEFINITION DISCARDED FOR DOMAIN DOM1: THE DOMAIN MANAGER CPU1 BELONGS TO ANOTHER DOMAIN
User has defined two domains with the same workstation as domain manager..
One definition is discarded.
Review the domain definitions (DOMREC) in the topology member (for example, tplginfo) of EQQPARM, and then renew the symphony.
EQQ3001E
PARAMETER DOMAINPARENT MISSING IN TOPOLOGY INFORMATION MEMBER
In topology information member missing some DOMAINPARENT into DOMREC definition.
Review the domain definitions (DOMREC) in Topology Information Member (tplginfo) of EQQPARM and then Controller or Batch, depending on where you were.
EQQ3002E
THE DOMAIN DEFINITION IS INCORRECT: AT LEAST ONE DOMAIN MUST BE SPECIFIED
No domain definition has been specified in the topology member (for example, tplginfo) of EQQPARM, but some workstation definition (CPUREC) is present.
The symphony file is not produced.
You must add the needed domain definitions (DOMREC) in the topology member (ex.: tplginfo) of EQQPARM and then renew the symphony.
EQQ3003E
THE DOMAIN DEFINITION IS INCORRECT: AT LEAST ONE FIRST LEVEL DOMAIN MUST EXIST
No first level domains have been defined. This implies the presence of a loop in the network.
The symphony file is not created.
Eliminate the loop in the network to correct the domain definition and renew the symphony.
EQQ3004E
NO VALID DOMAIN MANAGERS OF FIRST LEVEL
User has defined at least a first level domain with a manager workstation that is not in the symphony.
The symhony file is not created..
Review the domain definitions and correct the domain manager. Then renew the symphony.
EQQ3005I
THE DOMAIN DEFINITION IS INCORRECT: THE MASTER DOMAIN BECOMES PARENT FOR DOMAIN DOM1
Domain DOM1 specifies a parent domain that does not exist.
The scheduler forces the master domain as parent.
If you do not want this domain to have the master domain as parent, review the domain definition, specify a valid domain parent, and renew the symphony.
EQQ3006I
THE WORKSTATION CANNOT BE ASSIGNED TO MASTERDM: WORKSTATION CPU1 ASSIGNED TO DOMAIN DOM1
User has defined workstation CPU1 as belonging to MASTERDM, but this is not allowed.
The scheduler forces the first level domain DOM1 as domain for CPU1.
If you do not want to assign CPU1 to
this domain, change its CPUREC
definition and then
renew the Symphony file.
EQQ3007W
DOMAIN DEFINITION DISCARDED FOR DOMAIN DOM1: DOMAIN MANAGER CANNOT BE THE MASTER DOMAIN MANAGER
User has defined a domain with the scheduler as domain manager workstation. This is not allowed.
The domain definition is discarded.
If you do not want this domain definition to be discarded, change the domain manager and renew the symphony..
EQQ3008I
DOMAIN MANAGER CPU1 MUST HAVE CPUTYPE SET TO FTA
A domain definition has specified as manager a workstation that has not the CPUTYPE parameter set to FTA.
The scheduler adjusts the definition to make the workstation a domain manager.
If you do not want this workstation to be a domain manager, find the domain definition that specifies it as manager, and insert a different workstation name then renew the symphony.
EQQ3009I
DOMAIN MANAGER CPU1 IS NOT IN FULLSTATUS: FULLSTATUS IS FORCED
Domain manager must be in fullstatus mode.
The scheduler forces fullstatus mode.
If you do not want this workstation to be a domain manager, find the domain definition that specifies it as manager, and insert a different workstation name then renew the symphony.
EQQ3010I
WORKSTATION CPU1 SPECIFIES AN INCORRECT DOMAIN NAME DOM1. THE DOMAIN IS CHANGED TO ITS HOST DOMAIN DOM2
The domain has not been specified in the CPUREC definition.
The scheduler forces as domain the DOM2, the host domain of CPU1.
If you do not want the CPU1 to belong to this domain, specify a correct domain name in the CPUREC definition and renew the symphony.
EQQ3011I
WORKSTATION CPU1 SET AS DOMAIN MANAGER FOR DOMAIN DOM1
This message states that CPU1 is set as domain manager for domain DOM1.
If you do not want CPU1 to be a domain manager, find the domain definition that specifies it as manager, and insert a different workstation name and renew the symphony.
EQQ3012W
DOMAIN DEFINITION DISCARDED FOR DOMAIN DOM1: DOMAIN MANAGER CPU1 NOT FOUND
The domain definition specifies a manager that is not in the symphony.
The domain definition is discarded.
- Change the specified domain definition by inserting a different CPU name.
- Add the CPU1 definition (CPUREC) in the Topology Member (ex: tplginfo) of EQQPARM and define the workstation in the workstation database.
EQQ3013I
EXTENDED OR STANDARD AGENT CPU1 DOES NOT SPECIFY HOST
The extended or standard agent CPUREC definition does not specify a host name.
The scheduler tries to set the domain manager of the CPU1 domain as host, or forces the domain manager of a first level domain..
If you do not want the CPU1 to be hosted by its domain manager or by a first level domain manager, change the specified CPUREC definition by inserting the desired host name and renew the symphony.
EQQ3014E
CIRCULAR REFERENCE BETWEEN DOMAINS DETECTED
A circular reference between domains has been detected.
The symphony file is not created.
Correct the domains definition by specifying valid parent domains then renew the symphony.
EQQ3015I
DOMAIN MANAGER CPU1 BECOMES HOST FOR CPU2
The extended or standard agent CPUREC definition does not specify a host name.
The scheduler forces as host the domain manager of the domain referenced in the CPUREC definition; if no domain is referenced, the domain manager of a first level domain is specified..
If you do not want this domain manager to host the workstation, change the specified CPUREC definition by inserting the desired host name and renew the symphony.
EQQ3016I
AGENT CPU1 NOW BELONGS TO DOMAIN DOM1 WITH DOMAIN MANAGER CPU2
A host for the agent is specified but the agent and the host workstations belong to different domains.
The scheduler forces the agent domain to the host domain.
If you do not want this workstation to belong to this domain, change the specified CPUREC definition by inserting the desired host name and renew the symphony.
EQQ3017I
CPU HCPU CANNOT HOST AGENT CPU1. AGENT CPU1 IS NOW HOSTED BY CPUM DOMAIN MANAGER IN DOMAIN DOM1
The CPUREC definition of the referred extended or standard agent CPU1 has incorrect info in the CPUHOST parameter: either a host name is specified for which no workstation does exist in the workstation database, or for this host name no CPUREC exists.
The scheduler forces the domain manager of the domain child of MASTERDM as host.
Update the CPUHOST value entered according to the criteria in the above explanation. Otherwise, the CPU1 agent will be hosted by CPUM in DOM1.
EQQ3018I
DOMAIN MANAGER CPU1 NOW HOSTS STANDARD AGENT CPU2
Standard agent CPU2 specifies a host that is not a domain manager.
The standard agent is re-hosted to the manager of its domain.
If you do not want this domain manager to host the workstation, change the specified CPUREC definition by inserting the desired host name and renew the symphony.
EQQ3019I
WORKSTATION CPU1 SPECIFIES AN INCORRECT DOMAIN NAME DOM1. WORKSTATION DOMAIN CHANGED TO THE FIRST LEVEL DOMAIN DOM2
The domain specified in the CPUREC definition does not exist or is not defined.
The scheduler forces as domain a first level domain.
If you do not want the workstation to belong to this domain, specify the right domain name in the CPUREC definition and renew the symphony.
EQQ3020I
IN CPU1 CPUREC DEFINITION THE DOMAIN IS FORCED TO DOM1
The CPU1 was selected to be the domain manager of the DOM1 domain, but its domain specification differs from DOM1.
DOM1 is forced.
If you do not want CPU1 to be the domain manager of DOM1 domain, change the domain manager name in the DOM1 definition and run the batch again.
EQQ3021E
CPUNAME KEYWORD IS MISSING
CPUREC statement was specified without a CPUNAME parameter.
The CPU parsing process ends.
In the EQQPARM member of topology information (for example, TPLGINFO), find the CPUREC statement without the CPUNAME parameter and specify a valid name for the CPU. This name must be the name of a fault-tolerant workstation present in the scheduler WS database. Restart Batch.
EQQ3022E
CPUNAME CPU1 IS NOT UNIQUE
CPUNAME parameter specifies a CPU name that already exists, but it must be unique.
The CPU parsing process ends.
In the EQQPARM member of topology information (for example, TPLGINFO), find the CPUREC statements with the CPUNAME value and delete the redundant CPU definitions. Alternatively, change the CPUNAME values. A valid name for a CPU is the name of a fault-tolerant workstation present in the scheduler WS database. Restart Batch.
EQQ3023E
CPUNAME CPU1 DOES NOT HAVE CPUOS KEYWORD SPECIFIED
CPUREC statement does not have CPUOS parameter.
The CPU parsing process ends.
In the EQQPARM member of topology information (for example, TPLGINFO), find the CPUREC statement with that CPUNAME value and add the CPUOS parameter. Restart Batch.
EQQ3024E
CPUNAME CPU1 DOES NOT HAVE CPUNODE KEYWORD SPECIFIED
The CPUREC statement does not have a CPUNODE parameter.
The CPU parsing process ends.
In the EQQPARM member of topology information (for example, TPLGINFO), find the CPUREC statement with that CPUNAME value and add the CPUNODE parameter. Restart Batch.
EQQ3025I
STANDARD AGENT CPU1 MUST HAVE HOST SPECIFIED
A CPUREC statement for a standard agent does not have CPUHOST parameter.
The scheduler uses either the manager of the domain child of MASTERDM or the manger of the domain eventually specified in the CPUDOMAIN parameter.
If you do not want this CPU to be the host or manager of the domain child of MASTERDM or of domain specified, change the CPU definition to specify a valid host name. Restart Batch.
EQQ3026I
ACCESS METHOD, FULLSTATUS AND RESOLVE DEPENDENCIES ATTRIBUTES ARE NOT COMPATIBLE FOR STANDARD AGENT TYPE CPU CPU1
A CPUREC statement for a standard agent does not support access method, fullstatus, and resolve dependencies.
Specifications are ignored.
Either delete the incorrect parameters from the CPUREC statement or change the CPU type, then restart Batch.
EQQ3027E
EXTENDED AGENT CPU1 MUST HAVE HOST AND ACCESS METHOD SPECIFIED
The CPUREC statement for an Extended Agent must have access method and host CPU specified.
The CPU parsing process continues.
Find theCPU1 definition in the topology information member and specify both the access method and the host where the method resides. If you do not specify this information correctly, the workstation will fail when trying to execute the access method. Renew the Symphony.
EQQ3028I
AUTOLINK, FULLSTATUS, RESOLVE DEPENDENCIES AND SERVER ATTRIBUTES ARE NOT COMPATIBLE FOR EXTENDED AGENT TYPE CPU CPU1
The CPUREC statement for an Extended agent does not support autolink, fullstatus, resolve dependencies, and server attributes.
Specifications are ignored.
Either delete the incorrect parameters from the CPUREC statement or change the CPU type. Renew the Symphony.
EQQ3029I
HOST AND ACCESS METHOD ATTRIBUTES ARE NOT COMPATIBLE FOR FTW TYPE CPU CPU1
The CPUREC statement for a fault-tolerant agent does not support host and access method attributes.
Specifications are ignored.
Either delete the incorrect parameters from the CPUREC statement or change the CPU type. Renew the Symphony.
EQQ3030I
DOMAIN MANAGER CPU1 MUST HAVE SERVER ATTRIBUTE SET TO BLANK
The CPUREC statement for a domain manager does not support the server attribute.
Specifications are ignored.
Either delete the incorrect parameter from the CPUREC statement or change the domain definition that specifies CPU1 as manager and renew the symphony.
EQQ3031E
HOST IS A REQUIRED ATTRIBUTE FOR EXTENDED AGENT CPU CPU1
The CPUREC statement for an Extended Agent must specify the host CPU. The CPU parsing process will end.
The CPU parsing process ends.
Find the CPU1 definition in the topology information member and specify both the access method and the host where the method resides. If you do not specify this information correctly, the workstation will fail when trying to execute the access method. Restart the Batch or the Controller.
EQQ3032E
DOMAIN KEYWORD IS MISSING
The DOMAIN parameter is missing from the DOMREC statement.
The Domains parsing process ends.
In the EQQPARM member of topology information (for example, TPLGINFO), find the DOMREC statements without the DOMAIN parameter and specify a valid name for the domain. Restart the Controller or Batch, as appropriate.
EQQ3033E
DOMAIN NAME DOM1 IS NOT UNIQUE
The DOMAIN parameter specifies a domain name that already exists, but it must be unique.
The domains parsing process ends.
In the EQQPARM member of topology information (for example, TPLGINFO), find the DOMREC statements without the DOMAIN parameter and delete the redundant Domain definitions, or change their DOMAIN values to be unique. Restart the Controller or Batch, as appropriate.
EQQ3034E
DOMAIN DOM1 MUST HAVE DOMAIN MANAGER SPECIFIED
The definition of domain DOM1 does not have a domain manager specified, but this is required.
The domains parsing process ends.
In the EQQPARM member of topology information (for example, TPLGINFO), add the name of the manager in the DOMMNGR parameter. Restart the Controller or Batch, as appropriate.
EQQ3036W
CPUREC DEFINES CPU CPU1 NOT FOUND IN THE WS DATABASE.
In the topology information member it was found a CPUREC definition for a CPU CPU1 that does not exist in the Host Workstation database.
No CPU will be added to the Symphony file for CPU1.
Verify that the CPUNAME info CPU1 entered in the referred CPUREC definition corresponds to a workstation that does exist in the Host Workstation database.
EQQ3037E
MISSING KEYWORD KEYWD OR VALUE NOT SPECIFIED IN STATEMENT STMT.
The required keyword is missing or incorrectly specified in the related statement.
The initialization of the server started task fails.
Check the statement and correct any syntax error.
EQQ3038E
A NEW SYMPHONY FILE ALREADY EXISTS
A previous batch job has created the Symphony successfully but NMM has not yet processed it.
The symphony creation fails.
Wait for the message EQQW090I in the controller log file. After that, you can run the batch job again. If the problem indefinitely persists, stop and restart the NMM task using the MODIFY command or restart the controller.
EQQ3039E
PREVIOUS SYMPHONY CREATION STEP NOT COMPATIBLE
The previous Symphony progress status is not compatible with the next, probably because an error has occurred in the meantime.
The Symphony creation fails.
If there are some messages explaining the error occurred, fix the problem and, if a valid CP exists, run Symphony refresh from Option 3.5. Consider that some error messages should be shown also in the data set corresponding to the DD SYSPRINT specified in the DP batch job. If the problem persists contact the Software Support.
EQQ3040E
WORKSTATION WSNAME NOT DEFINED IN TOPOLOGY INFORMATION MEMBER
Current Plan has a fault-tolerant workstation whose definition is missing in the topology information member.
The creation of Symphony fails.
If a valid CP exists, define the CPU in the topology information member (for example, TPLGINFO) of EQQPARM, and renew the Symphony.
EQQ3041W
TOPOLOGY INFORMATION MISSING: TEXT. THE TPLGYPRM KEYWORD IS MISSING OR INCORRECTLY SPECIFIED IN THE BATCHOPT STATEMENT.
The TPLGYPRM keyword of the TOPOLOGY statement in the topology parameters member (for example, TPGYPARM) is missing or incorrect.
TEXT can be either blank or WORKSTATION WSNAME REQUIRES IT.
Symphony creation fails.
Specify the topology information member of EQQPARM correctly and, if a valid CP exists, run Symphony Renew from Option 5.3.
EQQ3042E
JOB JOBNM IS ON WORKSTATION CPUNM THAT IS NOT PRESENT IN SYMPHONY FILE
- The CPUNM is not defined in the topology information member
OR:
- The CPUNM is defined, but has not been flagged as a fault-tolerant workstation in the scheduler WS database so it has not be added to Symphony.
Depending on where you are, Batch or Controller, the Symphony creation either fails or the occurrence operation is not added to the CP.
Define the workstation correctly in both the topology information member and the workstation database, then renew Symphony.
EQQ3043E
JOB JOBNM ON WORKSTATION CPUNM MUST SPECIFY ONE KEYWORD BETWEEN JOBSCR AND JOBCMD
The job definition JOBNM in EQQSCLIB must specify one, and only one of either the JOBSCR or JOBCMD parameters. Either these parameters are both missing or both present.
If you are running EQQSLCHK sample JCL, workstation field is filled with N/A (Not applicable), because the CPU name is not available for the sample.
- The creation of Symphony continues but the job is added in fail status.
- The addition of the operation fails.
- EQQSLCHK sample JCL continues parsing process.
Find the JOBNM definition in EQQSCLIB and correct the definition. Renew the Symphony if you were creating it, or add the occurrence again if you were using the MCP.
EQQ3044E
JOB JOBNM ON A CPU CPUNM SPECIFIES USER USRNM THAT IS NOT IN SYMPHONY
A job definition JOBNM specifies a WNT workstation, but the user USRNM for that workstation is bad defined in users information member (for example, USRINFO).
The job is added in the symphony file in Fail status, while in the current plan the operation remains in Started status.
Find the JOBNM definition in EQQSCLIB and correct the JOBUSR parameter value to specify an existing user. Renew the Symphony if you were creating it, or add the occurrence again if you were using the MCP. If you want to change the USRNM definition in users information member (for example, USRINFO), you must renew Symphony.
EQQ3045I
JOB JOBNM ON WORKSTATION CPUNM HAS NO JOBUSR KEYWORD SPECIFIED, THE DEFAULT ONE SPECIFIED FOR THE WORKSTATION IS USED
The job definition does not specify a user name. The default user specified for CPUNM will be used to execute the job.
If you are running EQQSLCHK sample JCL, workstation field is filled with N/A (Not applicable), because the CPU name is not available for the sample.
The job is added to the symphony file under the user name specified as the default for CPUNM.
EQQSLCHK sample JCL continues parsing process.
None.
EQQ3046I
TPLGYMEM KEYWORD IS NOT PRESENT IN TOPOLOGY MEMBER
The TOPOLOGY statement of the topology parameters member (for example, TPLGPARM) does not specify any topology information member name.
The default name TPLGINFO is used.
If the TPLGINFO member does not exist or does not contain valid topology information statements, some severe error will occur. If this is the situation, change the TOPOLOGY statement to specify a valid topology information name, and renew Symphony.
EQQ3047E
BINDIR KEYWORD MISSING IN TOPOLOGY MEMBER
BINDIR parameter is required.
The task ends.
Add the BINDIR parameter in the TOPOLOGY statement with a valid path name, then renew Symphony.
EQQ3048E
WRKDIR KEYWORD MISSING IN TOPOLOGY MEMBER
WRKDIR parameter is required.
The task ends.
Add the WRKDIR parameter in the TOPOLOGY statement with a valid path name, then renew Symphony.
EQQ3049I
USRMEM KEYWORD IS NOT PRESENT IN TOPOLOGY MEMBER
The USRMEM parameter is missing. This means that you are not using WNT fault-tolerant workstations.
If you are not using WNT fault-tolerant workstations, the Symphony creation process and WNT occurrence adding to CP fails.
- Define their user names and passwords in the users information member (for example, USRINFO) of EQQPARM
- Specify the parameter USRMEM in the TOPOLOGY statement, specifying the name of the member that contains the user information if you have not used the default member name USRINFO
- Renew Symphony
EQQ3050E
USRNAM KEYWORD IS MISSING
The USRREC statement requires the USRNAM parameter.
The task ends.
Find all the USRREC statements without the USRNAM parameter in the users information member of EQQPARM. Add valid users names in these definitions, and renew Symphony.
EQQ3051W
USER DEFINITION RECORD USER DOES NOT SPECIFY CPU OR CPU NAME CPUNM IS NOT CORRECT: THE USER IS NOT ADDED TO THE SYMPHONY FILE
In a USRREC statement, the USRCPU parameter is not specified or the CPU name specified in the parameter is not an existing CPU.
The task continues its processing, ignoring this record. This may impact the execution of Windows® jobs that need the specified user.
Add or correct the CPU CPUNM specified for the user USER.
Check the USRREC statements in the scheduler parameters to make sure that the CPU specified for the Windows users is correct.
EQQ3052E
INVALID C/PLX INTERFACE AREA
An incorrect memory area is passed by the PLX code to the C code.
The batch job does not produce the Symphony file.
Save the batch job message log and contact the Software Support.
Contact your system programmer.
EQQ3053E
FNM1: EFFECTIVE USERID NOT GOTTEN
The task is unable to get the UNIX System Services user IDfor the user that has executed the planning batch job.
The batch job does not produce the Symphony file.
Define a UNIX System Services user ID for the user.
Contact the system programmer to fix the problem and run Symphony Renew.
Check that the user that executed the batch job has a user ID defined for UNIX System Services.
EQQ3054E
FNM1: ALLOCATION OF HEADER RECORD FOR FILE SUF1 FAILED
The task is unable to allocate memory for the header record of Symphony file.
The batch job does not produce a Symphony file.
Increase the memory for the batch job, or correct any other discovered problem.
Contact the system programmer to fix the problem and run Symphony Renew.
The error is due to insufficient memory available to the task. Check what is preventing the task from obtaining memory.
EQQ3055E
FNM1: BUILDING OF HEADER RECORD FOR FILE SUF1 FAILED
The task is unable to build the symphony file.
The batch job does not produce a Symphony file.
Change the access mode of the work directory or provide the required rights to the user to allow them to write the new Symphony file.
Contact the system programmer to fix the problem and run Symphony Renew.
Check the batch job sysout and the system log to find possible system error messages referring to authorization problems. Check the access mode of the work directory (the one specified in WRKDIR parameter of the TOPOLOGY statement in the scheduler parameters) so that the user that is running the batch job is not prevented from writing in that directory.
EQQ3056E
FNM1: ACCESS ATTRIBUTES OF FILE SUF1 NOT CHANGED
The task is unable to set the access mode to the SUF1 Symphony file.
The batch job does not produce Symphony file.
Change the access mode of the work directory or provide the required rights to the user to allow them to write the new Symphony file.
Contact the system programmer to fix the problem and run Symphony Renew.
Check the batch job sysout and the system log to find possible system error messages referring to authorization problems. Check the access mode of the work directory, which is set in the WRKDIR parameter of the TOPOLOGY statement of the scheduler, to ensure that the user who is running the batch job is not prevented from writing in that directory.
EQQ3057E
FNM1: OPENING OF FILE SUF1 FAILED
The task is unable to open the SUF1 Symphony file.
The batch job does not produce Symphony file.
Set the access mode of the work directory or provide the required rights to the user to allow the user to write to the file.
Contact the system programmer to fix the problem and run Symphony Renew.
Check that the SUF1 file exists and that the user that is running the batch job has the correct rights to write to it.
EQQ3058E
FNM1: ADDING OF CPU RECORD CPU1 TO FILE SUF1 FAILED
The task is unable to put information for the CPU CPU1 in the SUF1 Symphony file.
The batch job does not produce Symphony file.
Set the access mode of the work directory or provide the required rights to the user to allow the user to write to the file. Alternatively, increase the free space on the file system according to the discovered problem.
Contact the system programmer to fix the problem and run Symphony Renew.
Check that the SUF1 file exists and that the user that is running the batch job has the correct rights to write to it. Check that there is sufficient free space on the file system.
EQQ3059E
FNM1: ADDING OF DOMAIN RECORD CPU1 TO FILE SUF1 FAILED
The batch job does not produce Symphony file.
Set the access mode of the work directory or provide the required rights to the user to allow the user to write to the file. Alternatively, increase the free space on the file system according to the discovered problem.
Contact the system programmer to fix the problem and run Symphony Renew.
Check that the SUF1 file exists and that the user that is running the batch job has the correct rights to write to it. Check that there is sufficient free space on the file system.
EQQ3060E
FNM1: READING FILE SUF1 FAILED: JOBSTREAM SCH1 NOT ADDED
The task is unable to read information for the SCH1 Job Stream from the SUF1 Symphony file as expected.
The batch job does not produce Symphony file.
Set the access mode of the work directory or provide the required rights to the user to allow the user to write to the file
Contact the system programmer to fix the problem and run Symphony Renew.
Check that the SUF1 file exists and that the user that is running the batch job has the correct rights to write to it.
EQQ3061E
FNM1: WRITING TO FILE SUF1 FAILED: JOBSTREAM SCH1 NOT ADDED
The task is unable to put information for the SCH1 Job Stream in the SUF1 Symphony file.
The batch job does not produce Symphony file.
Set the access mode of the work directory or provide the required rights to the user to allow the user to write to the file. Alternatively, increase the free space on the file system according to the discovered problem.
Contact the system programmer to fix the problem and run Symphony Renew.
Check that the SUF1 file exists and that the user that is running the batch job has the correct rights to write to it. Check that there is sufficient free space on the file system.
EQQ3062E
FNM1: ALLOCATION OF COMMON JOBSTREAM RECORD FAILED
The task is unable to allocate memory for the Job Stream record of Symphony file.
The batch job does not produce Symphony file.
Increase the memory for the batch job, or correct any other discovered problem.
Contact the system programmer to fix the problem and run Symphony Renew.
The error is due to insufficient memory available to the task. Check what is preventing the task from obtaining memory.
EQQ3063E
FNM1: ALLOCATION OF COMMON JOB RECORD FAILED
The task is unable to allocate memory for the Job record of the Symphony file.
The batch job does not produce Symphony file.
Increase the memory for the batch job, or correct any other discovered problem.
Contact the system programmer to fix the problem and run Symphony Renew.
The error is due to insufficient memory available to the task. Check what is preventing the task from obtaining memory.
EQQ3064E
FNM1: WRITING OF JOB RECORD JOB1 TO FILE SUF1 FAILED
The task is unable to put information for the JOB1 job in the SUF1 Symphony file.
The batch job does not produce Symphony file.
Set the access mode of the work directory or provide the required rights to the user to allow the user to write to the file. Alternatively, increase the free space on the file system according to the discovered problem.
Contact the system programmer to fix the problem and run Symphony Renew.
Check that the SUF1 file exists and that the user that is running the batch job has the correct rights to write to it. Check that there is sufficient free space on the file system.
EQQ3065E
FNM1: READING JOB RECORD JOB1 OF FILE SUF1 FAILED
The task is unable to read information for the JOB1 Job from the SUF1 Symphony file as expected.
The batch job does not produce Symphony file.
Set the access mode of the work directory or provide the required rights to the user to allow the user to write to the file.
Contact the system programmer to fix the problem and run Symphony Renew.
Check that the SUF1 file exists and that the user that is running the batch job has the correct rights to write to it.
EQQ3066E
FNM1: UPDATING JOB RECORD JOB1 OF FILE SUF1 FAILED
The task is unable to update information for the JOB1 job in the SUF1 Symphony file.
The batch job does not produce Symphony file.
Set the access mode of the work directory or provide the required rights to the user to allow the user to write to the file.
Contact the system programmer to fix the problem and run Symphony Renew.
Check that the SUF1 file exists and that the user that is running the batch job has the correct rights to write to it.
EQQ3067E
FNM1: UPDATING JOBSTREAM RECORD SCH1 OF FILE SUF1 FAILED
The task is unable to update information for the SCH1 job Stream in the SUF1 Symphony file.
The batch job does not produce Symphony file.
Set the access mode of the work directory or provide the required rights to the user to allow the user to write to the file.
Contact the system programmer to fix the problem and run Symphony Renew.
Check that the SUF1 file exists and that the user that is running the batch job has the correct rights to write to it.
EQQ3068E
FNM1: JOBSTREAM RECORD SCH1 NOT FOUND IN FILE SUF1
The task is unable to found information for the SCH1 job Stream in the SUF1 Symphony file.
The batch job does not produce Symphony file.
Set the access mode of the work directory or provide the required rights to the user to allow the user to write to the file.
Contact the system programmer to fix the problem and run Symphony Renew.
Check that the SUF1 file exists and that the user that is running the batch job has the correct rights to write to it.
EQQ3069E
FNM1: JOB RECORD JOB1 NOT FOUND IN FILE SUF1
The task is unable to find information for the JOB1 job in the SUF1 Symphony file.
The batch job does not produce Symphony file.
Set the access mode of the work directory or provide the required rights to the user to allow the user to write to the file.
Contact the system programmer to fix the problem and run Symphony Renew.
Check that the SUF1 file exists and that the user that is running the batch job has the correct rights to write to it.
EQQ3070E
FNM1: USER RECORD USR1 NOT ADDED TO FILE SUF1
The task is unable to put information for the USR1 NT user in the SUF1 Symphony file.
The batch job does not produce Symphony file.
Set the access mode of the work directory or provide the required rights to the user to allow the user to write to the file. Alternatively, increase the free space on the file system according to the discovered problem.
Contact the system programmer to fix the problem and run Symphony Renew.
Check that the SUF1 file exists and that the user that is running the batch job has the correct rights to write to it. Check that there is sufficient free space on the file system.
EQQ3071E
FNM1: FILE SUF1 NOT CLOSED OR COMMON AREA NOT RELEASED
The task is unable to update the last information in the SUF1 Symphony file.
The batch job does not produce Symphony file.
Set the access mode of the work directory or provide the required rights to the user to allow the user to write to the file. Alternatively, increase the free space on the file system according to the discovered problem.
Contact the system programmer to fix the problem and run Symphony Renew.
Check that the SUF1 file exists and that the user that is running the batch job has the correct rights to write to it. Check that there is sufficient free space on the file system.
EQQ3072E
FNM1: FILE SUF1 NOT RENAMED AS SNF1
The task is unable to rename the SUF1 Symphony file as SNF1.
The batch job does not produce Symphony file.
Change the access mode to the work directory or provide the required rights to the user to allow them to set the access mode of the new Symphony file. If SNF1 is already, present remove it.
Contact the system programmer to fix the problem and run Symphony Renew.
Check the access mode of the work directory, which is specified in the WRKDIR parameter of the TOPOLOGY statement of the scheduler, to ensure that the user that is running batch job can rename files in that directory. Check that SNF1 does not already exist.
EQQ3073E
INVALID FUNCTION REQUEST PASSED TO EQQZCEE
An incorrect function has been called by the PLX code to the C code.
The batch job does not produce Symphony file.
Save the batch job message log and contact the Software Support.
Contact your system programmer.
EQQ3075E
EQQSCLIB OPENING FAILED
The task is unable to open the PDS specified by EQQSCLIB DDNAME.
The batch job does not produce Symphony file.
Check that DDNAME EQQSCLIB is correctly defined and that the user that is executing the batch job can read the specified data set.
Contact your system programmer.
EQQ3076E
EQQSCLIB INVALID RECORD LENGTH
The task is unable to use the PDS specified by EQQSCLIB DDNAME because of an incorrect record length.
The batch job does not produce Symphony file.
Check that DDNAME EQQSCLIB is correctly defined and the specified data set is allocated. For details, refer to the Installation Guide.
Contact your system programmer to fix the problem and run Symphony Renew.
EQQ3077E
NO VALID JOB DEFINITION FOUND IN EQQSCLIB FOR JOB JB1NAM
The task finds a wrong job definition in EQQSCLIB for the indicated JB1NAM job.
- The creation of Symphony continues, but the job is added to the Symphony file in Fail status. In the CP file, at job run time, the status of the job will be Started, with extended status Waiting for submission.
- The addition of the operation fails.
Check for other messages explaining the error. Correct the JB1NAM member of EQQSCLIB definition. Renew the Symphony if you were creating it, or add the occurrence again if you were modifying the CP.
EQQ3078E
OCCURENCE OCC1 NOT FOUND IN EQQSCPDS
The task is unable to find the specified occurrence in the Current Plan.
The batch job does not produce a Symphony file.
Save the batch job message log and contact the Software Support.
Contact your system programmer.
EQQ3079W
NO OCCURENCES FOUND IN EQQSCPDS
The task is unable to find any occurrences in the Current Plan.
The batch job produces a Symphony file without jobs.
None.
EQQ3080I
PROCESS OF ADDING TOPOLOGY INFORMATION TO SYMPHONY HAS FAILED
A previous error prevents the task from producing the Symphony.
The batch job does not produce a Symphony file.
Examine previous errors.
EQQ3081E
EQQSCLIB CLOSING FAILED
An error has occurred closing the data set associated with the EQQSCLIB DDNAME.
The batch job continues its own processing.
None.
EQQ3082E
SYMPHONY JOB OP1NUM OF JOBSTREAM APP1TOK WITH NO CORRESPONDING RECORD IN EQQSCPDS
The task is unable to find the specified job in the Current Plan.
The batch job does not produce a Symphony file.
Save the batch job message log and VSAM data set associated with EQQSCPDS and contact the Software Support.
Contact your system programmer.
EQQ3083I
LOGLINES KEYWORD IS NOT PRESENT IN TOPOLOGY MEMBER THE DEFAULT VALUE IS USED
The LOGLINES parameter has been not specified in the TOPOLOGY statement.
The task continues its processing by using the default value for the parameter.
If a value different from the default is preferred, add the parameter to the statement.
EQQ3084W
LOGLINES KEYWORD IN TOPOLOGY MEMBER HAS AN IVALID VALUE SPECIFIED THE DEFAULT VALUE IS USED
The LOGLINES parameter in the TOPOLOGY statement has an incorrect value specified.
The task continues its processing by using the default value for the parameter.
Correct the value and rerun the task to use the selected value.
EQQ3085I
TRCDAYS KEYWORD IS NOT PRESENT IN TOPOLOGY MEMBER THE DEFAULT VALUE IS USED
The TRCDAYS parameter has been not specified in the TOPOLOGY statement.
The task continues its processing by using the default value for the parameter.
If a value different from the default is preferred, add the parameter to the statement.
EQQ3086W
TRCDAYS KEYWORD IN TOPOLOGY MEMBER HAS AN IVALID VALUE SPECIFIED THE DEFAULT VALUE IS USED
The TRCDAYS parameter in the TOPOLOGY statement has an incorrect value specified.
The task continues its processing by using the default value for the parameter.
Correct the value and rerun the task to use the selected value.
EQQ3087I
SYMNEW FILE HAS BEEN CREATED
The batch job has successfully created the Symphony file.
The task continues its own processing.
None.
EQQ3088E
THE SYMPHONY FILE HAS NOT BEEN CREATED
The batch job was unable to produce the Symphony file.
The task continues its own processing.
Check the daily plan batch mlog and controller mlog for other messages explaining the cause of the error and correct it. If a valid CP exists renew the symphony or run the batch again.
EQQ3089W
PORTNUMBER KEYWORD IN TOPOLOGY MEMBER HAS AN IVALID VALUE SPECIFIED THE DEFAULT VALUE IS USED
The PORTNUMBER parameter in the TOPOLOGY statement has an incorrect value specified.
The task continues its processing by using the default value for the parameter.
Correct the value and rerun the task to use the selected value.
EQQ3090I
PORTNUMBER KEYWORD IS NOT PRESENT IN TOPOLOGY MEMBER THE DEFAULT VALUE IS USED
The PORTNUMBER parameter has not been specified in the TOPOLOGY statement.
The task continues its processing by using the default value for the parameter.
If a value different from the default is preferred, add the parameter to the statement.
EQQ3091E
FAILED SYNCHRONIZATION WITH THE END-TO-END DISTRIBUTED ENVIRONMENT
The NMM task was not able to synchronize with the TWS distributed environment. There might be a communication problem between the controller and the server.
The NMM continues its processing and the Symphony creation will fail.
Verify that the Enabler tasks and the Server are active. If necessary restart either the Enabler or the Server and then try to recreate the Symphony file running a Daily Plan or a Symphony Renew batch job. If the Enabler and the Server are active, save the message log data set containing this error message and contact the Software Support.
EQQ3092I
CPUTYPE NOT SPECIFIED FOR CPUNAME CPU1 CPUTYPE CPUT IS USED
The CPUTYPE parameter was not specified in the topology definitions for the CPU identified in the message text. The CPUTYPE is set to the value shown in the message text.
The CPU parsing process continues.
None.
EQQ3093W
JOB JOBNM ON WORKSTATION CPUNM MUST SPECIFY ONE JOBREC STATEMENT ONLY. THE FIRST DEFINITION WILL BE USED.
The script definition of FTW job JOBNM contains more than one JOBREC statement. Only one JOBREC statement for member is allowed.
The Batch job continues processing using the definition contained in the first JOBREC statement in the member.
Correct the script definition using only one JOBREC statement. The script definition is contained in the JOBNM member of the PDS related to EQQSCLIB DDDEF.
EQQ3094I
CPULIMIT NOT SPECIFIED FOR CPUNAME CPU1 . THE DEFAULT VALUE IS USED
The parameter CPULIMIT was not used in the CPUREC statement for the fault-tolerant workstation CPU1.
The task continues processing using the default value for CPU limit.
If you want to limit the maximum jobs running simultaneously, add the CPULIMIT parameter in the CPUREC statement.
EQQ3095W
CPULIMIT KEYWORD FOR CPUNAME CPU1 HAS AN INVALID VALUE SPECIFIED THE DEFAULT VALUE IS USED
An invalid value has been specified in the CPULIMIT parameter in the CPUREC statement for fault-tolerant workstation CPU1
The task continuse processing using the default value for CPU limit.
Correct the value specified in the CPULIMIT parameter. If the error has been detected in a batch job launched to extend or replan the Current Plan or to refresh Symphony file, run a new refresh Symphony batch job to create a new Symphony containing the specified value.
EQQ3096E
THE EQQSCPDS DATA SET PROVIDED BY CONTROLLER IS NOT VALID
- Problems in data set defined by the EQQSCPDS DD-statement.
- Controller and server failed to syncronize.
The Symphony creation fails and the daily plan batch program ends in error.
Check the Controller message log to understand why the EQQSCPDS data set is not valid, in particular check for previous EQQN064E messages. Fix the problem and recreate the Symphony. If the cause of failure is a syncronization problem it could be better to wait a while before recreating the Symphony Renew to allow Translator to process all the events in data set specified by the EQQTWSOU DD-statement.
EQQ3097E
SOME DOMAINS SPECIFIED BUT NO WORKSTATIONS IN SYMPHONY FILE
No workstations have been added to the symphony file but some domain definitions (DOMREC) are present in the topology member (ex.: tplginfo) of EQQPARM.
The symphony file is not produced.
You must add the needed CPUREC definitions (CPUREC) in the topology member (ex: tplginfo) of EQQPARM, define the workstations in the workstation database, and renew the symphony.
EQQ3098W
THE TOPOLOGY IS IN USE: THE BATCH PROCESSING CANNOT BE PERFORMED IF THE CONTROLLER IS NOT AVAILABLE
The batch job detectedthat the controller is not active and the Topology member is specified in the batch options.
The batch job fails and no new CP plan nor Symphony file are created.
Restart the controller and re-submit the batch job.
EQQ3099E
THE REASON OF THE PREVIOUS ERROR IS: TXT
This error provides more detail on what caused the previous error and is issued when a system call failed for some reason.
Depends on the previous error.
Depends on the previous error.
EQQ3100I
CODEPAGE KEYWORD IS NOT PRESENT IN TOPOLOGY STATEMENT THE DEFAULT VALUE IS USED
The parameter CODEPAGE has not been specified in the Topology statement.
The task continues its processing by using the default value for the parameter.
If you prefer a value different from the default, add the parameter to the statement.
EQQ3101I
NUMJOB JOBS ADDED TO THE SYMPHONY FILE FROM THE CURRENT PLAN
During the processing of the daily plan NUMJOB jobs were added to the file.
TThe batch job continues its normal processing.
None.
EQQ3102I
CPUTZ NOT SPECIFIED FOR CPUNAME CPU1. THE DEFAULT VALUE IS USED
The parameter CPUTZ was not used in the CPUREC statement for the fault-tolerant workstation CPU1.
The task continues processing using the default value for the CPU timezone.
If you want to specify a timezone different from the default one, specify the CPUTZ parameter in the CPUREC statement.
EQQ3103E
FNM1: UNABLE TO LOAD TIMEZONE INFORMATION FOR TZ TIMEZONE UTC WILL BE USED FOR CPU CPU1
- An unsupported timezone has been specified.
- The BINDIR has been incorrectly specified.
- The file containing the timezone information cannot be accessed.
The batch program continues processing using UTC timezone for the workstation CPU1.
Check that the specified timezone is supported and that the BINDIR parameter of the TOPOLOGY statement specifies the correct directory.
EQQ3104I
E2E HOSTNAME NOT SPECIFIED, THE IP ADDRESS VALUE IS TAKEN FROM TCP/IP CONFIGURATION
The parameter HOSTNAME was not used in the Topology statement.
The task continues processing using the hostname that the operating system returns for the local machine.
If you want to specify an hostname different from the default one or you are experiencing problems connecting distributed agents to the controller, specify the parameter with the required value.
EQQ3105I
A NEW NCP WAS CREATED
A new current plan (NCP) was created during the creation, extension, or replanning of the daily plan.
The process continues.
None.
EQQ3106I
WAITING FOR SCP
Duing DP extent, DP replan or symphony Renew, the batch is waiting for SCP to start the Symphony file creation.
The process continues.
None.
EQQ3107I
SCP IS READY: START JOB ADDITION TO SYMPHONY FILE
During DP extend, DP replan or symphony Renew, the batch has been notified that the SCP VSAM data set is available so the addition of the jobs to the symphony file can start.
The process continues.
None.
EQQ3108I
JOBS ADDITION TO SYMPHONY FILE COMPLETED
During DP extend, DP replan or Symphony Renew, the batch has added all the jobs to the symphony file. The Symphony creation process can continue adding other definitions, for example the job dependencies or the user's definitions.
The process continues.
None.
EQQ3109E
MEMBER MEMBER NOT FOUND IN EQQSCLIB LIBRARY
There is no member named MEMBER in the EQQSCLIB library. This may not necessarily be an error: if the operation is defined as centralized, the EQQSCLIB member containing the job definition is optional.
- The creation of Symphony continues, but the job is added to the Symphony file in Fail status. In the CP file, at job run time, the status of the job will be Started, with extended status Waiting for submission.
- The addition of the operation fails.
Correct the problem in EQQSCLIB, then run Symphony Renew to create and distribute a correct Symphony file.
EQQ3110E
EQQSCLIB LIBRARY MEMBER MEMBER IS EMPTY
The member named MEMBER in EQQSCLIB does not contain any statements.
- The creation of Symphony continues but the job is added in fail status.
- The addition of the operation fails.
Correct the EQQSCLIB definition. Renew the Symphony if you were creating it, or add the occurrence again if you were modifying the CP.
EQQ3111E
I/O ERROR READING EQQSCLIB LIBRARY MEMBER MEMBER
An I/O error has prevented the task from parsing member MEMBER of EQQSCLIB.
- The creation of Symphony continues but the job is added in fail status.
- The addition of the operation fails.
Correct the EQQSCLIB definition. Renew the Symphony if you were creating it, or add the occurrence again if you were modifying the CP.
EQQ3112E
INVALID STATEMENT STMT IN EQQSCLIB LIBRARY MEMBER MEMBER
- A non-valid STMT statement.
- A non-valid STMT keyword in one of its statements.
- The creation of Symphony continues but the job is added in fail status.
- The addition of the operation fails.
Correct the EQQSCLIB definition. Renew the Symphony if you were creating it, or add the occurrence again if you were modifying the CP.
EQQ3113E
NO STMT STATEMENT IS PRESENT IN EQQSCLIB LIBRARY MEMBER MEMBER
Member MEMBER in EQQSCLIB does not contain the required STMT statement.
- The creation of Symphony continues but the job is added in fail status.
- The addition of the operation fails.
Correct the EQQSCLIB definition. Renew the Symphony if you were creating it, or add the occurrence again if you were modifying the CP.
EQQ3114E
IN STATEMENT STMT THE VALUE VALUE SPECIFIED FOR KEYWORD KEYWORD IS INVALID
An incorrect value for keyword KEYWORD in statement STMT was found while parsing a job definition.
- The creation of Symphony continues but the job is added in fail status.
- The addition of the operation fails.
Correct the EQQSCLIB definition. Renew the Symphony if you were creating it, or add the occurrence again if you were modifying the CP.
EQQ3115E
IN STATEMENT STMT RIGHT PARENTHESIS IS MISSING FOR KEYWORD KEYWORD
A syntax error for keyword KEYWORD in statement STMT was found while parsing a job definition. The left parenthesis that is before the keyword is not matched with a right parenthesis.
- The creation of Symphony continues but the job is added in fail status.
- The addition of the operation fails.
Correct the EQQSCLIB definition. Renew the Symphony if you were creating it, or add the occurrence again if you were modifying the CP.
EQQ3116E
IN STATEMENT STMT THE VALUE SPECIFIED FOR KEYWORD KEYWORD IS TOO LONG, MAX LENGTH IS LEN
An incorrect value for keyword KEYWORD in statement STMT was found while parsing a job definition. The value specified is too long, it cannot exceed LEN characters.
- The creation of Symphony continues but the job is added in fail status.
- The addition of the operation fails.
Correct the EQQSCLIB definition. Renew the Symphony if you were creating it, or add the occurrence again if you were modifying the CP.
EQQ3117E
IN STATEMENT STMT THE KEYWORD KEYWORD IS SPECIFIED TWICE
An error was found while parsing a job definition. Keyword KEYWORD in statement STMT was specified twice. A keyword can only be used once in a statement.
- The creation of Symphony continues but the job is added in fail status.
- The addition of the operation fails.
Correct the EQQSCLIB definition. Renew the Symphony if you were creating it, or add the occurrence again if you were modifying the CP.
EQQ3118E
THE STATEMENT STMT IS SPECIFIED TWICE
An error was found while parsing a job definition. Statement STMT was specified twice. A statement can only be used once in a job definition.
- The creation of Symphony continues but the job is added in fail status.
- The addition of the operation fails.
Correct the EQQSCLIB definition. Renew the Symphony if you were creating it, or add the occurrence again if you were modifying the CP.
EQQ3119I
CPUUSER NOT SPECIFIED FOR CPUNAME CPU1. THE DEFAULT VALUE IS USED
The CPUREC statement that defines the configuration of workstation CPU1 does not contain the CPUUSER parameter.
HCL Workload Automation for Z will use tws as the default user for the jobs scheduled on workstation CPU1. This value is used for operations that do not specify the user name in the job definition and, if they are centralized, do not use user exit 01 to set the user name.
If tws is not correct as the default user, specify the CPUUSER parameter in the CPUREC statement for workstation CPU1.
EQQ3120E
END-TO-END TRANSLATOR SERVER PROCESS NOT AVAILABLE
- The message can be issued during controller initialization if the server has not already started. In this case it is not an error.
- If the Event Manager is not active the Receiver starts waiting for it to become active - EQQW099I message with action = 'STARTED' is issued in the controller MLOG and the Receiver stops checking for the server availability. When the Event manager becomes active again - EQQW099I message with action = 'STOPPED' is issued in the controller MLOG - and the Receiver restarts checking for the server availability.
- The daily plan batch programs are interrupted.
- The controller keeps running.
If the message appears in the controller MLOG while the server is still initializing, wait a while for EQQZ193I message before checking for errors. Otherwise check for errors in the topology server, correct them and restart the server. Check in the controller MLOG for EQQZ193I message. If you receive the message EQQ3120E during a DP batch, after the EQQZ193I message is issued in the controller MLOG you can run the batch program again.
EQQ3121W
KEYWD KEYWORD IN STMT STATEMENT HAS AN INVALID VALUE SPECIFIED. THE DEFAULT VALUE IS USED
The value specified for keyword KEYWD in statement STMT is not correct.
The program will use the default value for keyword KEYWD.
Correct the value specified in statement STMT for keyword KEYWD to avoid receiving this warning message or if you want to use a different value than the default.
EQQ3122I
KEYWD KEYWORD IS NOT PRESENT IN STMT STATEMENT THE DEFAULT VALUE IS USED
Keyword KEYWD has not been specified in statement STMT.
The program will use the default value for keyword KEYWD.
Specify a value for keyword KEYWD in statement STMT if you do not want to use the default.
EQQ3123W
KEYWD KEYWORD FOR CPUNAME CPU1 HAS AN INVALID SPECIFIED VALUE. THE DEFAULT VALUE IS USED
The value specified for keyword KEYWD in the CPUREC statement for workstation CPU1 is not correct.
The program will use the default value for keyword KEYWD.
Correct in the CPUREC statement of CPU1 the value specified for keyword KEYWD to avoid receiving this warning message or if you want to use a different value than the default.
EQQ3124E
FNM1: INTERNAL ERROR WRITING SYMPHONY FILE
There was an internal error during the execution of the FNM1 routine called to build the symphony file. The next EQQ3099E message will display the reason of this error.
The batch job is interrupted.
If the problem persists, search the IBM Support database for a solution at Support.
EQQ3125W
RECOVERY STATEMENT IGNORED FOR CENTRALIZED SCRIPT JOBNM
The recovery statement in member JOBNM in EQQSCLIB will be ignored because job JOBNM is centralized.
The recovery statement is ignored.
Correct member JOBNM in EQQSCLIB to avoid the warning message.
EQQ3126W
KEYWORD JOBCMD/JOBSCR IGNORED FOR CENTRALIZED SCRIPT JOBNM
The JOBCMD and JOBSCR keywords in statement JOBREC of member JOBNM in EQQSCLIB will be ignored because job JOBNM is centralized.
Keywords JOBCMD and JOBSCR are ignored.
To avoid the warning message, correct theJOBREC definition in member JOBNM of EQQSCLIB.
EQQ3127E
DEPNR DEPENDENCIES DEFINED FOR OPERATION OPERNR IN APPLICATION APPL, IADATE, IATIME. THE INTERNAL, EXTERNAL AND PENDING PREDECESSORS NUMBER IS IPREDNR, EPREDNR AND PPREDNR RESPECTIVELY. SPECIAL RESOURCES SRYN.
- A predecessor operation.
- One or more special resources required by the operation. In this case, one dependency has to be considered regardless the number of required resources.
The daily planning batch process terminates. Neither the current plan nor the Symphony file are updated.
Decrease the number of dependencies specified for the operation in the AD file. Update the LTP accordingly and resubmit the daily planning job.
EQQ3128E
FNM1: UNABLE TO LOAD TIMEZONE INFORMATION FOR CONTROLLER. TIMEZONE UTC WILL BE USED FOR MASTER.
The value of TIMEZONE parameter is incorrect.
The scheduler uses the UTC value as default.
Correct the specified TIMEZONE value.
EQQ3129E
FNM1 PUTENV ENVVAR FAILED
While running the call PUTENV in module FNM1, an error occurred when a new environment variable ENVVAR was being added or the value of an existing environment variable was being changed. The environment variable contains the string used in the PUTENV call.
The program runs without this environment setting.
None.
EQQ3131I
WAITING FOR A CP BACKUP
The batch job is waiting for the backup of the current plan to complete.
Processing continues.
None.
EQQ3132I
CREATING A NEW CP
The daily planning job is creating a new current plan (NCP). The normal mode manager (NMM) controller subtask is waiting for the process to complete.
Processing continues.
None.
EQQ3133I
INITIALIZING A NEW SYMPHONY FILE (RUN NUMBER = RUNNO)
The daily planning job is creating and initializing the new Symphony file, based on the new current plan (NCP). The RUNNO value is the run number of this Symphony file.
The batch job updates the Symphony file with the records contained in the event files.
None.
EQQ3134E
AT LEAST ONE USER DEFINITION RECORD MUST BE SPECIFIED FOR WORKSTATION CPU
Workstation CPU is a WNT workstation, but not even a USRREC definition was specified for it.
The Symphony file is not created.
Create at least a USRREC definition for the workstation.
EQQ3135I
LIST OF OBJECTS
Loop analysis message, issued in the EQQLOOP data set together with message EQQ3136I or EQQ3137I. Possible values for objects are OCCURRENCES and OPERATIONS.
None.
None.
EQQ3136I
OCC ID: OCCURRENCE
Loop analysis message, issued in the EQQLOOP data set. It identifies the occurrence of the network when a loop type NO ENTRY POINT or NO EXIT POINT , or both, are detected and the loop analysis fails.
For each occurrence involved in the loop, one message EQQ3136I is issued.
EQQBATCH module terminates.
Examine the EQQLOOP data set and your network to identify bad dependencies.
The network might be corrupted.
EQQ3137I
OPER ID: OPERATION
Loop analysis message, issued in the EQQLOOP data set. It identifies the operation that was not checked in the network when a loop type SOME NODES COULD NOT BE CHECKED is detected and the loop analysis fails.
For each operation involved in the loop, one message EQQ3137I is issued.
EQQBATCH module terminates.
Examine the EQQLOOP data set and your network to identify bad dependencies.
The network might be corrupted.
EQQ3138E
THE NUMBER OF OCC NETWORK IDS BUILT SO FAR, REACHED ITS MAX ALLOWED VALUE (65535). PLAN ACTIVITY STOPS.
The planning activity stops, because the number of Occurrence Network IDs reached might generate a plan corruption.
- 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.
EQQ3139I
TIMEZONE KEYWORD IS NOT PRESENT IN TOPOLOGY STATEMENT
TIMEZONE parameter is missing in the TOPOLOGY statement.
The scheduler uses the UTC value as default.
Add the TIMEZONE parameter to avoid the informational message.
EQQ3140E
THE CPUHOST NAME IS NOT VALID. IT CAN BE EITHER 'OPCMASTER' OR HAVE A MAXIMUM LENGTH OF 4 CHARACTERS.
The name specified in the CPUHOST parameter of the CPUREC statement is longer than 4 characters. OPCMASTER is the only name that can exceed this limit. OPCMASTER can be used only for standard or fault-tolerant agents that are directly attached to the end-to-end server and belong to the MASTERDM domain.
The daily planning batch ends with RC=16.
Correct the name in the CPUHOST parameter.
EQQ3141I
WORKSTATION CPU IS IN MASTERDM DOMAIN AND CANNOT RESOLVE DEPENDENCIES. THE CPURESDEP PARAMETER WILL BE FORCED TO OFF.
In the CPUREC statement, you specified a fault-tolerant agent in the MASTERDM domain with the CPURESDEP parameter set to ON. Fault-tolerant agents in domain MASTERDM must have CPURESDEP set to OFF.
The value of the CPURESDEP parameter is forced to OFF.
Set CPURESDEP to OFF.
EQQ3142I
WORKSTATION CPU IS IN MASTERDM DOMAIN AND CANNOT BE FULLSTATUS. THE FULLSTATUS PARAMETER WILL BE FORCED TO OFF.
In the CPUREC statement you specified a fault-tolerant agent in the MASTERDM domain with the FULLSTATUS parameter set to ON. Fault-tolerant agents in domain MASTERDM must have FULLSTATUS set to OFF.
The value of the FULLSTATUS parameter is forced to OFF.
Set FULLSTATUS to OFF.
EQQ3143W
IN CPUREC DEFINITION OF WORKSTATION WSNAME THE CPULIMIT VALUE IS IGNORED BECAUSE IT DIFFERS FROM THE VALUE STORED IN THE CURRENT PLAN
The CPULIMIT parameter in the CPUREC statement for workstation WSNAME has a value different from the value stored in the current plan. The value in the current plan cannot be updated by simply running the Symphony Renew option, therefore the CPULIMIT is ignored and the value in the current plan is used to create the Symphony file.
None.
Extend or replan the current planning period
to have the CPULIMIT value applied, or use conman lc
to
dynamically change the value in the current plan.
EQQ3144E
THE CPUHOST FOR AN EXTENDED AGENT MUST BE AN EXISTING FAULT TOLERANT OR STANDARD AGENT
The CPUREC for an extended agent does not refer to an existing CPUHOST. No default values exist as host.
The processing is stopped. No symphony file is produced.
Correct the CPUREC definition for the extended agent and ensure that a workstation is defined to be used as default host (it must be either a standard agent, fault-tolerant agent, or domain manager).
EQQ3145E
WORKSTATION CPU1 BECOMES HOST FOR CPU2
An error in the CPUREC for workstation CPU2 was found. The CPUHOST value is reset to the default value CPU1.
The processing continues with the new CPUHOST value.
Correct the CPUREC definition for the workstation.
EQQ3146E
EXTENDED AGENT CPU1 HAS AN INCORRECT CPUHOST DEFINITION: CPUM
The CPUHOST for the extended agent was incorrectly specified. It was set either to OPCMASTER, a non-existent CPU, or another extended agent. An extended agent cannot use OPCMASTER or another extended agent as a host.
- The default first level domain manager and its domain exist
- The default fault tolerant agent and its domain exist
- The default standard agent and its domain exist
Correct the CPUREC definition for the workstation.
EQQ3147E
EXTENDED AGENT CPU1 HAS AN INCORRECT DOMAIN DEFINITION: DOM1
The CPUDOMAIN parameter for the extended agent either does not exist or does not coincide with the domain of the CPUHOST workstation.
- The defined CPUHOST and its domain, if it exists
- The default first level domain manager and its domain, if they exist
- The default fault tolerant agent and its domain, if they exist
- The default standard agent and its domain, if they exist
Correct the CPUREC definition for the extended agent.
EQQ3148I
CPUHOST CPU2 IS AN EXTENDED AGENT
This message is issued after message EQQ3146W, if an extended agent was specified as CPUHOST.
None.
None.
EQQ3149W
CPUHOST CPU1 HAS AN INCORRECT DOMAIN DEFINITION: DOM1
An extended agent did not specify the CPUDOMAIN parameter, but its CPUHOST has an incorrect value for it.
- The default first level domain manager and its domain exist
- The default fault tolerant agent and its domain exist
- The default standard agent and its domain exist
Correct the CPUREC definition for the workstation.
EQQ3150E
LOOP FOUND IN AN APPLICATION NETWORK:
- Loop type (no entry and/or exit point, some nodes could not be checked)
- Network ID
- Total number of operations in the network
- Total number of dependencies in the network
- Number of first operations (FOPs), that is operations with no predecessors
- Number of last operations (LOPs), that is operations with no successors
- Number of unchecked operations
- The first occurrence of the network (provided for debug reasons)
The current plan is not created or extended and the loop analysis is started.
Examine the EQQLOOP data set to discover the reasons of the loop and see the suggestions on how to resolve it.
EQQ3151I
LOOP REDUCTION ITERATION NN REDUCED LOOP TO MM OPERATIONS
Loop analysis message, issued in the EQQLOOP data set. The reduction process was iteratively performed by the loop analysis function and only the operations directly involved in the loop were left in the matrix representing the network. For details, refer to Managing the Workload.
The loop analysis function identifies the operations involved in the loop.
Examine the EQQLOOP data set.
EQQ3152I
ADID IADATE IATIME WSD OPNO JOBNM
- Application definition ID
- Input arrival date
- Input arrival time
- Workstation definition ID
- Operation number
- Job name
None.
None.
EQQ3153I
LOOP OPERATION: (ADID) IADATE IATIME WSD OPNO JOBNM
- Application definition ID
- Input arrival date
- Input arrival time
- Workstation definition ID
- Operation number
- Job name
For each operation involved in the loop, one message EQQ3153I is issued.
Details about the operation involved in the loop are provided.
Examine the EQQLOOP data set.
EQQ3154I
PREDECESSOR OF: (ADID) IADATE IATIME WSD OPNO JOBNM
Loop analysis message, issued in the EQQLOOP data set. It identifies a successor of the operation specified in message EQQ3153I.
Details about the operation involved in the loop are provided.
Examine the EQQLOOP data set.
EQQ3155I
SUCCESSOR OF: (ADID) IADATE IATIME WSD OPNO JOBNM
Loop analysis message, issued in the EQQLOOP data set. It identifies a predecessor of the operation specified in message EQQ3153I.
Details about the operation involved in the loop are provided.
Examine the EQQLOOP data set.
EQQ3156I
REMOVED DEPENDENCY: (ADID) WSD OPNO JOBNM IADATE IATIMEPREDECESSOR OF: (ADID) WSD OPNO JOBNM IADATE IATIMEREASON FOR REMOVAL: REASON
Loop analysis message, issued in the EQQLOOP data set. It indicates the dependency that was identified as being removed from the matrix representing the network, to resolve the loop. It also explains the reason for the removal according to the loop analysis that was done.
Possible values for the reason are: IA TIME CHECK, CLOSEST TO LOOP ENTRY, and MINIMAL NET DISTORTION. For details about the meaning of these values, refer to Managing the Workload.
The system tries to resolve the loop.
According to the information provided in this message, consider if you can actually remove the indicated dependency from your network and resolve the loop.
EQQ3157I
LIST OF INVOLVED APPLICATIONS SORTED BY LAST UPDATE IN AD ADID VALIDTO LASTUPD USER
- Application definition ID
- VALID TO date of the application definition
- Date and time of the last update made to the application definition
- The user who made the last update
None.
None.
EQQ3158I
LOOP ADID: ADID VALIDTODATE LASTUPDDATE LASTUPDTIME USR
- Application definition ID
- VALID TO date
- The date of the last update
- The time of the last update
- The user who made the last update
For each application involved in the loop, one message EQQ3158I is issued, in descending order according to the last update made to the application definitions.
Lists the applications involved in the loop, ordered by the last update date and time.
In the EQQLOOP data set, examine the applications that were listed, starting from the one that was modified most recently. The loop can be caused by recent changes made to the application definitions.
EQQ3159E
LOOP ANALYSIS FAILED: THE LIST OF OBJECTS IS AVAILABLE IN EQQLOOP
Loop analysis failed. Possible values for objects are OCCURRENCES and OPERATIONS. This message is issued in the EQQMLOG data set.
EQQBATCH module terminates.
Examine the EQQLOOP data set and your network to identify bad dependencies.
The network might be corrupted. Check the EQQLOOP data set to find detailed messages about the network.
EQQ3160E
EVENT DATASET WITH DDNAME = DDNAME CANNOT BE ACTION
The specified action could not be performed on the specified event data set. Possible values for ACTION are OPENED and READ. This message is issued in the EQQMLOG data set.
This action is skipped on the specified data set and job processing continues
Correct the error and restart the job.
Examine the EQQMLOG for other specific messages that indicate the cause of the problem
EQQ3161I
STATUS OF EVENT DATASET: DDNAME = DDNAME NUMBER OF RECORDS = RECNUM STATUS IS = STATUS UNPROCESSED EVENTS = RECNOT UNPROCESSED EVENTS % = PERCENTAGE
The message shows the following status information related to the event data set with DDNAME DDNAME:
- Number of records (excluding the header): RECNUM
- Status: STATUS
- Number of unprocessed event records: RECNOT
- Percentage of unprocessed events over total: PERCENTAGE
None.
None.
EQQ3162E
WRONG HEADER FOR EVENT DATASET WITH DDNAME = DDNAME
The header of the event data set with DDNAME DDNAME has inconsistent or unrecognized data. The data set cannot be used.
Job processing is interrupted.
Check that the event data set used is a valid TWSIN or TWSOU event data set. Correct the error and restart the job.
EQQ3163E
NETWORK LOOP DETECTED DURING BATCH DAILY PLAN
A loop was found in a network during the daily planning activity. This message is issued in the system log.
The current plan is not created or extended and the loop analysis is started.
Examine the EQQLOOP data set to find the reasons for the loop and suggestions on how to resolve it.
EQQ3164E
AN ERROR OCCURRED DURING NETWORK CONDITIONS VALIDATION PROCESS
A loop was found in a network during the daily planning activity. The inconsistent definition includes condition dependencies. This message is issued in the system log.
The current plan is not created or extended and the loop analysis is started.
Examine the EQQLOOP data set to find the reasons for the loop and suggestions on how to resolve it.
EQQ3166E
NO WS OPEN TIMES FOR PERIOD PER1 - PER2.
All workstations are closed during the period
of time extending from PER1 to PER2. The format of PER1 and PER2 is YYMMDD
HHHH
.
The daily planning program is terminated.
Use the Workstation Description panel or the Calendar panel to update the workstation open intervals.
EQQ3167E
BLANK INPUT ARRIVAL IN OCCURRENCE INDEX BLOCK.
While processing the index blocks for occurrences belonging to the old current plan, the daily plan batch detected a blank value in the IA time.
The daily planning program ends in error.
If the problem persists, search the IBM Support database for a solution at Support.
EQQ3168I
THE TOTAL NUMBER OF CURRENTLY IDENTIFIED OCC NETWORKS IS MNETIDOC
Processing continues.
- 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.
EQQ3169I
THE NUMBER OF OCC NETWORK IDS BUILT SO FAR REACHED 80% OF THE MAX ALLOWED VALUE
Processing continues.
- 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.
EQQ4010E
RECOVERY JOB OF JOB JOBNM IS ON WORKSTATION CPURE THAT IS NOT PRESENT ON SYMPHONY FILE
- The workstation is not defined in the topology information member.
- The workstation is defined, but has not been flagged as a fault-tolerant workstation in the scheduler database.
- The creation of Symphony continues but the job is added in fail status.
- The addition of the operation fails.
Correct the EQQSCLIB definition. Renew the Symphony if you were creating it, or add the occurrence again if you were modifying the CP.
EQQ4011I
RECOVERY JOB OF JOBNM CANNOT USE KEYWORD MESSAGE IF RECOVERY OPTION IS STOP
The recovery statement (JOBREC) in member JOBNM in EQQSCLIB cannot specify the parameter MESSAGE if the recovery option is STOP. It is not possible to use recovery option STOP with recovery action prompt reply.
The MESSAGE parameter is ignored.
To avoid the warning message, correct the JOBREC definition in member JOBNM in EQQSCLIB.
EQQ4012E
RECOVERY JOB OF JOBNM SPECIFIES USER USRRE THAT IS NOT IN SYMPHONY
The recovery statement (JOBREC) in member JOBNM in EQQSCLIB specifies a non-valid user name USRRE for the recovery job. The user name must be defined on the in the PARMLIB in the users information member (for example, USRINFO)..
Depending on where you are, Batch or controller, you can have one of the following situations:
- The creation of Symphony continues but the job is added in fail status.
- The addition of the operation fails.
Correct the JOBREC definition in member JOBNM in EQQSCLIB. Renew the Symphony if you were creating it, or add the occurrence again if you were modifying the CP.
EQQ4013E
RECOVERY JOB OF JOBNM MUST SPECIFY ONE KEYWORD BETWEEN JOBSCR AND JOBCMD
The recovery statement (JOBREC) in member JOBNM in EQQSCLIB must specify one of either the JOBSCR or JOBCMD parameters. The two parameters are both either missing or present.
Depending on where you are, Batch or controller, you can have one of the following situations:
- The creation of Symphony continues but the job is added in fail status.
- The addition of the operation fails.
Correct the JOBREC definition in member JOBNM in EQQSCLIB. Renew the Symphony if you were creating it, or add the occurrence again if you were modifying the CP.
EQQ4014I
RECOVERY JOB OF JOBNM HAS NO JOBUSR KEYWORD SPECIFIED, THE DEFAULT ONE SPECIFIED FOR CPU CPURE IS USED
The JOBUSR keyword is missing from the recovery statement (JOBREC) in member JOBNM in EQQSCLIB. The default one specified for CPU CPURE in the CPUREC statement will be used in its place.
Depending on where you are, Batch or controller, the creation of Symphony or the addition of the operation continues by automatically setting the user with the default value.
To use a different value, you must add the JOBUSR parameter in script JOBNM and renew the Symphony.
EQQ4015I
RECOVERY JOB OF JOBNM HAS NO JOBWS KEYWORD SPECIFIED, THE WORKSTATION CPUNM OF JOB JOBNM IS USED
The JOBWS parameter is missing from the recovery statement (JOBREC) in member JOBNM in EQQSCLIB. The workstation defined for job JOBNM will be used in its place.
If you are running EQQSLCHK sample JCL, workstation field is filled with N/A (Not applicable), because the CPU name is not available for the sample.
- The creation of Symphony or the addition of the operation continues by automatically setting the workstation to CPUNM.
- EQQSLCHK sample JCL continues parsing processing.
If you want to specify a different recovery job workstation than the workstation of the job to recover, you must add the JOBWS parameter in script JOBNM and renew the Symphony.
EQQ4016W
JOB JOBNM HAS NO RECOVERY JOB: JOBUSR, JOBWS, INTERACTV, RCCONDSUC, RECOVERY STATEMENT KEYWORDS WILL BE IGNORED
In RECOVERY statement in member JOBNM in EQQSCLIB, there are no JOBCMD or JOBSCR parameters: JOBNM has no recovery job then JOBUSR, JOBWS, INTERACTV, and RCCONDSUC recovery statement parameters will be ignored.
Depending on where you are, Batch or controller, the creation of Symphony or the addition of the operation continues.
If you want to define a recovery job for JOBNM, add JOBCMD or JOBSCR to the recovery statement and renew the Symphony.
EQQ4017E
FNM1: WRITING OF PROMPT RECORD FOR JOB JOB1 TO FILE SUF1 FAILED
The task is unable to put information for the prompt record of JOB1 job in the SUF1 Symphony file.
The creation of the Symphony fails.
Depending on the user problem do one or more of the following operations:
- Set the access mode of the work directory or provide the required rights to the user to allow the user to write to the file.
- Increase the free space on the file system.
Check that the SUF1 file exists and that the user that is running the batch job has the correct rights to write to it. Check that there is sufficient free space on the file system. Contact the system programmer and renew the Symphony.
EQQ4018E
JOB JOBNM: RCCONDSUC VALUE LENGTH NOT ALLOWED REC
In member JOBNM in EQQSCLIB, in JOBREC/RECOVERY statement the length of RCCONDSUC value is not allowed because the length of RCCONDSUC plus the length of JOBSCR/JOBCMD is greater than 4095.
Depending on where you are, Batch or Controller:
— The Symphony creation continues but job is added in fail status
— Operation adding fails.
Correct JOBREC/RECOVERY definition in member JOBNM in EQQSCLIB: you can change RCCONDSUC or JOBSCR/JOBCMD value. Renew Symphony if you were creating it, or add the occurance again if you were modifying the CP.
EQQ4019E
JOB JOBNM RCCONDSUC VALUE NOT VALID. RSN: REASON
- Unbalanced parenthesis
- Invalid operation
- Invalid expression
- Invalid operand
- The symphony creation continues but job is added in fail status
- Operation adding fail
Correct the RCCONDSUC value.
- Renew Symphony
- Add the operation again
EQQ4020E
MISPLACED VARSUB STATEMENT IN JOB JOBNM ON WORKSTATION CPNUM
The VARSUB statement was inserted incorrectly in the member JOBNM of the SCRIPTLIB. The VARSUB statement must always be in the first position.
The creation of Symphony continues, but the job is added in fail status.
Check and correct the position of the VARSUB statement in the JOBNM member of SCRIPTLIB.
Renew the Symphony if you were creating it, or add the occurrence again if you were modifying the CP.
EQQ4021E
UNDEFINED VARIABLE VAR IN SCTN SCRIPT
The SCTN definition of the EQQSCLIB library specifies the VAR variable which is neither predefined by the scheduler nor appears in a JCL variable table of the scheduler database.
- The creation of Symphony continues, but the job is added in fail status.
- The addition of the operation fails.
Correct the SCTN definition or define the VAR variable in a JCL variable table of the scheduler database. Renew the Symphony or request to add the occurrence using the panel interface again.
EQQ4022E
VALIDATION ERROR IN SCRIPT SCTN. VALUE IS REQUIRED FOR THE VARIABLE VAR BUT IS DEFINED AS BLANK
The variable substitution exit setting of the VAR variable might be set to blank.
The creation of Symphony or the addition of the operation fails.
Change the Exit process or use the panel interface to modify the variable specification. Renew the Symphony or request to add the occurrence using the panel interface again.
EQQ4024E
INVALID VARIABLE VAR IN SCRIPT SCTN
The name of a variable can contain from one to eight alphanumeric characters. The first character must be alphabetic.
The creation of Symphony or the addition of the operation fails.
Correct the script. Renew the Symphony or request to add the occurrence using the panel interface again.
EQQ4025E
RECURSIVE SUBSTITUTION IN SCRIPT SCTN
The value of a variable depends on the values of other variables, which in turn depend on its value. No value can be determined for this variable
If the job is an end-to-end job with fault-tolerant capabilities, then the creation of Symphony or the addition of the operation fails. If the job is a job with advanced options, the current operation status is set to ended-in-error with error code OJCV.
Examine the tables and variable definitions. Correct them to eliminate the closed translation loop. If the job is an end-to-end job with fault-tolerant capabilities, renew the Symphony or request to add the occurrence using the panel interface again. If the job is a job with advanced options, resubmit the job.
EQQ4026I
INTRACTV KEYWORD IGNORED FOR JOB JOBNM ON WORKSTATION CPNM
The JOBNM definition of EQQSCLIB library specifies the INTRACTV parameter in the JOBREC or RECOVERY statements. This parameter is ignored because is supported on Windows workstations only.
None.
None.
EQQ4027E
UNDEFINED VALUE FOR DEPENDENT VARIABLE VAR IN SCRIPT SCTN
The independent variable is currently set to a value that is not included in the dependency value list of the dependent variable.
- The creation of Symphony continues, but the job is added in fail status.
- The addition of the operation fails.
Check and correct the variable definitions. Renew the Symphony or request to add the occurrence using the panel interface again.
EQQ4028W
BLANK VALUE FOR VARIABLE VAR IN SCRIPT SCTN
Data not found in the Extended Info field in the Current Plan operation record.
Processing continues.
Before resubmitting the operation, check the current value of the operation Extended Info field in the Current Plan.
EQQ4029E
TRUNCATION OCCURRED DURING VARSUB IN SYSTEM AUTOMATION COMMAND FOR APPLICATION ADID WITH INPUT ARRIVAL IADATE, IATIME AND OPERATION NUMBER OPNO
The variable substitution caused the system automation command text to exceed its maximum length (255 bytes). The operation is identified by the owning application ID, operation input arrival date and time, and operation number.
The variable substitution in the system automation command fails. If the SAVARFAIL parameter is set, the system automation operation ends in error with code OJCV.
Check the command text and the variables used. Change the variables to correct the error or make the variable definition available. Request to add the occurrence using the dialog interface again.
EQQ4031W
EQQSCLIB IS EMPTY
All data sets associated with the EQQSCLIB ddname are empty.
None.
None.
EQQ4032E
RECOVERY JOB OF JOB JOBNM IS ON WORKSTATION CPURE THAT IS NOT PRESENT IN FAULT TOLERANT WORKSTATION DEFINITIONS
The recovery statement in member JOBNM in EQQSCLIB specifies a workstation CPURE that is not defined in the topology information member (for example, TPLGINFO).
None.
Define either the workstation CPURE in the topology information member (for example, TPLGINFO) of EQQPARM, or the correct workstation in the JOBWS parameter for member JOBNM in SCRIPTLIB.
EQQ4033I
PROCESSED JOB JOBNM IN CONCNUM CONCATENATED SCRIPT LIBRARY
Job JOBNM processed from EQQSLCHK sample JCL is defined in the script library CONCNUM of the EQQSCLIB DDNAME.
None.
None.
EQQ4034E
RECURSIVE SUBSTITUTION IN SYSTEM AUTOMATION COMMAND TEXT FOR APPLICATION ADID WITH INPUT ARRIVAL IADATE, IATIME AND OPERATION NUMBER OPNO
The value of a variable depends on the values of other variables, which in turn depend on its value. No value can be determined for this variable. The operation is identified by the owning application ID, operation input arrival date and time, and operation number.
The variable substitution in the system automation command fails. If the SAVARFAIL parameter is set, the system automation operation ends in error with code OJCV.
Examine the tables and variable definitions. Correct them to eliminate the closed translation loop and submit the command again.
EQQ4035E
UNDEFINED VALUE FOR DEPENDENT VARIABLE VAR IN SA COMMAND FOR APPLICATION ADID WITH INPUT ARRIVAL IADATE, IATIME AND OPERATION NUMBER OPNO
The independent variable is currently set to a value that is not included in the list of dependency values related to the dependent variable. The operation is identified by the owning application ID, operation input arrival date and time, and operation number.
The variable substitution in the system automation command fails. If the SAVARFAIL parameter is set, the system automation operation ends in error with code OJCV.
Check the contents of the variable definitions. Correct them and request to add the occurrence again.
EQQ4036E
VARIABLE VAR NOT VALID IN SYSTEM AUTOMATION COMMAND TEXT FOR APPLICATION ADID WITH INPUT ARRIVAL IADATE, IATIME AND OPERATION NUMBER OPNO
The variable used in the command text is not valid. The name of a variable can contain from 1 to 8 alphanumeric characters, and the first character must be alphabetic. The operation is identified by the owning application ID, operation input arrival date and time, and operation number. The variable in error is shown.
The variable substitution in the system automation command fails. If the SAVARFAIL parameter is set, the system automation operation ends in error with code OJCV.
Check the contents of the variable definitions. Correct them and request to add the occurrence again.
EQQ4037E
BLANK VALUE FOR VARIABLE VAR IN SA COMMAND TEXT FOR APPLICATION ADID WITH INPUT ARRIVAL IADATE, IATIME AND OPERATION NUMBER OPNO
Data not found for the variable VAR. The operation is identified by the owning application ID, operation input arrival date and time, and operation number.
The variable substitution in the system automation command fails. If the SAVARFAIL parameter is set, the system automation operation ends in error with code OJCV.
Before resubmitting the operation, check the current value for the variable of the operation.
EQQ4038E
VALIDATION ERROR FOR REQUIRED VARIABLE VAR IN SA COMMAND FOR APPLICATION ADID WITH INPUT ARRIVAL IADATE, IATIME AND OPERATION NUMBER OPNO
The variable substitution exit could set the variable VAR to blank.
The variable substitution in the system automation command fails. If the SAVARFAIL parameter is set, the system automation operation ends in error with code OJCV.
Change the exit process or use the dialog interface to modify the variable specification of the operation. Request to add the occurrence again.
EQQ4039E
UNDEFINED VARIABLE VAR IN SYSTEM AUTOMATION COMMAND TEXT FOR APPLICATION ADID WITH INPUT ARRIVAL IADATE, IATIME AND OPERATION NUMBER OPNO
The variable used in the system automation command text was not found. The operation is identified by the owning application ID, operation input arrival date and time, and operation number.
The variable substitution in the system automation command fails. If the SAVARFAIL parameter is set, the system automation operation ends in error with code OJCV.
Check the command text and the variables used. Change the variables to correct the error or make the variable definition available. Request to add the occurrence using the dialog interface again.
EQQ4040E
INCOHERENT DATA IN EQQWSDS. SOME DESTINATIONS RESULT DEFINED WITHOUT A VIRTUAL WORKSTATION. WSNAME: WSNAME.
An internal error occurred in the workstation definition. Some records result as being defined for destinations but no virtual workstation record with that name are defined in the data base.
DP batch ends in error with return code 12.
Contact the Software Support.
EQQ9970E
THE MAXSTNUM KEYWORD SPECIFIES A VALUE THAT IS NOT RANGE 1 - 9999 (NUMBER OF OPERATIONS)
The value set for MAXSTNUM in the JTOPTS statement is outside of the allowed range.
Parsing of the initialization parameters stops.
Modify the MAXSTNUM setting. Valid values are in the range 1-9999 jobs. The default value is 1000.
EQQ9971E
THE MAXSTWAIT KEYWORD SPECIFIES A VALUE THAT IS NOT RANGE 1 - 90 (MINUTES)
The value set for MAXSTWAIT in the JTOPTS statement is outside of the allowed range.
Parsing of the initialization parameters stops.
Modify the MAXSTWAIT setting. Valid values are in the range 1-90 minutes. The default value is 10.
EQQ9972E
THE SMOOTHSUBCONFLEVEL KEYWORD SPECIFIES A VALUE THAT IS NOT IN THE RANGE 0 – 5
The value set for SMOOTHSUBCONFLEVEL in the JTOPTS statement is outside of the allowed range.
DP batch ends with return code 16, and the parsing of the initialization parameters stops.
Modify the SMOOTHSUBCONFLEVEL setting. Valid values are in the range 0-5.
EQQ9974E
INVALID OPTION VALUE FOR OCCURRENCE NUMBER LIMIT
The value of the occurrence number limit is invalid.
The job is terminated.
Check the input parameters and resubmit the job.
EQQ9975E
EQQ9977E
EQQ9979E
EQQ9980E
OPEN FAILED FOR PARMLIB DATA SET
The batch program could not open the parameter library (EQQPARM) data set.
The job is terminated.
Check and correct the EQQPARM DD statement in the JCL and resubmit the job.
EQQ9981E
BATCHOPT PARAMETER NOT FOUND
The batch program could not find the BATCHOPT initialization statement in the data set specified in the EQQPARM DD statement.
The job is terminated.
Check and correct the EQQPARM DD statement in the JCL and resubmit the job.
EQQ9985E
INVALID OPTION VALUE FOR DP ALGORITHM
The value of the DP algorithm (DPALG) option in the BATCHOPT statement is invalid.
The job is terminated.
Specify a valid option value. Refer to Customization and Tuning for more information.
EQQ9988I
DB2SYSTEM DB2SYS IS NOT AVAILABLE
The DB2 system specified in the DB2SYSTEM keyword of the BATCHOPT statement is not started, has been stopped, or has abended, or the specified name is incorrect.
The daily planning program continues processing, but no operations are inserted into the history database.
Check the reason for the failure and correct the problem.
EQQ9989E
DB2 MODULE DB2MOD LOAD FAILED
DB2 module DB2MOD failed to load during the daily planning batch run.
The daily planning batch job is terminated.
Check the reason for the failure and correct the problem.