Working with IBM
WebSphere message queues (MQ)
IBM WebSphere MQ is a family of network software products launched
by IBM in March 1992. It was previously known as MQSeries, a
trademark that IBM rebranded in 2002 to join the suite of WebSphere
products. WebSphere MQ, which is often referred to simply as "MQ"
by users, is IBM's Message Oriented Middleware offering. It allows
independent and potentially non-concurrent applications on a
distributed system to communicate with each other. MQ is available
on a large number of platforms (both IBM and non-IBM), including
z/OS (mainframe), OS/400 (IBM System i or AS/400), Transaction
Processing Facility, UNIX (AIX, HP-UX, Solaris), HP NonStop,
OpenVMS, Linux, OS 2200, and Microsoft Windows.
WebSphere MQ is often referred to as "MQ" or "MQ Series".
There are two parts to message queue (hence "MQ"):
- Messages are collections of binary or character (for
instance ASCII or EBCDIC) data that have some meaning to a
participating program. As in other communications protocols,
storage, routing, and delivery information is added to the message
before transmission and stripped from the message prior to delivery
to the receiving application.
- Message queues are objects that store messages in an
A queue Manager is a Websphere MQ prerequisite and system
service that provides a logical container for the message queue and
is responsible for transferring data to other queue managers via
There are several advantages to this technology:
- Messages do not depend on pure packet-based
transmissions, such as TCP/IP. This allows the sending and
receiving ends to be decoupled and potentially operate
- Messages will be delivered once and once only,
irrespective of errors and network problems.
NetDecision acts as so called WebSphere MQ Client. A WebSphere
MQ client is part of the product that can be installed on its own,
on a separate machine from the base product and server. It can
interact, by means of a communications protocol, with one or more
WebSphere MQ servers and connect to their queue managers.
IMPORTANT: The WebSphere
MQ Client package is not a part of NetDecision installation
package. The WebSphere MQ Client must be downloaded from
IBM website, installed and configured on NetDecision host
To start using MQ, you must first connect to Queue Manager by
using WMQConnect() function. At the end of
your script the Queue Manager connection must be closed by
using WMQDisconnect() function.
a message queuing queue manager.
|Disconnects from a message queuing queue
|Opens a message queue.
This function permits an application to read messages from, and
write messages to, a queue.
|Closes a message queue.
|Puts a message on a queue that was opened for
|Gets a message from a queue that was opened for
||The WMQ error handling related to a message queuing queue
||The WMQ error handling related to actual queues.
||Sets options used for reading messages from queue using