IV39045: WSRR PROFILE CREATION CREATES WINDOWS SHORTCUTS WITH DEFAULT SERVER1 EVEN THOUGH A DIFFERENT SERVER NAME IS SPECIFIED.

8.0.0.3-WS-WSRR-ZOS-IFIV65487_IV79085_IV87422_IV87429_IV89477
8.0.0.3-WS-WSRR-MultiOS-IFIV65487_IV79085_IV87422_IV87429_IV89477
WebSphere Service Registry and Repository V8.0 Fix Pack 2

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 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