Direct links to fixes
APAR status
Closed as program error.
Error description
When a WSRR profile is created on Windows Platforms using PMT, the windows shortcut is created with the default server name of server1 even when a different server name is specified during profile creation.
Local fix
Edit the shortcut and change the server name from server1 to the appropriate server name.
Problem summary
**************************************************************** USERS AFFECTED: All users of WebSphere Service Registry and Repository V8.0 on Windows **************************************************************** PROBLEM SUMMARY: During WSRR standalone profile creation or augmentation there is an option to specify the server name. If the server name is changed from the default, the server is created successfully but the Windows start and stop server shortcuts do not work as they still use the default server1 as a parameter.
Problem conclusion
The code which creates the Windows shortcuts was changed to use the specified server name rather than always using server1. This fix is targeted at WSRR V8.0.0.2.
Temporary fix
Comments
APAR Information
APAR number
IV39045
Reported component name
SERVICE REGISTR
Reported component ID
5724N7200
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-04-02
Closed date
2013-04-23
Last modified date
2013-04-23
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
SERVICE REGISTR
Fixed component ID
5724N7200
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSWLGF","label":"WebSphere Service Registry and Repository"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
23 April 2013