dspmqver (display version information)

Purpose

Use the dspmqver command to display IBM MQ version and build information.

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

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 1	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) For IBM MQ 9.1 and earlier, when 32-bit support is missing from a 64-bit system, the dspmqver -a command might issue a message suggesting that the 32 bit version of GSKit is not installed. For more information, see the Command failure section of this topic. This issue is fixed in IBM MQ 9.2.
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:

1. 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

Command failure

Failure when 32-bit support is missing from a 64-bit system

In IBM MQ 8.0, IBM MQ 9.0, and IBM MQ 9.1, the 32-bit and 64-bit versions of IBM Global Security Kit (GSKit) for IBM MQ (GSKit) are bundled together. When you run dspmqver -a or dspmqver -p 64, the command checks both versions of GSKit. When 32-bit support is missing from a 64-bit system, you might get a message suggesting that the 32-bit version of GSKit is not installed. The GSKit issue is fixed in IBM MQ 9.2. For information about 64-bit Linux® distributions that might no longer support 32-bit applications by default, and guidance on manually loading the 32-bit libraries for these platforms, see Hardware and software requirements on Linux systems.

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.

[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.

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