A fix is available
APAR status
Closed as program error.
Error description
When defining catalog server domains in WebSphere eXtreme Scale, the domain name is not honored from the configuration and if more than one catalog domain was specified only the default domain is started.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All WebSphere eXtreme Scale users who have * * defined multiple catalog service domains * * in the WebSphere Application Server * * administrative console. * * * **************************************************************** * PROBLEM DESCRIPTION: Defined catalog service domain names * * are ignored and not started, unless * * the domain is marked as the default. * **************************************************************** * RECOMMENDATION: * **************************************************************** The code was fixed to recognize multiple catalog service domain configurations.
Problem conclusion
A future cumulative fix corrects the problem for WebSphere eXtreme Scale Version 7.1.
Temporary fix
Comments
APAR Information
APAR number
PM26286
Reported component name
XD EXTREME SCAL
Reported component ID
5724J3402
Reported release
710
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-11-09
Closed date
2010-11-30
Last modified date
2010-11-30
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
XD EXTREME SCAL
Fixed component ID
5724J3402
Applicable component levels
R710 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
23 September 2020