PM40848: EXCEPTIONS FAIL TO TRIGGER 11/09/13 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Having an AND SYSTABLESPACE Exception Condition such as PGSIZE
  along with other ANDed Exception Conditions such as MVS CATALOG
  ALLOCATED_TRACKS and SYSTABLEPART CARDF when Objects are at the
  PART Level doesn't Trigger Objects even though all Exception
  Condition criteria is met. Another scenario that can cause
  Objects not to be Triggered are conditions that are treated like
  a  parenthetical expression such as
  {noformat}
  O SYSTABLESPACE DAYS_SINCE_ALTERED GE 0
  A               DAYS_SINCE_ALTERED LE 7
  {noformat}
  which is evaluated as OR (DAYS_SINCE_ALTERED GE 0 AND
  DAYS_SINCE_ALTERED LE 7). If some Objects don't meet the AND
  Condition, this can cause other Objects that have met their
  Exception Condition criteria to get erroneously un-triggered.
  
  Also addressed in this APAR is a problem that occurs when there
  are multiple DAY OF WEEK or DAY OF MONTH Exception
  Conditions selected, no other "OR" Exception Conditions are
  specified/selected, and there are "AND" Exception Conditions
  also specified/selected.  Even though an object may meet all of
  its "AND" Conditions, the object is not triggered.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Automation Tool.                *
  ****************************************************************
  * PROBLEM DESCRIPTION: Having an AND SYSTABLESPACE Exception   *
  *                      Condition such as PGSIZE along with     *
  *                      other ANDed Exception Conditions such   *
  *                      as MVS CATALOG ALLOCATED_TRACKS and     *
  *                      SYSTABLEPART CARDF when Objects are at  *
  *                      the PART Level doesn't Trigger Objects  *
  *                      even though all Exception Condition     *
  *                      criteria is met. Another scenario that  *
  *                      can cause Objects not to be Triggered   *
  *                      are conditions that are treated like    *
  *                      a  parenthetical expression such as     *
  *                      {noformat}                              *
  *                      O SYSTABLESPACE DAYS_SINCE_ALTERED GE 0 *
  *                      A               DAYS_SINCE_ALTERED LE 7 *
  *                      {noformat}                              *
  *                      which is evaluated as OR                *
  *                      (DAYS_SINCE_ALTERED GE 0 AND            *
  *                      DAYS_SINCE_ALTERED LE 7). If some       *
  *                      Objects don't meet the AND Condition,   *
  *                      this can cause other Objects that have  *
  *                      met their Exception Condition criteria  *
  *                      to get erroneously un-triggered. Also   *
  *                      addressed in this APAR is a problem     *
  *                      that occurs when there are multiple     *
  *                      DAY OF WEEK or DAY OF MONTH Exception   *
  *                      Conditions selected, no other "OR"      *
  *                      Exception Conditions are                *
  *                      specified/selected, and there are       *
  *                      "AND" Exception Conditions also         *
  *                      specified/selected.  Even though an     *
  *                      object may meet all of its "AND"        *
  *                      Conditions, the object is not           *
  *                      triggered.                              *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Code has been changed to correct this condition.
  

Problem conclusion

• APPLY the PTF.
  

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:

Modules/Macros

• HAA$BMSG HAA$BULJ HAA$BUTA HAA$BUTB HAA$BUTE
  HAA$BUTP HAA$BUTR HAA$BUTS HAA$BUTT HAA$BUTX HAA$CALL HAA$EPRU
  HAA$EPRV HAA$ERRS HAA$ERST HAA$ERSV HAA$ETRG HAA$EXCP HAA$JBRK
  HAA$JPRU HAA$SINF HAA$UDOP HAA$UOPT HAA$URBD HAA$UREA HAA$UREO
  HAA$URPR HAA$VREA HAA$VREO HAA$VRPR HAA#BPRI HAA#EPRI HAA#ERSH
  HAA#ERSI HAA#EXCS HAA#OBEX HAA#UPRI HAA#UTED HAA#UTOB HAA@PEXC
  HAAHERST HAAHERSV HAAHURBD HAAHUREA HAAHUREO HAAHURPR HAAHVRBD
  HAAHVREA HAAHVREO HAAHVRPR HAAM52   HAAM53   HAAREPRC HAA38
  HAA387E  HAA53    HAA538E  HAA539E  HAA54    HAA540E  HAA541E
  HAA542E  HAA57    HAA578E
  

Fix information

• Fixed component name

  DB2 AUTOMATION

• Fixed component ID

  5697G6300

Applicable component levels

• R310 PSY UK73166

     UP11/10/29 P F110

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.