PJ40424: SOMETIMES THE FAILURE OF A BRANCH UNIT INSIDE ITERATOR OPERATOR DID NOT BREAK THE ITERATOR LOOP EXPECTEDLY

IBM ISW-InterimFix-SQW_9.7.3.v20120719

APAR status

• Closed as program error.

Error description

• Steps to reproduce:
  1. Put an iterator operator (from 0 to 3).
  2. Inside the iterator,
  2.1. Firstly check whether the current iterator var is 0
  (Variable_Comparison_A).
  If yes, linked to File_Wait_A - where we detect a not existing
  file. And link to a Continue operator on the failure output port
  (QUITE IMPORTANT!!!!)
  If no, linked to Variable_Comparison_B.
  2.2. In Variable_Comparison_B, check whether the current
  iterator var is 1
  If yes, linked to File_Wait_B - where we detect a not existing
  file, but link to nothing.
  If no, linked to the End Iterator.
  3. Link End Iterator to File_Write_SUCCESS operator on the
  success output port.
  4. Link End Iterator to File_Write_FAIL operator on the fail
  output port.
  
  Expected result: File_Wait_B failed, and break the iterator
  loop. Finally the logic went to the File_Write_Fail.
  Actual result: File_Wait_B failed but marked the iterator as
  successful. Finally the logic went to the File_Write_Success.
  

Local fix

• Workaround : None.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All.                                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * SOMETIMES THE FAILURE OF A BRANCH UNIT INSIDE ITERATOR       *
  * OPERATOR                                                     *
  * DID NOT BREAK THE ITERATOR LOOP EXPECTEDLY                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to fix pack 9.7.7.                                   *
  ****************************************************************
  

Problem conclusion

• Steps to reproduce:
  1. Put an iterator operator (from 0 to 3).
  2. Inside the iterator,
  2.1. Firstly check whether the current iterator var is 0
  (Variable_Comparison_A).
  If yes, linked to File_Wait_A - where we detect a not existing
  file. And link to a Continue operator on the failure output port
  If no, linked to Variable_Comparison_B.
  2.2. In Variable_Comparison_B, check whether the current
  iterator var is 1
  If yes, linked to File_Wait_B - where we detect a not existing
  file, but link to nothing.
  If not, linked to the End Iterator.
  3. Link End Iterator to File_Write_SUCCESS operator on the
  success output port.
  4. Link End Iterator to File_Write_FAIL operator on the fail
  output port.
  
  Expected result: File_Wait_B failed, and break the iterator
  loop. Finally the logic went to the File_Write_Fail.
  Actual result: File_Wait_B failed but marked the iterator as
  successful. Finally the logic went to the File_Write_Success.
  

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:

Fix information

• Fixed component name

  DWE SQL WHSE TO

• Fixed component ID

  5724DWESQ

Applicable component levels

• R973 PSY

     UP