IBM Support

PI42590: BBOO0038E FUNCTION IWMSTEND FAILED WITH RC=8, REASON=119C084F, EXTENDED 473727 REASON=XXXXXXXX.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The customer's controller region logged hundreds of HTTP
    REQUEST TIMEOUT messages
    
    09:02:54 BBOO0327I HTTP REQUEST TIMEOUT:
             (0000):(FFF65FC7):(00010005):(00000000):():
             (2015/06/01 09:02:54.837060):
             (2015/06/01 09:02:08.837661):
             ():
             (RemoteWebContainer):(httprequest):
             (ip addr=10.0.11.17 port=24639):
             ():():(/orsstd/folderopen.do)
    ...
    13:37:54 BBOO0327I HTTP REQUEST TIMEOUT:
             (0000):(FFC54A41):(00010005):(00000000):():
             (2015/06/01 13:37:06.196718):
             (2015/06/01 13:37:06.197051):
             ():
             (RemoteWebContainer):(httprequest):
             (ip addr=10.0.11.5 port=62522):
             ():():(/orsstd/foldersearch.do)
    The customer's servant region logged
    09:05:34 +BBOO0038E Function IWMSTEND failed with RC=8,
             REASON=119C084F, EXTENDED REASON=FFF65FC7.
    ...
    13:37:59 +BBOO0038E Function IWMSTEND failed with RC=8,
             REASON=119C084F, EXTENDED REASON=FFC54A41.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS   *
    *                      servant issued message "BBOO0038E       *
    *                      FUNCTION IWMSTEND FAILED ..."           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A request queued from the controller for dispatch in a servant
    was timed out and cleaned up in the controller.  There are
    timing windows and configuration settings that allow the
    request
    to get into the servant after it timed out in the controller.
    The servant dispatch code will detect that the request has
    timed out, but during request dispatch cleanup processing it
    may
    invoke the WLM service IWMSTEND with a questionable WLM
    execution unit token.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI42590

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-06-08

  • Closed date

    2015-06-15

  • Last modified date

    2015-06-15

  • 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

  • R850 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":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022