MQ Visual Browse

Appendix D Frequently Asked Questions (FAQ)

Q. What does reason code 2058 mean?

A. Generally, 2058 means that you have an invalid queue manager name or that the host does not have that particular queue manager. Check the spelling of the queue manager name that you inputted. Also, queue manager names are case sensitive (e.g. MQA1 is not the same as mqa1).

Q. What does reason code 2059 mean?

A. Generally, 2059 means that the queue manager is down. Try restarting the queue manager and command server on the remote box. Reason code 2059 can also oocur if you inputted an incorrect port number. Therefore, verify that the port number is correct.

Q. What does reason code 2009 mean?

A. Generally, 2009 means that the channel name is incorrect. Verify that you have inputted the correct server connection channel name. Also, channel names are case sensitive (e.g. JAVA.CHL is not the same as java.chl).

Q. What does reason code 2035 mean?

A. The reason code 2035 means that the user's UserId is not authorized to access the queue on the remote (or local) queue maanger. Ask your WebSphere MQ Administrator to grant your UserId the necessary authority to access the queue.

Q. When I click the Test button in the Queue Manager Access Profile window, nothing happens. No response from MQ Visual Browse at all.

A. This generally means that the MCA (Message Channel Agent) is timing out on a TCP/IP error. The TCP/IP time-out value appears to be at least 1 minute (maybe even longer).

Assuming the network is stable and working, make sure that both queue manager and the listener are running on the box that you are attempting to connect to (or /etc/inetd and /etc/services have been configured correctly ).
The time-out could be from an incorrect value for either the hostname or Port #.
- From a DOS prompt or Unix shell, ping the hostname - e.g. ping remotehostname or ping xx.xx.xx.xx
- Also, verify that you have inputted the same port number that the listener is using on the remote box.

Q. Can I use MQ Visual Browse with my mainframe (OS/390 or z/OS) queue managers?

A. Yes. But you need to have the CAF (Client Attachment Feature) installed on the mainframe.
On the mainframe, go to SDSF and look in the xxxxCHIN (where xxxx is the queue manager name) output for a message:

CSQX099I - xxxx CSQXGIP Client attachment feature available If this message doesn't show up, then you don't have the feature installed. The CAF is a required for any client program (including MQ Visual Browse) to connect directly to a mainframe queue manager.

Q. Can I install MQ Visual Browse on a network drive (LAN) and run it from that location?

A. Yes. MQ Visual Browse will happily run from a network drive. Each user's preferences will be stored in their own "Home Directory". On Windows, the home directory is the "My Documents" folder. On Unix and Linux, the home direcory is the user's standard logon directory (i.e. /export/home/me ).

Note: If you going to run MQ Visual Browse from a network drive and share it with other members of your team, please make sure you have purchased sufficient licenses of MQ Visual Browse.

Q. Can I share my queue manager connection information for MQ Visual Browse with another user or put it on a network drive (LAN)?

A. Yes. MQ Visual Browse stores the queue manager connection information in a file called: CommProfileDB.properties. By default, this file is stored in the user's "Home Directory". You can move the CommProfileDB.properties to any directory or network drive that you wish. After you have moved the file, you will need to update MQ Visual Browse about the new location for CommProfileDB.properties. Do the following to update MQ Visual Browse:

Start MQ Visual Browse
Select Edit -> Preferences from the menu
Click the Browse button for the CommProfileDB Directory field
Navigate to the location of the CommProfileDB.properties file
Click the OK button in the File dialog box
Finally, click the OK button in the Preferences popup box.

Q. Can I set or update the MQMD fields under the Context tab (application id data, etc...)?

A. Yes. MQ Visual Browse supports MQ's various setting of the context information. MQ Visual Browse supports the following:

Setting No Context Information. When this open option is used then each message saved will NOT contain any context information.
Default Context Information. When this open option is used the queue manager will set the appropriate context information for the message on behalf of the user.
Set All Context. When this open option is used the user must fill in all context information (assuming they have authority to do it).

The default action is to open the queue using 'Default Context'. To select a different open option, first close the queue (File -> Close Queue) then click File -> Open Queue. In the lower right of the Open Queue window you will see 'Open Options' . Click the Context dropdown box and select a different context mode (i.e. Set All Context). Now click the Open button and you will be able to change / update / alter any message's context information.