IBM WMQ Interview Questions

If you're looking for IBM WebSphere Message Queue Interview Questions, you are at right place. There are lot of opportunities from many reputed companies in the world. According to research IBM WebSphere Message Queue market share of about 15.7%. So, You still have opportunity to move ahead in your career in IBM WebSphere Message Queue. Mindmajix offers advanced IBM WebSphere Message Queue Interview Questions that helps you in cracking your interview & acquire dream career.

Are you intereted in taking up for IBM WebSphere Message Queue Certification Training? Enroll for Free Demo on IBM WebSphere Message Queue Training!


Q. What is MQ and what does it do?
MQ stands for MESSAGE QUEUEING. WebSphere MQ allows application programs to use message queuing to participate in message-driven processing. Application programs can communicate across different platforms by using the appropriate message queuing software products.

Q. What is Message driven process?
When messages arrive on a queue, they can automatically start an application using triggering. If necessary, the applications can be stopped when the message (or messages) have been processed.

Q. What are advantages of the MQ?
1. Integration.
2. Asynchrony
3. Assured Delivery
4. Scalability.

Q. How does it support the Integration?
Because the MQ is independent of the Operating System you use i.e. it may be Windows, Solaris,AIX.It is independent of the protocol (i.e. TCP/IP, LU6.2, SNA, NetBIOS, UDP).It is not required that both the sender and receiver should be running on the same platform

Q. What is Asynchrony?
With message queuing, the exchange of messages between the sending and receiving programs is independent of time. This means that the sending and receiving application programs are decoupled; the sender can continue processing without having to wait for the receiver to acknowledge receipt of the message. The target application does not even have to be running when the message is sent. It can retrieve the message after it is has been started.

Q. What are the hardware and Software requirements for MQ Installation in AIX?
WebSphere MQ for AIX, V5.3 runs on any machine that supports the AIX V4.3.3 PowerPC® 32.bit, or AIX® V5.1 Power 32 bit only operating system.
Disk Storage: Typical storage requirements are as follows:
1 Server installation: 50 MB
2. Client installation: 15 MB
3 Data storage (server): 50 MB
4. Data storage (client): 5 MB.

Software Requirements:
Operating system: The operating systems supported by WebSphere MQ for AIX, V5.3 are:
1. AIX V4.3.3, with PTF U472177, running in a 32 bit environment, on 32 or 64 bit hardware.
2. AIX V5.1, with PTFs U476879, U477366, U477367 and U477368, and APAR fix IY29345 running 32 bit kernel running on 32 or 64 bit hardware.
3. AIX V5.1, with PTF U476879, U477366, U477367 and U477368, and APAR fix IY29345 running 64 bit kernel running on 64 bit hardware.

Connectivity The network protocols supported by WebSphere MQ for AIX, V5.3 are:
2. SNA LU 6.2.
Databases: DB2 7.1, 7.2
Oracle 8i and 9i
Sybase v12 or v 12.5
Java: If you want to use the Java Messaging Support, you need the Java Runtime Environment Version 1.3 or later

Q. What are the software and hardware requirements for installing MQ on Windows?
MQ v 5.3 supports Windows 2000, Windows 2000XP,Windows 2000NT,
Windows 2003 SE, Windows 2003EE.

Disk Storage: Typical storage requirements are as follows:
1 Server installation: 50 MB
2. Client installation: 15 MB
3 Data storage (server): 50 MB
4. Data storage (client): 5 MB.

Connectivity The network protocols supported by WebSphere MQ for AIX, V5.3 are:
2. SNA LU 6.2.
3. LU 6.2
4. NetBIOS

Databases: DB2 7.1, 7.2
Oracle 8i and 9i
Sybase v12 or v 12.5
Java: If you want to use the Java Messaging Support, you need the Java Runtime Environment Version 1.3 or later

