Displaying the WebSphere MQ version

WebSphere MQ provides a program called dspmqver which can display the version of WebSphere MQ and its installed components like the WebSphere MQ Java™ and JMS classes, WebSphere MQ Telemetry, and the IBM Global Security Kit for WebSphere MQ. On IBM i, WebSphere MQ also provides the DSPMQMVER CL command which displays the main product version only.

WebSphere MQ V7.0.1, V7.1, and V7.5 (except IBM i)

• IBM i Command Line
  ===> DSPMQMVER

• IBM i Q Shell
  ===> /QSYS.LIB/QMQM.LIB/DSPMQVER.PGM -a

• Linux & UNIX
  sh> dspmqver -a

• Windows
  C:\> dspmqver -a

WebSphere MQ V7.0.0.x and V6.0

• IBM i Command Line
  ===> DSPMQMVER

• IBM i Q Shell
  ===> /QSYS.LIB/QMQM.LIB/DSPMQVER.PGM -p 15

• Linux & UNIX
  sh> dspmqver -p 15

• Windows
  C:\> dspmqver -p 15

WebSphere MQ V5.3

• IBM i Command Line
  ===> CALL QMQM/MQVER

• Linux & UNIX
  sh> dspmqver -p 7
  
  sh> mqver -p 7

• Windows
  C:\> dspmqver -p 7
  
  C:\> mqver -p 7

Working with Multiple Installations

If you have multiple installations of WebSphere MQ (which is supported by WebSphere MQ V7.1 and later except on IBM i), you can run dspmqver -i to list the main product version of them all. If you wish to see the detailed component version information for a particular installation, you must set up your environment and run dspmqver from that installation as described below.

Setting your Environment with setmqenv

The dspmqver command uses a Java runtime in order to display the version of WebSphere MQ components which are written in Java. In order for this to work, you must have recent Java runtime in your PATH, and your CLASSPATH variable must include the WebSphere MQ files com.ibm.mq.jar and com.ibm.mqjms.jar. If you are running WebSphere MQ V7.1 or later, you can use the setmqenv command on most platforms to set up the environment for you:

• IBM i does not supply the setmqenv command.

• Linux & UNIX
  sh> . /path/to/wmq-7.5/bin/setmqenv -s

• Windows
  C:\> "C:\Program Files (x86)\IBM\WebSphere MQ_2\bin\setmqenv" -s

Setting your Environment Manually

If you do not have setmqenv, you must set your CLASSPATH manually in order for dspmqver to show the version of all components. WebSphere MQ V7.0 and V6.0 on IBM i, Linux and UNIX systems provides scripts called setjmsenv (and setjmsenv64 on some V7.0 systems) which you can source to help set your CLASSPATH for WebSphere MQ:

• IBM i Q Shell
  ===> . /QIBM/ProdData/mqm/java/bin/setjmsenv

• Linux & UNIX
  sh> . /opt/mqm/java/bin/setjmsenv64
  
  sh> . /opt/mqm/java/bin/setjmsenv

If you do not use the setjmsenv scripts, you must set your CLASSPATH manually as shown below. On UNIX and Linux systems, you may also need to set your library path so that dspmqver can load the WebSphere MQ bindings library. Point your library path at the WebSphere MQ java/lib or java/lib64 directory, depending on whether your JVM is 32- or 64-bit:

• AIX
  sh> export CLASSPATH=/usr/mqm/java/lib/com.ibm.mq.jar:/usr/mqm/java/lib/com.ibm.mqjms.jar
  sh> export LIBPATH=/usr/mqm/java/lib64
  sh> dspmqver -a

• HP-UX
  sh> export CLASSPATH=/opt/mqm/java/lib/com.ibm.mq.jar:/opt/mqm/java/lib/com.ibm.mqjms.jar
  sh> export SHLIB_PATH=/opt/mqm/java/lib
  sh> dspmqver -a

• IBM i Q Shell
  Permanently set the CLASSPATH variable from the IBM i Command Line, for example:
  ===> ADDENVVAR(CLASSPATH) VALUE('/QIBM/ProdData/mqm/java/lib/com.ibm.mq.jar:/QIBM/ProdData/mqm/java/lib/com.ibm.mqjms.jar') LEVEL(*SYS)
  
  Alternatively, you can set the CLASSPATH temporarily in your Q Shell:
  ===> export CLASSPATH=/QIBM/ProdData/mqm/java/lib/com.ibm.mq.jar:/QIBM/ProdData/mqm/java/lib/com.ibm.mqjms.jar
  
  Then run the dspmqver program from the Q Shell:
  ===> /QSYS.LIB/QMQM.LIB/DSPMQVER.PGM -a

