Skip to main content

dspmq command in IBM MQ V9.2 - Middleware News

 [mqm@localhost ~]$ uname -aLinux localhost.localdomain 4.18.0-193.el8.x86_64 #1 SMP Fri May 8 10:59:10 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
[mqm@localhost ~]$


[mqm@localhost ~]$ dspmqver -a
Name:        IBM MQ
Version:     9.2.0.0
Level:       p920-L200710.DE
BuildType:   IKAP - (Production)
Platform:    IBM MQ for Linux (x86-64 platform)
Mode:        64-bit
O/S:         Linux 4.18.0-193.el8.x86_64
O/S Details: CentOS Linux 8 (Core)
InstName:    Installation1
InstDesc:
Primary:     No
InstPath:    /opt/mqm
DataPath:    /var/mqm
MaxCmdLevel: 920
LicenseType: Developer

Name:        IBM MQ Java Runtime Environment
Version:     java full version JRE 1.8.0 IBM Linux build 8.0.6.10 - pxa6480sr6fp10-20200408_01(SR6 FP10)
Location:    file:/opt/mqm/java/jre64/jre

Name:        IBM MQ classes for Java
Version:     9.2.0.0
Level:       p920-L200710.DE
Build Type:  Production
Location:    file:/opt/mqm/java/lib/com.ibm.mq.jar

Name:        IBM MQ classes for Java Message Service
Version:     9.2.0.0
Level:       p920-L200710.DE
Build Type:  Production [Built on IBM Corporation  8.0.5.17 - pxa6480sr5fp17-20180627_01(SR5 FP17) Linux]
Location:    file:/opt/mqm/java/lib/com.ibm.mqjms.jar

Name:        Common Services for Java Platform, Standard Edition
Version:     9.2.0.0
Level:       p920-L200710.DE
Build Type:  Production
Location:    file:/opt/mqm/java/lib/com.ibm.mq.jmqi.jar

Name:        Java Message Service Client
Version:     9.2.0.0
Level:       p920-L200710.DE
Build Type:  Production
Location:    file:/opt/mqm/java/lib/com.ibm.mqjms.jar

Name:        IBM MQ JMS Provider
Version:     9.2.0.0
Level:       p920-L200710.DE mqjbnd=p920-L200710.DE
Build Type:  Production
Location:    file:/opt/mqm/java/lib/com.ibm.mqjms.jar


Name:        IBM MQ Advanced Message Security
Version:     9.2.0.0
Level:       p920-L200710.DE
BuildType:   IKAP - (Production)

Name:        IBM MQ AMQP Support
Version:     9.2.0.0
Level:       p920-L200710.DE
Build Type:  Production
Location:    file:/opt/mqm/amqp/lib/AMQPListener.jar

Name:        IBM MQ Telemetry
Version:     9.2.0.0
Level:       p920-L200710.DE
Build Type:  Production
Location:    file:/opt/mqm/mqxr/lib/MQXRListener.jar

AMQ8250I: The 32-bit GSKit component is not installed.

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

Name:        WebSphere Application Server
Version:     20.0.0.3
Location:    file:/opt/mqm/web

AMQ8250I: The 64-bit IBM MQ Replicated Data Queue Managers component is not installed.

Name:        IBM MQ Managed File Transfer
Version:     9.2.0.0
Level:       p920-L200710.DE
Build Type:  Production

Name:        libCurl
Version:     libcurl/7.71.1 GSKit 8.0.55.16
Location:    file:/opt/mqm/lib64/libcurl.so

Name:        libedit
Version:     libedit 0:63:0 (20191231-3.1)
Location:    file:/opt/mqm/lib64/libedit.so

Name:        Bridge for Salesforce (jetty)
Version:     9.3.27.v20190418
Location:    /opt/mqm/mqsf/prereqs/jetty*.jar

Name:        Bridge for Salesforce (cometd)
Version:     3.1.13
Location:    /opt/mqm/mqsf/prereqs/cometd*.jar

Name:        Bridge for Salesforce (slf4j)
Version:     1.7.30
Location:    /opt/mqm/mqsf/prereqs/slf4j*.jar

Name:        Bridge for Blockchain (jetty)
Version:     9.3.27.v20190418
Location:    /opt/mqm/mqbc/prereqs/jetty*.jar

Name:        Bridge for Blockchain (sdk)
Version:     2.1.3
Location:    /opt/mqm/mqbc/prereqs/fabric-gateway-java.jar
[mqm@localhost ~]$
[mqm@localhost ~]$
[mqm@localhost ~]$
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
139 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
2 comments
Read more

IBM WebSphere MQ – Common install/uninstall issues for MQ Version on Windows - Middleware News

Creating a log file when you install or uninstall WebSphere MQ WebSphere MQ for Windows is installed using the Microsoft Installer (MSI). If you install the MQ server or client through launchpad , MQPARMS or setup.exe , then a log file is automatically generated in %temp% during installation. Alternatively you can supply parameters on the installation MSI command msiexec to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). If you uninstall through the Windows Add/Remove programs option, no log file is generated. You should either uninstall from the MSI command line and supply parameters to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). For details on how to enable MSI logging, see the following article in the WebSphere MQ product documentation: Advanced installation using msiexec For details on how to enable system-w
Post a Comment
Read more