PH21994: ABEND 0C4 IN EQQDNTOP (NEW CURRENT PLAN) WITH DATASPACE (CPDATASPACE) ENABLED.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The 0C4 abend is occurring in  EQQDPZMR +F2A, while performing
  loop analysis. In fact, this module is the one performing the
  loop analysis. Problem occurs, according to the provided offest,
  when it is checking if the LOOP control scanning the
  predecessors has ended with a match or if it needs to continue.
  
  It is in the loop detection module, while checking  for the
  operation with:
  480205        wkey_iadate
  0401           wkey_iatime
  AI0MB3LATET wkey_adid
  00000001      wkey_opno
  
  While scanning the PRED chain it found a predecessor operation
  which is actually an occurrence (it is a pending predecessor)
  and this is causing to get a not valid pointer (due to a
  different layout of the occurrence block, added with dataspace)
  considering it as an application dependency. this originated
  the S0C4.
  The mapping used is different if the DataSpace is enabled or
  not. That is why disabling the DataSpace the Abend does not
  occur. Problem is in 950 and in 930 code as well.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All 930 IWSz and 950 zWS users using the     *
  *                 Data Space.                                  *
  *                 FUNCTION=DP                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: Abend S0C4 might occur when running the *
  *                      daily plan (any type) during the Loop   *
  *                      Detection.                              *
  ****************************************************************
  An abend S0C4 might occur in Daily Plan (replan, extend, trial)
  during the Loop detection phase, when the Data Space feature is
  enabled. If the Data Space is disabled, under the same
  conditions no abend occurs.
  

Problem conclusion

• Problem was due to a wrong check when scanning the predecessor
  chain and a pending predecessor is found in the loop.
  

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:

  UI68608 UI68609

Modules/Macros

• EQQDPZMR
  

Fix information

• Fixed component name

  TIV WRKLD SCHD

• Fixed component ID

  5697WSZ01

Applicable component levels

• R932 PSY UI68608

     UP20/03/27 P F003

• R952 PSY UI68609

     UP20/03/27 P F003

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.