• Linux & Solaris
  sh> export CLASSPATH=/opt/mqm/java/lib/com.ibm.mq.jar:/opt/mqm/java/lib/com.ibm.mqjms.jar
  sh> export LD_LIBRARY_PATH=/opt/mqm/java/lib64
  sh> dspmqver -a

• Windows
  C:\> set CLASSPATH=C:\Program Files (x86)\IBM\WebSphere MQ\java\lib\com.ibm.mq.jar:C:\Program Files (x86)\IBM\WebSphere MQ\java\lib\com.ibm.mqjms.jar
  C:\> dspmqver -a

Solving Problems

1. If you have absolutely no idea what version of WebSphere MQ is installed on your system, try running dspmqver with no flags. If the dspmqver command is not found, check to see whether your system has any information about WebSphere MQ installations and run the dspmqver command from the installation directories (if any).
   
   
2. If dspmqver prints the message "AMQ8351: WebSphere MQ Java environment has not been configured properly" then you must set or double-check your CLASSPATH. On IBM i, Linux and UNIX you must ensure you are exporting the CLASSPATH variable so that it will be seen by dspmqver. If you are using the setjmsenv or setjmsenv64 script, make sure you source it using the dot syntax rather than running the script.
   
   
3. If dspmqver prints a message like "Exception in thread "main" java.lang.UnsupportedClassVersionError: com/ibm/mq/MQJavaLevel (Unsupported major.minor version 48.0)" then your JVM is too old. Run 'java -version' to check its level and compare it against the WebSphere MQ System Requirements. Install a newer JVM or modify your PATH to use a newer JVM if one is already on the system.
   
   
4. If dspmqver prints a message like "mqjbnd=CC=2;RC=2495;AMQ8568: The native JNI library 'mqjbnd' was not found. [3=mqjbnd]::Can't find library mqjbnd (libmqjbnd.a or .so) in sun.boot.library.path or java.library.path" then you must update the library path as shown above. On AIX the library path variable is called LIBPATH, on HP-UX it is SHLIB_PATH, and on Linux and Solaris systems it is called LD_LIBRARY_PATH. Be sure to point to the WebSphere MQ java/lib directory for 32-bit JVMs and java/lib64 for 64-bit JVMs, and export the library path variable so that it will be seen by dspmqver.

Sample Output

If your environment is properly configured, either manually or using the setmqenv program, then the output you receive from dspmqver should look similar to that shown below. The number of components may vary based on your WebSphere MQ version, platform, and installation options:

sh> dspmqver -a
Name:        WebSphere MQ
Version:     7.5.0.0
Level:       p000-L120604
BuildType:   IKAP - (Production)
Platform:    WebSphere MQ for AIX
Mode:        64-bit
O/S:         AIX 6.1
InstName:    Installation4
InstDesc:    
InstPath:    /usr/IBM/WMQ-7.5/usr/mqm
DataPath:    /var/mqm
Primary:     No
MaxCmdLevel: 750

Note there are a number (3) of other installations, use the '-i' parameter to display them.

Name:        WebSphere MQ classes for Java
Version:     7.5.0.0
Level:       p000-L120604
Build Type:  Production

Name:        Java Message Service Client
Version:     7.5.0.0
Level:       p000-L120604
Build Type:  Production

Name:        WebSphere MQ classes for Java Message Service
Version:     7.5.0.0
Level:       p000-L120604
Build Type:  Production

Name:        IBM WebSphere MQ Telemetry
Version:     7.5.0.0
Level:       p000-L120604
Build Type:  Production

Name:        IBM WebSphere MQ JMS Provider
Version:     7.5.0.0
Level:       p000-L120604 mqjbnd=p000-L120604
Build Type:  Production

Name:        Common Services for Java Platform, Standard Edition
Version:     7.5.0.0
Level:       p000-L120604
Build Type:  Production


DistHub Build Type:
DistHub Build Level: DH000-L50930
Webscale Distribution Hub Core
Name:        WebSphere MQ Advanced Message Security
Version:     7.5.0.0
Level:       p000-L120604
BuildType:   IKAP - (Production)

Name:        IBM Global Security Kit for WebSphere MQ
Version:     8.0.14.21
Build Type:  Production
Mode:        32-bit

Name:        IBM Global Security Kit for WebSphere MQ
Version:     8.0.14.21
Build Type:  Production
Mode:        64-bit