IV27438: INSTANCE NAME CHANGED TO UPPER CASE AFTER UPGRADE.
Fixes are available
Closed as program error.
The instance name for a multi-instance agent, such as the kr2 agent, changes from lower case or mixed case to upper case after upgrade.
The Agent instance name is changed to upper case after upgrade on Manage Tivoli Enterprise Service (MTEMS). On Window systems, when upgrading an IBM Tivoli Monitoring multi-instance agent to 622 Fix Pack 2 or later (including 623 GA and 623 Fix Pack 1), the agent instance names are changed to upper case on Manage Tivoli Enterprise Service (MTEMS). If the customer has a new multi-instance agent which has the entry "KQZ_INSTANCE_NAME=$(INSTANCE)" in the agent K<pc>ENV file packaged with an IBM Tivoli Monitoring installer older than 623fp2, after the upgrade there are two instaces displayed on portal server, one with the original instance name, one with upper case instance name. As a result, situations that use Manage System List (MSL) do not work properly. For example, After the upgrade, the instance "MyInstance" becomes "MYINSTANCE" on MTEMS. Both "MyInstance" and "MYINSTANCE" are shown on portal.
The code was modified to keep the correct instance name case when upgrading. Further more, if the instance name was already changed to upper case by previous upgrade, the current upgrade restores the instance to the original case. The fix for this APAR is contained in the following maintenance packages: | fix pack | 6.2.3-TIV-ITM-FP0002 | release | 6.3.0-TIV-ITM
Edit the file candlehome\TMAITM6\kxxcma_instance.ini, where xx is the product code. change the line Cantask=<UPPERCASED INTANCE NAME> to Cantask=<the correct instance name> and reconfig the agent
Reported component name
OMEG DIST INSTA
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
OMEG DIST INSTA
Fixed component ID
Applicable component levels