Skip to main content

IBM Websphere MQ - dspmqver command - Middleware News


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 follow:
-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 follow:
Information for each selected field is displayed on a separate line when the dspmqver command is run.
The default value is 8191. 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. Not applicable to HP Integrity NonStop Server.

Return codes

Return codeDescription
0Command completed normally.
10Command completed with unexpected results.
20An error occurred during processing.

Examples

The following command displays WebSphere 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 WebSphere MQ classes for Java:
dspmqver -p 2
The following command displays the Common Services for Java Platform Standard Edition, IBM WebSphere MQ, Java Message Service Client, and WebSphere MQ classes for Java Message Service:
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 WebSphere MQ custom channel for Windows Communication Foundation:
dspmqver -p 16 -f 9
The following command displays information about installations of WebSphere MQ.
dspmqver -i

Command Failure

The dspmqver command can fail if you try to view version or build information for the WebSphere MQ classes for Java, and you have not correctly configured your environment. For example, you might see the following message:
[root@blade883 ~]# dspmqver -p2
AMQ8351: WebSphere MQ Java environment has not been configured correctly.
To resolve this problem, ensure that the path is configured to include the JRE, and that the correct environment variables are set; for example, by usingsetjmsenv or setjmsenv64. For example:
export PATH=$PATH:/opt/mqm/java/jre/bin
cd /opt/mqm/java/bin/
. ./setjmsenv64

[root@blade883 bin]# dspmqver -p2
Name:       WebSphere MQ classes for Java
Version:    7.1.0.0
Level:      k000-L110908
Build Type: Production

C:\Users\karth>dspmqver -p1
Name:        IBM MQ
Version:     9.0.0.0
Level:       p900-L160518.TRIAL
BuildType:   IKAP - (Production)
Platform:    IBM MQ for Windows (x64 platform)
Mode:        64-bit
O/S:         Windows 8 Unknown x64 Edition, Build 9200
InstName:    Installation2
InstDesc:
Primary:     Yes
InstPath:    C:\Program Files\IBM\MQ
DataPath:    C:\ProgramData\IBM\MQ
MaxCmdLevel: 900
LicenseType: Trial

To use dspmqver to find out the version of the WebSphere MQ classes for Java that are being used, run the following command:

C:\Users\karth>dspmqver -p2
Name:        IBM MQ classes for Java
Version:     9.0.0.0
Level:       p900-L160518.TRIAL
Build Type:  Production
Location:    file:/C:/Program Files/IBM/MQ/java/lib/com.ibm.mq.jar


C:\Users\karth>dspmqver -p3
Name:        IBM MQ
Version:     9.0.0.0
Level:       p900-L160518.TRIAL
BuildType:   IKAP - (Production)
Platform:    IBM MQ for Windows (x64 platform)
Mode:        64-bit
O/S:         Windows 8 Unknown x64 Edition, Build 9200
InstName:    Installation2
InstDesc:
Primary:     Yes
InstPath:    C:\Program Files\IBM\MQ
DataPath:    C:\ProgramData\IBM\MQ
MaxCmdLevel: 900
LicenseType: Trial

Name:        IBM MQ classes for Java
Version:     9.0.0.0
Level:       p900-L160518.TRIAL
Build Type:  Production
Location:    file:/C:/Program Files/IBM/MQ/java/lib/com.ibm.mq.jar

To use dspmqver to find out what version of the WebSphere MQ classes for JMS are being used, run the command shown below:

C:\Users\karth>dspmqver -p4
Name:        IBM MQ classes for Java Message Service
Version:     9.0.0.0
Level:       p900-L160518.TRIAL
Build Type:  Production [Built on IBM Corporation  pwa6480sr1fp10-20150711_01 (SR1 FP10) Windows Server 2008 R2]
Location:    file:/C:/Program Files/IBM/MQ/java/lib/com.ibm.mqjms.jar

Name:        Common Services for Java Platform, Standard Edition
Version:     9.0.0.0
Level:       p900-L160518.TRIAL
Build Type:  Production
Location:    file:/C:/Program Files/IBM/MQ/java/lib/com.ibm.mq.jmqi.jar

Name:        Java Message Service Client
Version:     9.0.0.0
Level:       p900-L160518.TRIAL
Build Type:  Production
Location:    file:/C:/Program Files/IBM/MQ/java/lib/com.ibm.mqjms.jar

Name:        IBM MQ JMS Provider
Version:     9.0.0.0
Level:       p900-L160518.TRIAL mqjbnd=p900-L160518.TRIAL
Build Type:  Production
Location:    file:/C:/Program Files/IBM/MQ/java/lib/com.ibm.mqjms.jar


