IBM Websphere MQ - Upgrade from MQ V6 to V7 causes errors AMQ6090 and AMQ5037 - Middleware News

After you upgrade from WebSphere MQ V6 to V7, many instances of the errors AMQ6090 and AMQ5037 are shown in the queue manager error logs.

Symptom

The following errors are shown in the WMQ queue manager error logs.

AMQ6090: WebSphere MQ was unable to display an error message 6287.
EXPLANATION: MQ has attempted to display the message associated with return code
hexadecimal '6287'. The return code indicates that there is no message text associated with the message. Associated with the request are inserts 0 : 0 :

AMQ5037: The Queue Manager task 'ERROR-LOG' has started.
EXPLANATION: The Utility Task Manager, process ID (708760) type(203), has started the ERROR-LOG task.

Meanwhile, FDC files are generated which correspond to the AMQ5037 errors:

| Probe Id :- XC022001
| Component :- xcsDisplayMessage
| Program Name :- amqzmur0
| Major Errorcode :- zrcX_TASK_STARTED
| Probe Type :- MSGAMQ5037
| Probe Description :- AMQ5037: The Queue Manager task 'ERROR-LOG' has started.

Cause

WebSphere MQ uses the message catalog to display informational, warning or error messages. There is support for multiple languages by choosing to install different WMQ message catalog filesets. If the message catalog file is not correctly installed, WMQ processes would fail to print messages to the error log.

Diagnosing the problem

You need to confirm that the WMQ message catalog fileset has been correctly upgraded.

1. Determine which WMQ language message catalog is currently used by the queue manager .

• First check the "NLSPATH" environment variable setting from the shell where the queue manager is started. Usually, NLSPATH has a default value which depends on the current shell language settings as shown below:
  $ env | grep NLSPATH
  NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat
• 
  
• Then check the "LANG" environment variable setting to know what locale the shell is using. In this example, the shell uses "en_US".
  $ env | grep LANG
  LANG=en_US
• As such, the currently used WMQ message catalog file should be the amq.cat file under the directory /usr/lib/nls/msg/en_US which is installed by the WMQ fileset: "mqm.msg.en_US"

2. Check that the amq.cat file exists in the above directory and that the mqm user has correct permissions (755) to access the file.

• $ cd /usr/lib/nls/msg/en_US
  $ ls -la amq.cat
  -rwxr-xr-x 1 bin bin 569663 Jul 25 23:17 amq.cat

3. Confirm the correct version of the WMQ message catalog fileset is installed. If you find that "mqm.msg.en_US" is at a different level, you need to reinstall this fileset. The following example shows that the installed version is 7.0.1.6 while mqm.msg.en_US is still at 6.0.2.10

$ lslpp -l | grep MQ
mqm.base.runtime      7.0.1.6  COMMITTED  WebSphere MQ Runtime for   
mqm.base.samples      7.0.1.6  COMMITTED  WebSphere MQ Samples       
mqm.base.sdk          7.0.1.6  COMMITTED  WebSphere MQ Base Kit for    a
mqm.client.rte        7.0.1.6  COMMITTED  WebSphere MQ Client for AIX
mqm.java.rte          7.0.1.6  COMMITTED  WebSphere MQ Java Client, JMS
mqm.jre.rte           7.0.1.6  COMMITTED  WebSphere MQ Java Runtime  
mqm.keyman.rte        7.0.1.6  COMMITTED  WebSphere MQ Support for GSKit
mqm.msg.en_US         6.0.2.10  COMMITTED  WebSphere MQ Messages - U.S.
mqm.server.rte        7.0.1.6  COMMITTED  WebSphere MQ Server        
mqm.txclient.rte      7.0.1.6  COMMITTED  WebSphere MQ Extended      
mqm.base.runtime      7.0.1.6  COMMITTED  WebSphere MQ Runtime for   
mqm.man.en_US.data    7.0.1.6  COMMITTED  WebSphere MQ Man Pages - U.S. 

Resolving the problem

Install the WMQ V7 fileset "mqm.msg.en_US" to perform the update, using the correct installation image. Ensure that "mqm.msg.en_US" is updated successfully.