IBM Support

PH59257: LOCK HELD WHILE QSAM FILE OPEN IN AUTOMATED MODE FOR WRITE

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

  • <p>When a QSAM file was open in automated mode for write a lock
    was held on the QSAMWrite node's message flow instance for the
    duration of the file being open. This lock was to stop any other
    processes from making changes to the message flow until the file
    closed, preventing premature closure of the file. However, for a
    file open for a long time, any attempt to make changes to the
    message flow (such as changing message flow statistics settings)
    caused the admin process to wait for a long time too, until the
    file closed, making the integration server appear to hang as no
    subsequent admin messages could be processed so the integration
    server became unresponsive.</p><p> </p><p>This APAR changes
    processing to stop the lock being held for the duration of an
    automated file being open for QSAM write. A consequence of this
    change is that if a message flow containing a QSAMWrite node is
    redeployed when a file is open in automated mode, the file will
    be closed as part of the redeploy processing.</p>
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of the QSAMWrite node in IBM Integration Bus v10.1
    
    
    Platforms affected:
    z/OS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When the QSAMWrite node is operating in automated mode and holds
    a file open for a long duration, admin commands on the message
    flow can appear to hang with the following message seen and the
    integration server becoming unresponsive
    
    BIP8034E An internal configuration response message not received
    

Problem conclusion

  • This APAR changes processing to stop the lock being held for the
    duration of an automated file being open for QSAM write. A
    consequence of this change is that if a message flow containing
    a QSAMWrite node is redeployed when a file is open in automated
    mode, the file will be closed as part of the redeploy
    processing.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.1      10.1.0.3
    
    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

    PH59257

  • Reported component name

    INT BUS FOR Z/O

  • Reported component ID

    5655AB110

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-01-18

  • Closed date

    2024-01-29

  • Last modified date

    2024-01-29

  • 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

    INT BUS FOR Z/O

  • Fixed component ID

    5655AB110

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNQH8","label":"IBM Integration Bus for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A10","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
27 February 2024