EQQCP00 - EQQCP27
EQQCP00I
CRITICAL JOB TABLE DATA SPACE HAS BEEN CREATED. SIZE PAGES ARE USED FOR NUM JOB ENTRIES RECORDS.
The scheduler successfully created a data space for a critical job table. SIZE shows the number of pages (each 4096 bytes) used to create the data space. NUM shows the maximum number of job entries that the data space can contain. The scheduler uses a minimum of 20 pages.
Normal processing continues. The scheduler uses the data space when accessing the critical job table.
None.
EQQCP01E
CRITICAL JOB TABLE DATA SPACE CREATION FAILED. REASON CODE IS RSN.SIZE PAGES WERE REQUESTED FOR NUM JOB ENTRIES RECORDS.
The scheduler could not create a data space for critical job table storage. Reason code RSN is set by the DSPSERV service. SIZE shows the number of pages (each 4096 bytes) that the scheduler needed. NUM shows the number of job entries that the scheduler requested to store in the data space.
The normal mode manager (NMM) ends.
Correct the error and restart the NMM subtask.
Use the reason code RSN from DSPSERV to determine the cause of the error. Refer to the z/OS documentation that describes DSPSERV reason codes.
EQQCP02E
CRITICAL JOB TABLE DATA SPACE DELETED FAILED. REASON CODE IS RSN
The scheduler could not delete the data space. reason code RSN is set by the DSPSERV service.
Normal process continues.
Correct the error and, if necessary restart the subtask that encountered the error.
Use the reason code RSN from DSPSERV to determine the cause of the error. Refer to the z/OS documentation that describes DSPSERV reason codes.
EQQCP03I
CRITICAL JOB TABLE DATA SPACE HAS BEEN SUCCESSFULLY DELETED.
The scheduler successfully deleted a data space for a critical job table.
Normal processing continues.
None.
EQQCP04E
CRITICAL JOB TABLE DATA SPACE EXTENSION FAILED. REASON CODE IS RSN
The scheduler could not extend the data space. reason code RSN is set by the DSPSERV service.
Normal process continues.
Correct the error and, if necessary restart the subtask that encountered the error.
Use the reason code RSN from DSPSERV to determine the cause of the error. Refer to the z/OS documentation that describes DSPSERV reason codes.
EQQCP05I
CRITICAL JOB TABLE DATA SPACE HAS BEEN EXTENDED. SIZE ARE USED FOR NUM JOB ENTRY RECORDS.
The scheduler successfully extended a data space for a critical job table. SIZE shows the number of pages (each 4096 bytes) to which the data space was extended. NUM shows the maximum number of job entries that the data space can contain.
Normal processing continues. The scheduler uses the data space when accessing the critical job table.
None.
EQQCP06E
UNSUCCESSFUL DATA SPACE ACCESS REQUEST, INFORMATION FOLLOWS: ACCESS REQUEST IS FROM MODID , REASON CODE IS RSN , REQUESTED FUNCTION IS FUNC , INDEX NUMBER IS INDEX.
A scheduler subtask encountered an unexpected error when accessing the critical job table data space.
The messages that follow this message in the scheduler message log indicate the action taken by the scheduler subtask.
Correct the error and, if necessary, restart the subtask that encountered the error.
EQQCP10I
THE CRITICAL PATH HANDLER TASK HAS STARTED.
The critical path handler successfully completed the initialization phase.
The critical path handler processing starts.
None.
EQQCP11I
THE CRITICAL PATH HANDLER TASK HAS ENDED.
The critical path handler ended processing normally.
The critical path handler processing ends.
None.
EQQCP12E
THE CRITICAL PATH HANDLER TASK HAS ENDED DUE TO PROCESSING ERRORS.
The critical path handler cannot continue processing because of a severe error.
The critical path handler processing ends.
Correct the errors and restart the critical path handler. If the problem persists, for the information to collect, see the Diagnosis Guide and Reference, "Problem analysis procedures" section.
Review previous messages in the scheduler message log.
EQQCP13E
THE CRITICAL PATH HANDLER TASK HAS IGNORED THE FOLLOWING QUEUE ELEMENT REQUEST
The critical path handler cannot continue processing because of a severe error.
The critical path handler processing ends.
Collect the documentation listed in Diagnosis Guide and Reference, "Problem analysis procedures" section. Restart the critical path handler.
Review previous messages in the scheduler message log.
EQQCP14E
A SEVERE ERROR IN THE CRITICAL PATH HANDLER TASK HAS CAUSED ONE OR MORE DQES TO BE LOST
The critical path handler lost some requests.
The critical path handler will try to continue the process.
Collect the documentation listed in Diagnosis Guide and Reference, "Problem analysis procedures" section. Restart the critical path handler.
Review previous messages in the scheduler message log.
EQQCP15E
THE CRITICAL PATH HANDLER TASK ABENDED WHILE PROCESSING THE FOLLOWING DQE REQUEST
The critical path handler stopped with abnormal termination.
No retry is possible, the critical path handler ends.
Collect the documentation listed in Diagnosis Guide and Reference, "Problem analysis procedures" section. Restart the critical path handler.
EQQCP16E
THE CRITICAL PATH HANDLER TASK DETECTED AN ERROR WHILE PROCESSING THE FOLLOWING DQE: DQE
The critical path handler lost a request.
The critical path handler processing ends.
Collect the documentation listed in Diagnosis Guide and Reference, "Problem analysis procedures" section. Restart the critical path handler.
EQQCP17E
THE CRITICAL PATH HANDLER TASK INITIALIZATION FAILED: CANNOT OPEN CP FILE
The critical path handler cannot open the CP.
The critical path handler processing ends.
Collect the documentation listed in Diagnosis Guide and Reference, "Problem analysis procedures" section. Restart the critical path handler.
EQQCP18E
THE CRITICAL PATH HANDLER TASK INITIALIZATION FAILED: AN ERROR OCCURRED WHILE PROCESSING THE CPHQ QUEUE
The critical path handler cannot continue processing because of a severe error.
The critical path handler processing ends.
Collect the documentation listed in Diagnosis Guide and Reference, "Problem analysis procedures" section. Restart the critical path handler.
Review previous messages in the scheduler message log.
EQQCP19I
CRITICAL PATH RECALCULATED FOR OPERATION OPNUM IN APPLICATION ADID WITH IA: IA FOR JOB JOBNAME. THE TRIGGER WAS: TRIGGER.
- C
- Job on critical path, completed or removed from the hot list
- D
- Dynamic updates to the plan
- L
- Late job
- P
- Daily planning
If the network of your jobs contains either more than one job originating the same critical path, or a critical path nested in this one, the message is issued once.
The critical path handler processing continues.
None.
EQQCP20I
THE RISK LEVEL FOR CRITICAL JOB OPNUM IN APPLICATION ADID WITH IA: IA FOR JOB JOBNAME HAS BECOME POTENTIAL.
The critical path handler changed to potential the risk level for the job identified by the message variables.
Normal processing continues.
None.
EQQCP21I
THE RISK LEVEL FOR CRITICAL JOB OPNUM IN APPLICATION ADID WITH IA: IA FOR JOB JOBNAME HAS BECOME HIGH.
The critical path handler changed to high the risk level for the job identified by the message variables.
Normal processing continues.
None.
EQQCP22I
THE RISK LEVEL FOR CRITICAL JOB OPNUM IN APPLICATION ADID WITH IA: IA FOR JOB JOBNAME WAS RESET TO POTENTIAL.
The critical path handler reset to potential the risk level for the job identified by the message variables.
Normal processing continues.
None.
EQQCP23I
THE RISK LEVEL FOR CRITICAL JOB OPNUM IN APPLICATION ADID WITH IA: IA FOR JOB JOBNAME WAS RESET TO NONE.
The critical path handler reset to none the risk level for the job identified by the message variables.
Normal processing continues.
None.
EQQCP24E
THE CRITICAL JOB WITH OPERATION NUMBER OPNUM IN APPLICATION ADID WITH IA: IA FOR JOB JOBNAME HAS A LOOP IN ITS NETWORK AND HAS BEEN TEMPORARILY DISABLED.
The critical path handler task detected a loop in the network of this critical job, while recalculating its critical path. The critical job is temporarily disabled and will not be listed in the critical job list until the critical dataspace is rebuilt, after a controller restart or a batch plan turnover.
Normal processing continues.
Correct the loop and restart the critical path handler. If the problem persists, for the information to collect, see the Diagnosis Guide and Reference, Chapter 3, "Problem analysis procedures", section "Information needed for all problems", sub-section " Information to collect for daily planning problems". If you cannot determine the cause of the error and the error persists, search the IBM Support database for a solution at http://www.ibm.com/software/sysmgmt/products/support.
EQQCP25I
THE CRITICAL PATH HANDLER TASK SYNCHRONIZATION PHASE HAS STARTED.
The critical path handler has started its resynchronization phase after a controller restart or a batch plan job termination.
The schedulers processing continues.
None.
EQQCP26I
THE CRITICAL PATH HANDLER TASK SYNCHRONIZATION PHASE HAS ENDED.
The critical path handler has ended its resynchronization phase after a controller restart or a batch plan job termination.
The schedulers processing continues.
None.
EQQCP27I
THE CRITICAL JOB WITH OPERATION NUMBER OPNUM WITH RL RISKL IN APPLICATION ADID WITH IA: IA FOR JOB JOBNAME HAS BEEN COMPLETED.
The critical job completed.
The schedulers processing continues.
None.