PM99080: Differential between v7.5 and v8.5.x handling the handleHardIOErrors property

Rational Business Developer Fix Pack 2 (8.5.1.2) for 8.5.1

APAR status

• Closed as program error.

Error description

• Environment: z/OS
  Product name: IBM? Rational? Business Developer
  
  Program Version    :  8.5.0
  Description.
  Its observed that there is a differential with exception
  handling between v7.5 and v8.5.x when the handleHardIOErrors
  property is implemented.
  
  In the example scenario catching an SQL exception in v8 behaves
  differently as it intsigates a non-trappable exception where
  setting the option as handleHardIOErrors = yes will not cause it
  to be trapped as expected. In RBD v7.5.x in the same scenario
  the exception will be trapped.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a program tries to use a cursor that was not opened,
  with a generic get statement, and the cobolGen logic detects
  that at runtime, it manufactures a -501 sql error code. The
  logic always considered this to be a non-trappable error and
  would cause the program to terminate. The proper logic was
  to make it non-trappable only if handleHardIOErrors was
  turned off, either by the program level annotation, or
  moving a value to VGVar.handleHardIOErrors.
  

Problem conclusion

• The software has been updated to check to see if the runtime
  variable for whether the program can handle hard IO errors
  has been turned on/off, and if it is off, then prevents the
  exception from being trapped causing the program to
  terminate. If it was on however, the program is then able to
  use a try/onexception block to trap it.
  

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

  RATL BUS DEV

• Fixed component ID

  5724S5000

Applicable component levels

• R801 PSN

     UP