PI52399: MULTIPLE CPH ABENDS INDICATED BY MESSAGE EQQCP15E WHILE PROCESSING DQE AND THEREAFTER MESSAGE EQQZ045E

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• multiple CPH abends indicated by message:
  EQQCP15E THE CRITICAL PATH HANDLER TASK ABENDED
  while processing DQE
  which ends in critinal path subtask abend with message:
  EQQZ045E SUBTASK CRITPATH HANDLER ENDED UNEXPECTEDLY
  The abend occurred while processing a DQE
  adding a dependency for an operation not existing in the
  plan.
  
  The situation is incorrectly handled by CPH task that
  abends.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All TWSz and IWSz users using                *
  *                 Critical Path feature.                       *
  *                 FUNCTION=CPH                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: Multiple abends can occur in CPH task   *
  *                      when DQE referring to operations no     *
  *                      more in the current plan are received.  *
  ****************************************************************
  * RECOMMENDATION: APPLY THE PTF FIXING THIS APAR               *
  ****************************************************************
  Multiple abends can occur in CPH task when a request about an
  add dependency or add job or other refers to something
  no more present in the Current plan.
  

Problem conclusion

• The abend has been fixed by ignoring the wrong reference
  to not existing jobs in the plan.
  When a request about add dependency or add job or other refers
  to something no more present in the Current plan the request
  is ignored and the informational message EQQCP09I is issued:
  
  EQQCP09I A DQE OF TYPE dqetype WAS IGNORED BECAUSE THE INVOLVED
           OPERATION IDENTIFIED BY THE VSAM KEY vsamkey IS NO
           MORE IN THE PLAN
  
  This kind of request can occur when for example a user from
  MCP ISPF dialogue executes the following actions on an
  occurrence made by critical jobs:
  - select 5.1 to add an occurrence
  - select OPER  (e.g. there are 5 operations)
  - select one operation (e.g operation 003)
  - select dependencies
  - create a new successor dependency
  - press PF3
  - select again dependencies
  - delete just created successor dependency
  - press PF3
  - press PF3
  - delete just nmodified operation (e.g. 003)
  - press PF3
  - press PF3
  occurrence is added
  510Y
  512Y
  600Y
  602Y
  910Y
  912Y
  920Y
  922Y
  930Y
  932Y
  EQQCPHAN
  EQQCP0
  EQQMCCRT
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI34055 UI34056 UI34057 UI34058 UI34059 UI34060 UI34061 UI34062
  UI34063 UI34064

Modules/Macros

• EQQCPHAN EQQCP0   EQQMCCRT
  

Fix information

• Fixed component name

  TIV WRKLD SCHD

• Fixed component ID

  5697WSZ01

Applicable component levels

• R510 PSY UI34055

     UP16/01/29 P F601

• R512 PSY UI34060

     UP16/01/29 P F601

• R600 PSY UI34056

     UP16/01/29 P F601

• R602 PSY UI34061

     UP16/01/29 P F601

• R910 PSY UI34057

     UP16/01/29 P F601

• R912 PSY UI34062

     UP16/01/29 P F601

• R920 PSY UI34058

     UP16/01/29 P F601

• R922 PSY UI34063

     UP16/01/29 P F601

• R930 PSY UI34059

     UP16/01/29 P F601

• R932 PSY UI34064

     UP16/01/29 P F601

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.