IBM Support

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

Subscribe

You can track all active APARs for this component.

 

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 number

    PM99080

  • Reported component name

    RATL BUS DEV

  • Reported component ID

    5724S5000

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-10-15

  • Closed date

    2014-09-25

  • Last modified date

    2014-09-25

  • 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

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSMQ79","label":"Rational Business Developer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
25 September 2014