IBM Support

PI24532: ESQL SHARED ROW VARIABLE REFERENCES CAN BE CORRUPTED DURING DEPLOYMENT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During deployment of message flows and deployable ESQL files
    (ESQL that is not compiled and inlined into the message
    flows), other message flows references to ESQL SHARED ROW
    variables can be corrupted. This behaviour can be seen if the
    message flows have access to multiple in-scope ESQL SHARED ROW
    variables. Internally, the references to the ESQL SHARED ROW
    variables are being incorrectly resolved to the wrong SHARED
    ROW. This may be seen by the user if they store data into a
    given SHARED ROW, then later try and retrieve data from that
    same SHARED ROW. The store could store the data in one SHARED
    ROW, with the retrieve then incorrectly retrieving data from
    another SHARED ROW. This behaviour can give the impression that
    data in the SHARED ROW has been corrupted or is missing.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of WebSphere Message Broker V8.0 and IBM Integration
    Bus V9.0 using deployable ESQL with SHARED variables at the
    schema level.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Deploying deployable ESQL (ESQL that has not been compiled and
    inlined into the message flow) can corrupt the internal
    references of schema level SHARED variables in ESQL that is
    visible but not currently being deployed - such as ESQL files in
    another library. It may appear that one or more SHARED variables
    have been reset or cleared, or those SHARED variables can even
    appear to contain the contents of another SHARED variable.
    
    There are a number of resource name changes between WebSphere
    Message Broker and IBM Integration Bus Version 9.0. For details
    visit
    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
    tools.mft.doc/bb23814_.htm
    

Problem conclusion

  • The product now ensures that references to ESQL SHARED variables
    do not get corrupted when redeploying deployable ESQL code.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.7
    v9.0       9.0.0.4
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI24532

  • Reported component name

    WEB MB Z/OS

  • Reported component ID

    5697P4400

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-08-25

  • Closed date

    2014-09-30

  • Last modified date

    2016-05-05

  • 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

    WEB MB Z/OS

  • Fixed component ID

    5697P4400

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
05 May 2016