PM87193: IF THERE ARE MORE THAN 256 WEBSPHERE CONTROLLER ON 1 LPAR, RANDOM SERVERS MAY FAIL TO REGISTER WITH WLM

Fixes are available

APAR status

Closed as program error.

Error description

Currently, there is a restriction where only up to 256 WebSphere
controller can be registered with WLM.  If number of controllers
exceeds this limit, some servers will not be able to register
with WLM and will have this error:

BBOO0037E Function IWMSRCRR failed with RC=8, REASON=00000868
(256 WebSphere CR Limit Per SYSTEM)

In certain configuration, it is not needed to register server
with WLM.  This APAR will ship a new custom variable so it is
possible to customize which servers should always register with
WLM vs. those that do not need to register.

This apar does NOT lift the restriction of 256 WebSphere
controllers that can register with WLM per LPAR.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0, V8.0, and V8.5                 *
****************************************************************
* PROBLEM DESCRIPTION: Server fails to Regiter with WLM:       *
*                      BBOO0037E Function IWMSRCRR failed      *
*                      with RC=8, REASON=00000868.             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A server fails to register with Workload Manager (WLM) because
there is a limit to the number of servers that can register
with Workload Manager to receive input to make IIOP routing
decisions.
The current registration limit is 256 registered controller
regions per LPAR. Any registration attempt when there are
already 256 registered controller regions on the system are
rejected with the following return and reason code that can be
found in the controller region log:
BBOO0037E Function IWMSRCRR failed with RC=8,
REASON=00000868.

Problem conclusion

A new property with the name of protocol_iiop_enable_wlm_routing
is provided so that when disabled on certain WebSphere
Application Servers will avoid reaching the described limit.

APAR PM87193 requires changes to documentation.

NOTE: Periodically, we refresh the documentation on our Web
site, so the changes might have been made before you read this
text. To access the latest on-line documentation, go to the
product library page at:

http://www.ibm.com/software/webservers/appserv/library

The following changes to the WebSphere Application Server
Version 7.0 Information Center will be made available in
December 2013.

The topic "Application server custom properties for z/OS" will
be updated to include the following description of the
protocol_iiop_enable_wlm_routing environment variable:

protocol_iiop_enable_wlm_routing

Specifies whether WebSphere Application Server should enable
the process that allows it to receive input from the Workload
Manager (WLM) to make IIOP routing decisions.

When this property is enabled, WLM sends WebSphere Application
Server input that WebSphere Application Server uses to make
IIOP routing decisions.

It is recommended that you leave this property enabled.
However, because there is a limit to the number of servers
than can use this feature on a given LPAR, you might need to
disable this property for some of the servers on an LPAR if
the servers start experiencing the following error:
BBOO0037E Function IWMSRCRR failed with RC=8, REASON=00000868

Information              Value

Data Type                Boolean
Default                     1
Used by Daemon     No

APAR PM87193 is currently targeted for inclusion in WebSphere
Application Server Fix Packs 7.0.0.31, 8.0.0.7, and 8.5.5.1
of WebSphere Application Server.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PM87193
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-04-17
Closed date
2013-05-21
Last modified date
2014-02-05

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

R700 PSY UI13725
UP14/01/11 P F401

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

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

Document Information

Modified date:
11 January 2022

Tips

PM87193: IF THERE ARE MORE THAN 256 WEBSPHERE CONTROLLER ON 1 LPAR, RANDOM SERVERS MAY FAIL TO REGISTER WITH WLM - BBOO0037E

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY UI13725

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

Document Information

Share your feedback

Need support?