IBM Support

IT33066: IT31928 IS INCOMPLETE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • IT31928 defines the ordering in which ESQL files are processed
    during a deployment or startup to be the lexicographical
    ordering of the full paths to the deployed files on disk.
    IT31928 is incomplete in that it only applies this ordering
    during application startup. The order of deployment of ESQL
    files as part of a BAR file deploy is still system dependent.
    This can lead to a BAR file that contains ESQL files with an
    invalid ordering dependency deploying "successfully" but then
    not being able to start after the application has been stopped
    or the integration server has been restarted.
    Additionally this ordering restriction is not documented in the
    Knowledge Center.
    

Local fix

  • Restructure ESQL files in such a way that the order of
    processing of individual is not critical, e.g. do not initialize
    schema or shared variables in one file with values defined in
    another ESQL file.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of ESQL in IBM Integration Bus v10 and App Connect
    Enterprise
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    IT31928 defines the ordering in which ESQL files are processed
    during a deployment or startup to be the lexicographical
    ordering of the full paths to the deployed files on disk.
    IT31928 is incomplete in that it only applies this ordering
    during application startup. The order of deployment of ESQL
    files as part of a BAR file deploy is still system dependent.
    This can lead to a BAR file that contains ESQL files with an
    invalid ordering dependency deploying "successfully" but then
    not being able to start after the application has been stopped
    or the integration server has been restarted. Additionally this
    ordering restriction is not documented.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT33066

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-06-30

  • Closed date

    2022-03-04

  • Last modified date

    2022-03-04

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0"}]

Document Information

Modified date:
05 March 2022