IBM Support

PH61557: IIB INTEGRATION SERVER (IS) ABENDS IF MULTIPLE IS PROCESSES ARE ACCESSING THE SAME ACTIVITY LOG FILE

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

  • The Activity Log configuration service does provide an option to
    apply the configurable service to one or all of the integration
    servers on the integration node. The default is 'all' and in
    this case, it is possible that one or more of the integration
    servers may abend with the following abend stack:
    
    ImbConfigurationException::throwThis()
    ImbFile::write(const char*,int)
    
    ImbRotatableLogFile::write(const void*,int)
    ImbActivityLogFile::write(const ImbActivityLogEntry&)
    ImbActivityLogManager::writeActivityLogEntry(ImbActivityLogE
    ImbActivityLogManager::writeActivityLogEntryStatic(ImbActivi
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus v10.1 using ActivityLog
    configurable service
    
    
    Platforms affected:
    ZOS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The Activity Log configurableservice provides an option to apply
    the configurable service to one or all of the integration
    servers on the integration node. The default is 'all' and in
    such case, it is possible that one or more of the integration
    servers may abend when they all try to write to the same
    activity log file.
    

Problem conclusion

  • The product has been updated to introduce a new option,
    "executionGroupSpecificLogs", in the activity log configurable
    service. This option can be set to true or false, allowing users
    to specify whether to generate a separate activity log file for
    each Integration Server.  If you select this option, then the
    'activitylog file name' will be used to create a specific
    activitylogfile_EGname file for each of the integration servers.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version   Maintenance Level
    v10.1      10.1.0.7
    
    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

    PH61557

  • 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-05-29

  • Closed date

    2025-09-25

  • Last modified date

    2025-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

    INT BUS FOR Z/O

  • Fixed component ID

    5655AB110

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSNQH8","label":"IBM Integration Bus for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A10","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Document Information

Modified date:
25 September 2025