Q. What is a Message and what does it contain?
A message is a string of bytes that is meaningful to the applications that use it. Messages are used to transfer information from one application program to another (or between different parts of the same application). The applications can be running on the same platform, or on different platforms.
WebSphere MQ messages have two parts:
1. The application data. The content and structure of the application data is defined by the application programs that use it.
2. A message descriptor. The message descriptor identifies the message and contains additional control information, such as the type of message and the priority assigned to the message by the sending application. WebSphere MQ defines the format of the message descriptor. For a complete description of the message descriptor,

Q. What is the Max Length of the message does MQ support?
The default maximum message length is 4 MB, although you can increase this to a maximum length of 100 MB (where 1 MB equals 1 048 576 bytes).

Q. What is the difference between Persistent and Non Persistent Messages?
In Web Sphere MQ, messages can be either persistent or non persistent. Persistent messages are logged and can be recovered in the event of a WebSphere MQ failure. Thus, persistent messages are guaranteed to be delivered once and only once. Nonpersistent messages are not logged. Web Sphere still guarantees to deliver them not more than once, but it does not promise to deliver them once.

Q. What is the effect of using Persistant messages?
Persistent messages are usually logged. Logging messages reduces the performance of your application, so use persistent messages for essential data only. If the data in a message can be discarded if the queue manager stops or fails, use a nonpersistent message.

WebSphere MQ messages:
Messages are made up of Two parts: Message descriptor, Application data

Q. Types of messages?
Datagram: A Message sent with no response expected.
Request: A Message sent for which a response is expected.
Reply: A Response Message for a requested message.
Report: A Message that describes the occurrence or event

Q. Sizes?
Qmanagerà10000 Msgs Maxmsglengthà4 Mb
Queueà5000 Msgs Maxmsglengthà4 Mb

Q. What is the attribute used to see the Message length?

Q. What is MQ Client?
A Web Sphere MQ client is a component that allows an application running on a system to issue MQI calls to a queue manager running on another system. The output from the call is sent back to the client, which passes it back to the application.

Q. What is MQ Server?
A Web Sphere MQ server is a queue manager that provides queuing services to one or more clients. All the Web Sphere MQ objects, for example queues, exist only on the queue manager machine (the Web Sphere MQ server machine), and not on the client. A Web Sphere MQ server can also support local Web Sphere MQ Applications

Q. What are the Objects used in Web sphere MQ?
1. Queue Manager
2. Queues
3. Channels
4. Processes
5. Name lists.

Q. Mention the No of Characters required for creating names of the MQ objects?
For MQ Channels it is 20 Characters
For Remaining objects it is 48 characters.

Q. What about is the Default port number for MQ Queue Manager?

Q. Difference between MQSC commands and Control commands?
MQSC Commands – These commands are used to handle the admin related functions for the components that are present in the MQ Series. In general MQSC commands are used for creating and maintaining Message channels, Queue Managers, Clusters etc…
Control Commands – These commands are used to manage the processes and services that are helpful in the functioning of the MQ Series. In general these commands are used for Channel listener, Channel Initiator, Trigger monitor etc…

Q. Is the MQSC attributes are Case sensitive?
MQSC commands, including their attributes, can be written in uppercase or lowercase. Object names in MQSC commands are folded to uppercase (that is, QUEUE and queue are not differentiated), unless the names are enclosed within single quotation marks. If quotation marks are not used, the object is processed with a name in uppercase.
After entering in to queue manager we can find script commands.
Script commands are same for every queue manager.
(These Commands should be used in CAPITAL LETTERS)
1. DEFINE: To define/create MQ manager objects like queue, Channels, process, and listener.
2. ALTER: to update or modify the existing objects
3. DISPLAY: to view all the properties of a particular object or to Display all objects
4. DELETE: to delete created objects
5. CLEAR: to clear the message from the queue
6. END :-to come out of the queue manager
7. PING :-to check whether other side channel / queue manager is ready to accept our request.
8. START :- to start the particular channel or listener
9. STOP :-to stop particular channel or listener
10. REFRESH :-used to refresh the security every time after giving or executing, set mgr or command for queue manager or object
11. RESET :-used to reset channel,cluster,queue manager
12. RESOLVE :-to resolve the channel which is in indoubt state
13. SUSPEND :-to suspend a queue manager from a cluster environment
14. RESUME :-to remove a queue manager from a cluster environment

