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

Troubleshooting Java/JMS SSL Configurations - Middleware News

 This document is intended to help diagnose WebSphere MQ V7 Java™ or JMS SSL setup errors. It lists most of the common configuration errors that can cause an SSL connection from a Java/JMS client to a queue manager to fail, and gives the course of action to resolve the problem. In each case the error can be diagnosed by a combination of the error seen in the client log - either a console output, trace file or SystemOut.log file - and the queue manager's error logs. The document is quite long, so the easiest way to find the potential error is to search for one of the errors seen in this list, then filter this list using the error from the opposite end of the channel. All cases here assume that 2-way authentication is being attempted (SSLCAUTH set to REQUIRED on the queue manager's SVRCONN channel). This is the default, and the errors are very similar for 1-way authentication (SSLCAUTH set to OPTIONAL). Symptom Instructions on collecting documentation...
Post a Comment
Read more

Using telnet to test connectivity between IBM Websphere MQ Client and MQ server - Middleware News

You are having trouble connecting a WebSphere MQ client to a MQ server, receiving errors that you can not connect to the MQ queue manager. One of the first things to determine is if the two machines can communicate, and using the telnet tool is one way to accomplish it. Symptom Receiving errors which state that a queue manager is not found or not available. Connection errors. For example: AMQ9213, AMQ9524, AMQ9202 or AMQ9508 or MQRC =2059 0x0000080b MQRC_Q_MGR_NOT_AVAILABLE. Please note, this is by no means an exclusive list of errors related to this type a problem but just a sample of some of the more common error messages and codes that might occur. Cause One possible cause is that the two machines can not communicate. May be the IP address or hostname was not properly specified by the MQ client. The port number might be incorrect. A queue manager is not running at the desired host. The queue manager could be running, but the corresponding listener is not runnin...
Post a Comment
Read more

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 ...
143 comments
Read more