dspmqver (display version information)

By default, the dspmqver command displays version and build information for the installation from which it was started. A note is displayed if other installations exist; use the -i parameter to display their details.

Syntax

Optional parameters

-a

Display information about all fields and components.

-p Components

Display information for the components specified by component. Either a single component or multiple components can be specified. Enter either the value of a single component or the sum of the values of all the required components. Available components and related values are as follows:

Value	Description
1	IBM® MQ server, or client.
2	IBM MQ classes for Java.
4	IBM MQ classes for Java Message Service and IBM MQ classes for Jakarta Messaging.
8	WebScale Distribution Hub
16 ¹	IBM MQ custom channel for Windows Communication Foundation.
32	IBM MQ Message Service Client (XMS) for .NET (XMS .NET) - this component is only available on Windows.
64	IBM Global Security Kit (GSKit)
128	Advanced Message Security
256	IBM MQ AMQP Service
512	IBM MQ Telemetry Service
1024	Other bundled components that are used by IBM MQ
2048	WebSphere® Liberty profile
4096	IBM MQ Java runtime environment
8192	IBM MQ Replicated Data Queue Managers (RDQM)

Notes:

Supported by IBM MQ for Windows only. If you have not installed Microsoft.NET 3 or later, the following error message is displayed:
Title: WMQWCFCustomChannelLevel.exe - Application Error
The application failed to initialize properly (0x0000135).

The default value is 1.

-f Fields

Display information for the fields specified by field. Specify either a single field or multiple fields. Enter either the value of a single field or the sum of the values of all the required fields. Available fields and related values are as follows:

Value	Description
1	Name
2	Version, in the form `V.R.M.F`: Where `V` =Version, `R` =Release, `M` =Modification, and `F` =Fix pack
4	Level
8	Build type
16	Platform
32	Addressing mode
64	Operating system
128	Installation path
256	Installation description
512	Installation name
1024	Maximum command level
2048	Primary installation
4096	Data Path
8192	License type
16384	Release type, can be: `Long Term Support (LTS) and Continuous Delivery (CD)` if the Modification and Fix pack is zero `Long Term Support (LTS)` if the Modification is zero and Fix pack is not zero. `Continuous Delivery (CD)` otherwise See IBM MQ release types and versioning.

Information for each selected field is displayed on a separate line when the dspmqver command is run.

The default value is 65535. This displays information for all fields.

-b

Omit header information from the report.

-v

Display verbose output.

-i

Display information about all installations. You cannot use this option with other options. The installation from which the dspmqver command was issued is displayed first. For any other installations, only the following fields are displayed: Name, Version, Installation name, Installation description, Installation path, and Primary installation.

Return codes

Table 1. Return code identifiers and descriptions
Return code	Description
0	Command completed normally
10	Command completed with unexpected results
20	An error occurred during processing

Examples

The following command displays IBM MQ version and build information, using the default settings for -p and -f:

dspmqver

The following command displays information about all fields and components and is the equivalent of specifying dspmqver -p 63 -f 4095:

dspmqver -a

The following command displays version and build information for the IBM MQ classes for Java:

dspmqver -p 2

The following command displays the Common Services for Java Platform Standard Edition, IBM MQ, Java Message Service Client, IBM MQ classes for Java Message Service, and [Jakarta Messaging 3.0]

IBM MQ classes for Jakarta Messaging:

dspmqver -p 4

The following command displays the build level of the WebScale Distribution Hub:

dspmqver -p 8 -f 4

The following command displays the name and build type for IBM MQ custom channel for Windows Communication Foundation:

dspmqver -p 16 -f 9

The following command displays information about installations of IBM MQ.

dspmqver -i

Example output for MQ.NET Standard classes:

Name:        IBM Message Service Client for .NET Standard
Version:     9.1.1.0
Level:       p911-LXXXX
Build Type:  Production

Command failure

Failure when viewing the IBM MQ classes for Java

The dspmqver command can fail if you try to view version or build information for the IBM MQ classes for Java, and you have not correctly configured your environment, or if the IBM MQ JRE component is not installed, and an alternative JRE could not be located.

For example, you might see the following message:

[root@blade883 ~]# dspmqver -p 2
AMQ8351: IBM MQ Java environment has not been configured 
correctly, or the IBM MQ JRE feature has not been installed.

To resolve this problem, consider installing the IBM MQ JRE component if it is not already installed, or ensure that the path is configured to include the JRE, and that the correct environment variables are set.

For example, on AIX® and Linux®, you can use one of the following scripts to resolve this problem:

For JMS 2.0, use setjmsenv or setjmsenv64. For example:

export PATH=$PATH:/opt/mqm/java/jre/bin
cd /opt/mqm/java/bin/
. ./setjmsenv64

[root@blade883 bin]# dspmqver -p 2
Name:       IBM MQ classes for Java
Version:    8.0.0.0
Level:      k000-L110908
Build Type: Production

For Jakarta Messaging 3.0, use setjms30env or setjms30env64. For example:

export PATH=$PATH:/opt/mqm/java/jre/bin
cd /opt/mqm/java/bin/
. ./setjms30env64

[root@blade883 bin]# dspmqver -p 2
Name:       IBM MQ classes for Java
Version:    8.0.0.0
Level:      k000-L110908
Build Type: Production

Notes:

The setjmsenv and setjms30env scripts apply to AIX and Linux only.
On Windows, the runjms scripts provide similar functionality to that provided by the setjmsenv and setjms30env scripts on AIX and Linux.
For the IBM MQ classes for Java on Windows, if the IBM MQ JRE component is installed, you need to issue the setmqenv command to resolve error AMQ8351.