IBM Support

PM88133: WEBSPHERE TRANSACTION CONNECTING TO CICS VIA WOLA HANG

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Occasionally WebSphere transaction connecting to CICS via WOLA
    seem to hang. Control region could not be stopped either because
    there are still active transactions.
    Investigation showed that CICS link servers were stopped
    unexpectedly. Any transactions requiring XA resolution will not
    be able to finish with the link servers down.
    CICS TOR joblog shows following error message immediately before
    the STOP occurs:
    .
    BBO Mon Apr 22 10:46:02 2013 0004724
    BBOA8799E A WRITEQ TSQ BBO4724C error occurred with eibresp: 44
              eibresp2: 0.
    .
    BBO Mon Apr 22 10:46:02 2013 0004724
    BBOA8803E The link server stopped because of errors.
              Regname: OUTTRAN2
    .
    The error that occurred was a write to a CICS temporary storage
    queue that the WOLA link task creates.
    The queue has a name BBOxxxxx where xxxxx varies depending on
    the link task instance.
    The WRITEQ error code 44 is QIDERR which means the queue no
    longer exists.
    .
    WebSphere development found out that the temporary storage queue
    names created by the WOLA link server only contain 4 of the 5
    digits of the CICS task number.
    This can cause a link task to delete another link task's
    temporary storage queue.
    For example, if tasks 12345 and 22345 are running WOLA link
    tasks, and task 22345 exits, it will delete the temporary
    storage queue with 2345 in its name.  This means that task 12345
    will no longer be able to use this queue.
    .
    This APAR has been taken so that all five digits of the CICS
    task number are put into the temporary storage queue name that
    the WOLA link task creates.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.0 and V8.5                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: CICS WOLA link server stops             *
    *                      unexpectedly with message BBOA8803E.    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The WebSphere Optimized Local Adapters (WOLA) link server may
    stop unexpectedly after issuing message BBOA8803E in the job
    output.  The message will be preceeded by message BBOA8799E,
    which indicates a write to a CICS TSQ failed:
    BBOA8799E A WRITEQ TSQ BBO4724C error occurred with
    eibresp: 44 eibresp2: 0.
    The generated queue name is incorrect, and can collide with
    other queues used by the WOLA link server.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PM88133

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-04-30

  • Closed date

    2013-05-31

  • Last modified date

    2015-01-05

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PI32189

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"800","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
11 January 2022