IBM Support

PI24358: ABEND 0D6 HAPPENS WHEN A WOLA UNREGISTER CALL IS MADE WHEN THE APPLICATION SERVER IS DOWN

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The WebSphere OLA (WOLA) code starts the unregister process,
    but then takes a 0D6 abend when driving a PC routine to the (now
    stopped) WebSphere server.  This is converted to a RC=8 RSN=76
    indicating that the server is down.  This then leaves the
    registration in an unacceptable state.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.0 and V8.5                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: When stopping a WOLA CICS link server,  *
    *                      RC=8 and RSN=76 is returned.            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An attempt was made to stop a WOLA link server while the
    WebSphere Application Server for z/OS server instance was
    already stopped.  The WOLA code attempted to call a space
    switching PC routine to the stopped server.  The PC routine had
    already been deregistered, and an 0D6 abend resulted.  The
    abend was converted to a RC=8 RSN=76 and control returned to
    the caller.
    In the process of returning to the caller, the registration is
    marked as unregistered, but the registration itself is still
    allocated.  This results in a RC=8 RSN=8 when attempting to
    re-start the link server.
    Additionally, a native storage leak of an LSCB control block
    can occur when a client connect request fails.   The LSCB
    control block has an eyecatcher at offset x'00' of "Lscb".  The
    storage is in key 8 from subpool 0 if running in a raw client
    OR key 2 and subpool 249 otherwise.  The LSCBs are managed
    within a cellpool.
    

Problem conclusion

  • Code was added to allow a link server to be stopped when the
    associated WebSphere Application Server for z/OS server
    instance has already been stopped.
    
    Code has been modified to release the obtained LSCB when a
    client connect request returned with a failure.
    
    APAR PI24358 is currently targeted for inclusion in Fix Packs
    8.0.0.10 and 8.5.5.4 of WebSphere Application Server for z/OS.
    
    Please refer to the Recommended Updates page for delivery
    information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    
    In addition, please refer to URL:
    http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack PTF information.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI24358

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-08-21

  • Closed date

    2014-09-15

  • Last modified date

    2026-07-08

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Document Information

Modified date:
08 July 2026