Q. How can we write the MQSC commands that have too many parameters?.
For commands that have too many parameters to fit on one line, use continuation characters to indicate that a command is continued on the following line:
1. A minus sign ( ) indicates that the command is to be continued from the start of _ the following line.
2. A plus sign (+) indicates that the command is to be continued from the first nonblank character on the following line.

Q. What is programmable command format (PCF) commands?
These commands are issued from a programme for local or remote administration done by programmers.

Q. What are commands used for creating the Queue manager from the Command prompt?
Here -q used to define the Queue manager QM1 as a Default Queue manager
-d is used to define the default transmission Queue -u is used to define the default dead letter queue.

Q. How can U make the existing Queue Manager as an default Queue Manager?
On Windows systems, use the Web Sphere MQ Services snap-in to display the properties of the queue manager, and check the Make queue manager the default box. You need to stop and restart the queue manager for the change to take effect.

Q. Where are the backup files are present after creating the Queue Manager?
Windows systems: If you use Web Sphere MQ for Windows NT and Windows 2000, configuration information is stored in the Windows Registry.
UNIX Systems:
1. When you install the product, the Web Sphere MQ configuration file (mqs.ini) is created. It contains a list of queue managers that is updated each time you create or delete a queue manager. There is one mqs.ini file per node.
2. When you create a new queue manager, a new queue manager configuration file (qm.ini) is automatically created. This contains configuration parameters for the queue manager.

Q. What is the command used for starting the Queue Manager?
strmqm QMName

Q. What is the command used for stopping the Queue manager?
endmqm -w QMName
The command waits until all applications have stopped and the queue manager has ended.
endmqm –i QMName
This type of shutdown does not wait for applications to disconnect from the queue manager.

Q. What’s the message code for Stopping a Queue Manager?
AMQ4044 Queue manager stopping

Q. What is the command used to delete the QueueManager?
dltmqm QMName

Q. Display the attributes of the Queue Manager QM1?
runmqsc QM1 Display qmgr

Q. Identification/Authorization
I have an IBM Websphere MQ v6.0 queue manager running on Solaris 9. I want to prevent my staff members who have limited WebSphere MQ experience to make changes to the WMQ network.

Q. Is there a way to do this?
A: One way is to use Dale Lane’s “Using WebSphere MQ Explorer as a read-only viewer”:
The WebSphere MQ Explorer GUI provides a user-friendly way to administer your queue managers. It can be used as a read-only ‘viewer’. If you have some staff that doesn’t have authority to make changes to the WMQ network, but need them to be able to monitor what is happening, this would let them use WMQ Explorer to do it.
The following are the steps required to set this up for a single queue manager and highlight a couple of potential problems to watch out for.
Steps to carry out on the machine hosting the queue manager:
1. Create a user – making sure that the user is not a member of the MQM group.
2. Start a channel listener for the queue manager.
3. Create a server-connection (SVRCONN) channel on the queue manager – setting the MCAUSER attribute to the user name defined in step 1.
4. Use setmqaut to specify which objects you want the user to be able to see.
First, you need permission to connect to the queue manager:
setmqaut -m YOUR_QUEUE_MANAGER -t qmgr -p YOUR_USER_NAME +connect +inq +dsp
Next is to give permission to the queues that WMQ Explorer will need:
setmqaut -m YOUR_QUEUE_MANAGER -t q -n SYSTEM.ADMIN.COMMAND.QUEUE -p YOUR_USER_NAME +get +browse +inq +put
setmqaut -m YOUR_QUEUE_MANAGER -t q -n SYSTEM.MQEXPLORER.REPLY.MODEL -p YOUR_USER_NAME +inq +browse +get +dsp
setmqaut -m YOUR_QUEUE_MANAGER -t q -n ‘AMQ.**’ -p YOUR_USER_NAME +all
setmqaut -m YOUR_QUEUE_MANAGER -t q -n ‘MQAI.**’ -p YOUR_USER_NAME +all
Then, you could give access to all objects of a certain type, such as being able to display all channels:
setmqaut -m YOUR_QUEUE_MANAGER -t channel -n ‘**’ -p YOUR_USER_NAME +dsp
You might want to include additional permissions, such as the ability to browse messages on queues or inquire their attributes:
setmqaut -m YOUR_QUEUE_MANAGER -t q -n ‘**’ -p YOUR_USER_NAME +dsp +inq +browse
Review the System Administration Guide section on setmqaut for more detail on the options available.
Steps to carry out on the WebSphere MQ Explorer machine:
1. Right-click on ‘Queue Managers’ and choose “Show Queue Manager”.
2. Click on the “Add” button.
3. Enter the queue manager name and click “Next”.
4. Fill in the hostname of the machine hosting the queue manager, the TCP port number for the channel listener you started and the name of the server-connection channel you created.
5. Click “Finish”.