C:\Users\karth>dspmqver -p5
Name:        IBM MQ
Version:     9.0.0.0
Level:       p900-L160518.TRIAL
BuildType:   IKAP - (Production)
Platform:    IBM MQ for Windows (x64 platform)
Mode:        64-bit
O/S:         Windows 8 Unknown x64 Edition, Build 9200
InstName:    Installation2
InstDesc:
Primary:     Yes
InstPath:    C:\Program Files\IBM\MQ
DataPath:    C:\ProgramData\IBM\MQ
MaxCmdLevel: 900
LicenseType: Trial

Name:        IBM MQ classes for Java Message Service
Version:     9.0.0.0
Level:       p900-L160518.TRIAL
Build Type:  Production [Built on IBM Corporation  pwa6480sr1fp10-20150711_01 (SR1 FP10) Windows Server 2008 R2]
Location:    file:/C:/Program Files/IBM/MQ/java/lib/com.ibm.mqjms.jar

Name:        Common Services for Java Platform, Standard Edition
Version:     9.0.0.0
Level:       p900-L160518.TRIAL
Build Type:  Production
Location:    file:/C:/Program Files/IBM/MQ/java/lib/com.ibm.mq.jmqi.jar

Name:        Java Message Service Client
Version:     9.0.0.0
Level:       p900-L160518.TRIAL
Build Type:  Production
Location:    file:/C:/Program Files/IBM/MQ/java/lib/com.ibm.mqjms.jar

Name:        IBM MQ JMS Provider
Version:     9.0.0.0
Level:       p900-L160518.TRIAL mqjbnd=p900-L160518.TRIAL
Build Type:  Production
Location:    file:/C:/Program Files/IBM/MQ/java/lib/com.ibm.mqjms.jar


Labels:

Comments

Post a Comment

adsrerrapop

Popular posts from this blog

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure ...
140 comments
Read more

IBM Websphere MQ Reason code list / mq reason codes / websphere mq error codes / mq error messages

Reason code list ================= The following is a list of reason codes, in numeric order, providing detailed information to help you understand them, including: * An explanation of the circumstances that have caused the code to be raised * The associated completion code * Suggested programmer actions in response to the code * 0 (0000) (RC0): MQRC_NONE * 900 (0384) (RC900): MQRC_APPL_FIRST * 999 (03E7) (RC999): MQRC_APPL_LAST * 2001 (07D1) (RC2001): MQRC_ALIAS_BASE_Q_TYPE_ERROR * 2002 (07D2) (RC2002): MQRC_ALREADY_CONNECTED * 2003 (07D3) (RC2003): MQRC_BACKED_OUT * 2004 (07D4) (RC2004): MQRC_BUFFER_ERROR * 2005 (07D5) (RC2005): MQRC_BUFFER_LENGTH_ERROR * 2006 (07D6) (RC2006): MQRC_CHAR_ATTR_LENGTH_ERROR * 2007 (07D7) (RC2007): MQRC_CHAR_ATTRS_ERROR * 2008 (07D8) (RC2008): MQRC_CHAR_ATTRS_TOO_SHORT * 2009 (07D9) (RC2009): MQRC_CONNECTION_BROKEN * 2010 (07DA) (RC2010): MQRC_DATA_LENGTH_ERROR * 2011 (07DB) (RC2011): MQRC_DYNAMIC_Q_NAME_ERROR * 2012 (07DC) (RC201...
3 comments
Read more

Message Broker (WMB) installation and setup on Linux

Message Broker (WMB) installation and setup on Linux Installing the Binaries As a first step download the trail version of the message broker binaries from IBM site and install them. this part is very simple and process is depends on your operating system. Like for windows, you have .exe file and Linux has rpm and unix you get pkg or other. After installation Set up a broker database [Windows] __ 1. Create the broker database, BRKDB. Open a WebSphere Message Broker Command Console: mqsicreatedb BRKDB This command also establishes the required ODBC connection. _ 2. Verify your user account for the broker database. [Linux] If you are creating Oracle databases for 32-bit brokers on Linux® and UNIX® systems, run the mqsi_setupdatabase command before you create a database. mqsi_setupdatabase– Database–Database_Home_Directory Eg:mqsi_setupdatabase oracle /oracle/product/9i/Db_1 Add $ORACLE_HOME/lib to the end of the MQSI_LIBPATH library search path environment variabl...
Post a Comment
Read more