Things to watch out for:
Note 1: The WebSphere MQ Explorer user will only see the objects that they have the authority to see. So it’s worth being aware that in such a setup, the Explorer is no longer showing a definitive view of the objects on the queue manager.
Note 2: Attempts to view an object, which the user isn’t authorized to display, can result in an authorization event. See the Monitoring WebSphere MQ section on ‘Event Monitoring’ (f for more information. To summarize, if a queue manager has authorization events (AUTHOREV) enabled, every attempt to access something which a user is not authorized to will cause an event message to be put to the SYSTEM.ADMIN.QMGR.EVENT queue. So, for example, if a user does not have access to display queues, then one authorization event message will be put to SYSTEM.ADMIN.QMGR.EVENT for each queue they cannot access every time the Queues view in WMQ Explorer is refreshed. This could result in a lot of messages, so you may want to disable AUTHOREV or take steps to handle these messages.
Note 3: If you want to look at queues with WebSphere MQ Explorer in this way, you will need to have Refresh Pack or greater applied. A bug in the Explorer prior to this meant that the failure to display SYSTEM.AUTH.DATA.QUEUE (a queue which it is not possible to give a non-mqm user access to) prevented any queues from being displayed. This is documented more fully in APAR IC49051 (
Note 4: When I talk about the WMQ Explorer, I’m referring to the Eclipse-based Explorer that comes with WebSphere MQ version 6. I’ve not tried this on the v5.3 Windows WMQ Explorer.
Note 5: In the examples above, we used the -p option for setmqaut – specifying a specific user. This was done for simplicity but in practice using -g to specify a group is often easier to manage. See the System Administrative Guide for the full syntax.

Q. Websphere MQ & DB2 MQListener
I have a system that receives a message and calls a DB2 stored procedure to process it via a db2mqlsn command (on Windows). Now I’m migrating the system to Linux and the only thing left for me to do, is to setup the db2mqls to start automatically after the MQ manager starts.
My problem is that running the command won’t return a result because it keeps running indefinitely. Here’s part of what I got on the script (on /etc/init.d/):
su – mqm -c “cd /opt/mqm/bin; ./strmqm MYQUEUEMANAGER “
su – db2inst1 -c “cd /opt/ibm/db2/V9.1/bin; ./db2mqlsn run -configDB MYDB -config mydbconfig”
How can I setup a command call like that in the script that I have created that starts my MQ manager at boot (on /etc/init.d/)?
A: You might want to put the command into the background. At the end of the command just put a ‘&’:

runmqlsr -m MYQMGR -t tcp -p 1414 &

Q. Get support from IBM for MQ5.3 for Tandem Nonstop
What’s the best way to file problem reports about version 5.3 of MQ for Tandem Nonstop systems?
I have access to IBMLINK, what is the “Software Component Id” that should be used for the Tandem based 5.3 products? I have tried all of the numbers I have found in the documentation and in the read me files and none of them work.
A: Try using 5724A39. Also, you should try the ESR interface to IBM for the Tandem.
ESR will allow you to generate a PMR (case) but like all things, you need to be authorized by your companies IBM services coordinator.

Check Out IBM WebSphere Message Queue Tutorials

Q. Saving change impact on MQ
We are running 5.2 and 5.3. Our servers had the MS DST patches applied and the server OS time was correct; however, Eclipse was still showing times that is one hour behind.
Does day light saving change has any impact on MQ application?
A: Customers need to ensure that the JRE being used by eclipse that can be customized by customers is up to date by running the JTZU against the specified version that they are using. The actions that need to be taken are as follows:
1. Identify the JDK in use by eclipse. This can be done launching the WebSphere MQ explorer and then following the menu tree:
Window ->Preferences -> Java -> Installed JREs
 A list of one or more installed JREs is displayed in the panel. One of these JREs will be “checked” indicating that it is the one that eclipse will use to run Java code (MQ Explorer in this case) against. Make a note of this location for example C:JDKJ150 – Download and extract the appropriate JTZU from:

1. Use the command and change directories to the extract location.
2. Alter the runjtzuenv.bat file to set the location of a JVM that the tool will be launched under. For example:
rem set JAVA_HOME to the a Java installation directory
set JAVA_HOME=c:jdkj142jre
rem set NOGUI
set NOGUI=false
This would instruct the tool to run against a JRE (in this case 1.4.2) at a location c:jdkj142jre:
1. Launch the tool using runjtzu.bat
2. Select ‘Interactive mode’ and click start button
3. Ensure customer make a note of the warning message regarding applying maintenance
4. Enter the location of the java runtime being used by eclipse, for example c:jdkJ150jre (please note that ‘jre’ is needed here)
5. Click update to begin the update process.
6. Customer should then re-test the MQExplorer and determine if the problem persists.

Q. FDC Files filling up the disk space
We are using the MQ version 5.3 with the CSD Version 5 in Windows Server 2000. Since last 2 weeks, the FDC files are being generated continuously and now have occupied the drive completely. We have deleted some old FDC to free some space.
How do I stop these FDCs’ from getting generated?
A: This one’s from IBM:
Problem: You are running WebSphere® MQ v5.3. You monitor MQ with a user developed shell script, which runs runmqsc every 10 minutes. This script produces FDC files for probe id XC076001 and reason code of xecX_E_CONV_NOT_SUP. These FDC files also are reporting “Cat CCSID 954, user CCSID 819”. This means that the message catalog is using CCSID 954. The FDC does not stop runmqsc or the script. The environment where the messages come from is the one issuing the runmqsc commands and is also using CCSID 819.
Cause: This problem occurs because you have LC_ALL set to blank or no value. In this case the value of LC_ALL= will take precedence over LANG. So the default locale, English 819, is taken. Since there is no conversion table for 950 to 819 available the message display fails.
Solution: Set LC_ALL=ja and export this in a shell. Issue locale command and this should display LANG and LC_* as “ja”. Once the display shows the values correctly, issue runmqsc and check if the problem is resolved.
Also, it is suggested that you set all locale variables to the same value. In this case, either set them all to be “ja” or set all to be Japanese.
The locale output for the failing machine shows:

Q. Connection B/W MQ running on SOLARIS and Z/OS
We installed MQ Server 5.3 on a SUN Solaris Host. How would I create a connection b/w Solaris MQ and Mainframe MQ? Is there any file in which I need to give the IP address of remote host?
A: You need to create MQ channels between the two queue managers. Two manuals to look at: MQ Intercommunications and MQ Script Command Reference.
Briefly, channels come in pairs; one Sender and one Receiver, for example:
Messages flow one way on a channel. If you need messages to flow in the other direction, you will need to create a second pair of channels. Sender channels send messages from a transmission queue (xmitq). The QRemote definition specifies the name of the xmit queue. The programmer opens the QRemote definition.
To get messages from SUN to z/OS, create:
On the SUN qmgr: one Sender channel from SUN to z/OS. Let’s call it SUN.ZOS. On the Sender channel definition you specify ipaddress (port) of the z/OS qmgr and listener.
On z/OS: one Receiver channel from SUN to z/OS. Exact same name: SUN.ZOS.
To get messages from z/OS to SUN, create the inverse channel pair. Let’s call it ZOS.SUN:
On z/OS: one Sender channel from z/OS to SUN, specifying SUN qmgr ipaddress (port).
On SUN: one Receiver channel from z/OS to SUN. Exact same channel name: ZOS.SUN.
Examples for each platform type are in the Intercommunications manual.
You will need to have IP running on both SUN and z/OS and you will need to have listeners running on both, as well.

Q. Unsubscribing topic with command
We have a situation where we need to unsubscribe a topic in Publish Subscribe setup. The same is not working through our program. Can we issue any command that can be used to unsubscribe a topic or all the topics?
A: Send an “unsubscribe” message with RFHUtil or similar. Another option is to delete the subscription through the broker admin interface.

Q. Same message consumed by two different application
We have three qmgrs QM1, QM2 & QM3 which are connected to three applications App1 to QM1, App2 to QM2, & App3 to QM3. The requirement is to have messages sent by App1 to QM2 (Distributed Queing). This message has to be consumed by App2 from QM2 and also the same message has to be sent to QM3 to be consumed by App3.
The app team informed us that there won’t be any change in the code so we have to get this done only with MQ. Is this achievable using MQ?
A: Try the mirrorq exit. Please bear in mind the mirrorq exit is sample code & not necessarily production strength. If you’re going to use this over anything other than the short term, review it and be sure you’re confident of its robustness and your ability to support it.

Q. MQ update DB on another computer
From Machine A, a client program sends a request to MQ server in Machine B. Now, that computer updates the DB situated in another Machine C. Is this possible only with triggering?
A: Your scenario relies on Machine A being able to place a request message on Machine B, hence you’d need an MQ client connection between A and B or server side channels to carry the message. Machine B must be able to access the database on Machine C, so this implies a client link between the two machines. Unless they have replicated databases, RPC links, piped data transfer or an MQ link running PM4Data.
You would also need a triggered application on Machine B unless the application on Machine B was written to be long running or there wasn’t an application on Machine B. This could only be written in Java or C or a language with a supported environment on Machine B, unless there wasn’t an application at all.

Q. SSL certificate selection
I am having a queue manager to whom 10 different applications connects. I want to make them connect over SSL svrconn channels and for them to represent different unique certificates. So all 10 application key repositories will have same queue manager certificate but my queue manager key repository will have 10 different certificates, one from each application.
My Q. is how queue manager will know which certificate to use for handshake when a connection request comes?
A: QMGR will use their cert from keystore which alias name is Ibmwebspheremq during handshake.
Then in your configuration QMGR compares sent application public certificate with certificates from keystore.
Consider using standard PKI with CA rather than self-signed cert.

Q. Max message size overhead
What is the overhead on MQ for having a large value for maximum message length in a queue definition?
For example, if I define the maximum message length to say 10MB but the maximum message length is only initially set at 1MB.
Can this affect any performance on the settings else where?
A: The space used to hold the value for MaxMsgLen is a constant; it’s the same no matter what number is used for MaxMsgLen.
The only way that, for example, setting the MaxMsgLn for all queues, channels and qmgrs to the maximum possible will have any performance impact is if your logs are not sized to handle that size of message AND someone actually SENDS a big message.
Set it to the largest value you can possibly handle, and then you don’t have to worry about changing it every time an application needs a bigger value. Setting the MaxMsgLn doesn’t affect anything else. Sending a large message does.
Max Message length is only a safety feature to not receive unexpectedly large message.

Q. What is IBM MQ Series? What is the significance of MQ Series?
1. A middle ware from IBM
2. It has runtime managers such as Queue Managers and Queues
3. Queue is an object which holds messages of various formats – XML/text/byte
4. Queue manger maintains and manages objects like Queues, channels
5. Various listener applications listen to these queues for grabbing the messages, followed by processing these messages
6. Java Messaging Service is one of the standards provided by JEE specification for asynchronous messaging
7. The queues can be defined in JEE container and send messages on these queues
8. Message Driven Bean can be configured for listening the JMS queues
9. When a message is on the JMS queue, the corresponding MDB’s onMessage() method is invoked and the message processing can be done

Significance of Websphere MQ Series:
1. WebSphere MQ will significantly improves the flow of information across an enterprise
2. The message is placed and adjusted for dynamic business requirements
3. MQ series reduce maintenance, integration costs and acts as a bridge to various technologies
4. MQ Series reduces costs and all the disruptions are processed from data loss
5. Allows ongoing maintenance efforts through universal service delivery
6. Security breaches are eliminated and insures the compliance through message and transaction integrity

Q. What is a Message and what does it contain?
1. A message is a string of bytes which has a meaningful usage in applications
2. Messages are utilized to transfer information across applications
3. The applications can run on the same or on different platforms
Websphere MQ messages contain:
1. Application data: The application’s content and data is defined by the application programs which uses it.
2. Message Descriptor: The message is identified by the message descriptor and contains additional control information, like the type of message and priority assigned to the message

Q. How to define a buffer pool for holding messages in main storage? Explain
1. Buffer pool is defined by using DEFINE BUFFPOOL
2. DEFINE BUFFPOOL can be issued only from CSQINP1 data set
3. DISPLAY USAGE TYPE(PAGESET) can be used for displaying buffer pool information
4. The synonym DEF BP can also be used instead of DEFINE BUFFPOOL
DEFINE BUFFPOOL(buf-pool-id)
1. Parameter descriptions
(buf-pool-id) Buffer pool identifier, and a mandatory entry
2. An integer which in the range from zero through 15.
3. Integer represents the number of 4096-byte buffers

Q. What are the Telemetry Capabilities?
1. Telemetry enables Remote sensors, smart meters etc., to be easily connected with the existing applications and services
2. Telemetry provides messaging technique for optimizing the needs of sensor networks
3. Decision makers can focus on significant data and events
4. It enables responses of rapid and proactive nature for current situations
5. Network traffic is reduced and responsiveness increases by only sending significant data and events
6. It encourages various device manufacturers to enable their sensors that are ready to connect into 7. IBM connectivity solutions
8. Enables the custom implementation of messaging that is device-side for connecting unusual devices
9. Optimizes the use of network to lower the traffic
10. The pay-per-byte costs can be reduced in satellite networks

Q. What are the Integration and supported environments in IBM MQ?
1. IBM MQ supports in virtual integration
2. Supports more than 80 platform configurations, including z/OS support
3. Integrates with CICS,IMS,DB2,Microsoft .Net and JEE environments
4. Supports Message Queue Interface and Industry standards such as JMS interface along with integrated public-and-subscribe support
5. Internet secure communication is supported with industry standard SSL
6. IBM MQ supports IP V6
7. Awarded Common Criteria certification
8. Supports end-to-end governance with Extended Security Edition

Q. Mention some rules for using MQSC commands.
1. Each command of MQSC starts with a primary parameter, followed by a secondary parameter
2. The name or generic name of the object should be followed by secondary parameter
3. The keywords, parentheses and values could be separated by unlimited number of blanks and commas
4. At least one blank immediately preceding each parameter is mandatory, except on z/OS
5. Blanks enclosed within a pair of quotations marks are significant
6. Repeated parameters are not allowed
7. String can contain blanks, lowercase alphabets or special characters other than period(.), forward slash(/), underscore(_) percent sign(%) must be enclosed in a single quote
8. A blank pair of parenthesis is invalid with out significant information enclosed in between
9. Keywords are not case sensitive

Q. What is QueueManager in IBM WebSphere MQ ? What does QueueManager do?
QueueManageris primary component of WebSphere MQ or WMQ. QueueManager is responsible for storing and routing messages to other Queue Manager within MQ and it also communicate with outside world e.g. Java program or any other MQ client.

Q. What is Channel in IBM WebSphere MQ?
In WebSphere MQ or WMQ, Queue Manager use channel to transmit messages to other QueueManager. Channel carries one way traffic in MQ Series (i.e. channels are uni directional). You can have either sending channel or receiving channel in MQ.

Q. What is dead letter queue in IBM MQ Series?
Dead letter Queue in WebSphere MQ is a queue which is used by QueueManager to archive messages for a non existent queue. For example of QueueManagerQMGR, receives a messages for queue ABC and if it didn’t exist on that QueueMangaer then message will be routed to dead letter queue.

Q. What is CCDT file on WebSphere MQ or WMQ?
CCDT file or Client Channel Definition table is a binary file which contains connection details required by MQ clients e.g. Java application using JMS to connect to MQ Server. In order to connect to MQ Server, MQ clients needs MQ Server host name, MQ Server port name and server channel name. All these details are encapsulated in CCDT file named as AMQCLCHL.TAB. In order to create MQ Connection, MQ clients needs location of this file, which is provided as configuration. most of MQ errors comes either with incorrect CCDT files.

Q. What is SSLPEER in IBM Websphere MQ?
Another interesting and frequently asked WebSphere MQ Interview Q.. You can easily answer this MQ Q. if you connected MQ via SSL. SSLPEER is a String usually DN (Distinguished name) of MQ Client which connect to QueueManager securely using QueueManager. This is a mechanism WMQ uses to identify client. In case of Java or JMS client, SSLPEER is DN of client certificate stored in its keyStore and sent to server during SSL handshake.

Q. What is difference between dead letter queue and backout queue in Websphere MQ?
This is a follow Q. of previous MQ interview Q. “What is dead letter queue in MQ Series”. As we have seen that dead letter queue is used to store messages which is receives for non existent queue. On the other hand backout queue are application specific queue.If MQ client is not able to process message and ask for redelivery, message is redelivered to client with incremented delivery count. Once this deliveryCountcrossed a configured threshold message is moved to back-out queue for later processing or error handling. In short if MQ Series not able to deliver message to client after a preconfigured attempt, WMQ moves message to backout queue.

Q. What is difference between binding connection and client Connection?
This MQ Interview Q. is not common or frequently asked, but good to know. If MQ clients sits on same physical server where QueueManager is located than it can create binding connection which is relatively faster than client connection, which is usually created by MQ clients residing on same network but not same host. Most of application uses MQ client connection to connect QueueMangaer, which is easy and flexible.

Q. What is difference between local queue and remote queue in WMQ?
Rather simple and fact based MQ Series interview Q.. This is asked to see whether candidate is familiar with MQ Series terminology or not. In WebSphere MQ, local queues are queue on same QueueManager while remote queue refers to queue on different QueueManager.

Q. Which WebSphere MQ version have you worked ? What is the latest IBM WebSphere MQ version?
This MQ interview Q. is more to know that which version of MQ have you worked upon, do you familiar with any issue with that particular version or many major changes to previous or next version etc. Based upon your answer, you may expect some follow-up Q.s. By the way current version of WMQ is WebSphere MQ 7.5 but it always good to check IBM’s MQ website for latest version.

Q. Apart from WebSphere MQ, have you used any other Message Oriented Middleware (MOM) or any other MQ Series provider?
I like this MQ Interview Q. to ask because many times having experience of one or more Messaging technology or Messaging Middle-ware is good. As I said earlier Tibco RV, Tibco EMS and MQ Series are some of the popular messaging technology used in Java applications. On MQ front there are couple of more MQ providers e.g. Sonic MQ and Active MQ. Active MQ is free and from Apache software foundation, which is easy to install and use. You can use Active MQ for your development and test environment. it also provide a useful Queue browser to keep track of Queues and number of message on it.


Explore IBM WebSphere Message Queue Sample Resumes! Download & Edit, Get Noticed by Top Employers!Download Now!



Get Updates on Tech posts, Interview & Certification questions and training schedules