BM Websphere MQ interview Questions Part 1 - Middleware News

IBM Websphere MQ interview Questions Part 1 - Middleware News ==================

=============================================
What is MQ and what does it do? Ans. MQ stands for MESSAGE QUEUEING. WebSphere M
Q allows application programs to use message queuing to participate in message-d
riven processing. Application programs can communicate across different platform
s by using the appropriate message queuing software products. What is Message dr
iven process? Ans . When messages arrive on a queue, they can automatically star
t an application using triggering. If necessary, the applications can be stopped
when the message (or messages) have been processed. What are advantages of the
MQ? Ans. 1. Integration. 2. Asynchrony 3. Assured Delivery 4. Scalability. How d
oes it support the Integration? Ans. Because the MQ is independent of the Operat
ing 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 th
e sender and receiver should be running on the same platform What is Asynchrony?
Ans. With message queuing, the exchange of messages between the sending and rec
eiving programs is independent of time. This means that the sending and receivin
g application programs are decoupled; the sender can continue processing without
having to wait for the receiver to acknowledge receipt of the message. The targ
et application does not even have to be running when the message is sent. It can
retrieve the message after it is has been started. What are the hardware and So
ftware requirements for MQ Installation in AIX? Ans. 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 stor
age (server): 50 MB

4. Data storage (client): 5 MB. Software Requirements: Operating system: The ope
rating 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 V
5.1, with PTFs U476879, U477366, U477367 and U477368, and APAR fix IY29345 runni
ng 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 runni
ng on 64 bit hardware. Connectivity The network protocols supported by WebSphere
MQ for AIX, V5.3 are: 1. TCP/IP 2. SNA LU 6.2. Databases: DB2 7.1, 7.2 Oracle 8
i and 9i Sybase v12 or v 12.5 Java: If you want to use the Java Messaging Suppor
t, you need the Java Runtime Environment Version 1.3 or later What are the softw
are and hardware requirements for installing MQ on Windows? Ans: MQ v 5.3 suppor
ts Windows 2000, Windows 2000XP,Windows 2000NT, Windows 2003 SE, Windows 2003EE.
Disk Storage: Typical storage requirements are as follows: 1 Server installatio
n: 50 MB 2. Client installation: 15 MB 3 Data storage (server): 50 MB 4. Data st
orage (client): 5 MB. Connectivity The network protocols supported by WebSphere
MQ for AIX, V5.3 are: 1. TCP/IP 2. SNA LU 6.2. 3. LU 6.2 4. NetBIOS Databases: D
B2 7.1, 7.2

Oracle 8i and 9i Sybase v12 or v 12.5 Java: If you want to use the Java Messagin
g Support, you need the Java Runtime Environment Version 1.3 or later what is a
Message and what does it contain? Ans: A message is a string of bytes that is me
aningful to the applications that use it. Messages are used to transfer informat
ion from one application program to another (or between different parts of the s
ame application). The applications can be running on the same platform, or on di
fferent platforms. WebSphere MQ messages have two parts: 1. The application data
. The content and structure of the application data is defined by the applicatio
n programs that use it. 2. A message descriptor. The message descriptor identifi
es the message and contains additional control information, such as the type of
message and the priority assigned to the message by the sending application. Web
Sphere MQ defines the format of the message descriptor. For a complete descripti
on of the message descriptor, What is the Max Length of the message does MQ supp
ort/ Ans: 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). What is
the difference between Persistent and Non Persistent Messages? Ans: In Web Spher
e MQ, messages can be either persistent or non persistent. Persistent messages a
re logged and can be recovered in the event of a WebSphere MQ failure. Thus, per
sistent messages are guaranteed to be delivered once and only once. Nonpersisten
t messages are not logged. Web Sphere still guarantees to deliver them not more
than once, but it does not promise to deliver them once. What is the effect of u
sing Persistant messages? Ans: Persistent messages are usually logged. Logging m
essages 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: Mess
ages are made up of Two parts: Message descriptor, Application data Types of mes
sages? Datagram: A Message sent with no response expected. Request: A Message se
nt for which a response is expected. Reply: A Response Message for a requested m
essage. Report: A Message that describes the occurrence or event

Ex COA/COD Sizes ? Qmanager10000 Msgs Maxmsglength4 Mb Queue5000 Msgs Maxmsglength4

Mb What is the attribute used to see the Message length? Ans: MaxMsgLength What
is MQ Client? Ans: A Web Sphere MQ client is a component that allows an applicat
ion 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 ba
ck to the application. What is MQ Server? Ans: A Web Sphere MQ server is a queue
manager that provides queuing services to one or more clients. All the Web Sphe
re 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 What are the Objects used in Web
sphere MQ? Ans: 1. Queue Manager 2. Queues 3. Channels 4. Processes 5. Name list
s. Mention the No of Characters required for creating names of the MQ objects? A
ns: For MQ Channels it is 20 Characters For Remaining objects it is 48 character
s. What about is the Default port number for MQ Queue Manager? Ans: 1414 Differe
nce 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 a
re 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, Chan
nel Initiator, Trigger monitor etc Is the MQSC attributes are Case sensitive? Ans
: MQSC commands, including their attributes, can be written in uppercase or lowe
rcase. Object names in MQSC commands are folded to uppercase (that is, QUEUE and
queue are not differentiated), unless the names are enclosed within single quot
ation marks. If quotation marks are not used, the object

is processed with a name in uppercase. SCRIPT COMMANDS:After entering in to queu

e manager we can find script commands. Script commands are same for every queue
manager. (These Commands should be used in CAPITAL LETTERS) DEFINE :-To define/c
reate MQ manager objects like queue, Channels, process, and listener. ALTER :-to
update or modify the existing objects DISPLAY :-to view all the properties of a
particular object or to Display all objects DELETE :-to delete created objects
CLEAR :-to clear the message from the queue END :-to come out of the queue manag
er PING :-to check whether other side channel / queue manager is ready to accept
our request. START :- to start the particular channel or listener STOP :-to sto
p particular channel or listener REFRESH :-used to refresh the security every ti
me after giving or executing, set mgr or command for queue manager or object RES
ET :-used to reset channel,cluster,queue manager RESOLVE :-to resolve the channe
l which is in indoubt state SUSPEND :-to suspend a queue manager from a cluster
environment RESUME :-to remove a queue manager from a cluster environment How ca
n we write the MQSC commands that have too many parameters/ Ans: For commands th
at have too many parameters to fit on one line, use continuation characters to i
ndicate that a command is continued on the following line: 1. A minus sign ( ) i
ndicates that the command is to be continued from the start of _ the following l
ine. 2. A plus sign (+) indicates that the command is to be continued from the f
irst nonblank character on the following line. What is programmable command form
at (PCF) commands? These commands are issued from a programme for local or remot
e administration done by programmers.

What are commands used for creating the Queue manager from the Command prompt? A
ns: crtmqm -q -d MY.DEFAULT.XMIT.QUEUE -u DEAD.LETTER.QUEUE QM1 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.
How can U make the existing Queue Manager as an default Queue Manager? Ans: On W
indows 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 nee
d to stop and restart the queue manager for the change to take effect. Where are
the backup files are present after creating the Queue Manager? Ans: Windows sys
tems: If you use Web Sphere MQ for Windows NT and Windows 2000, configuration in
formation is stored in the Windows Registry. UNIX Systems: 1. When you install t
he product, the Web Sphere MQ configuration file (mqs.ini) is created. It contai
ns a list of queue managers that is updated each time you create or delete a que
ue manager. There is one mqs.ini file per node. 2. When you create a new queue m
anager, a new queue manager configuration file (qm.ini) is automatically created
. This contains configuration parameters for the queue manager. What is the comm
and used for starting the Queue Manager? Ans: strmqm QMName What is the command
used for stopping the Queue manager? Ans: endmqm -w QMName The command waits unt
il 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 que
ue manager. Whats the message code for Stopping a Queue Manager? AMQ4044 Queue ma
nager stopping What is the command used to delete the QueueManager? Ans: dltmqm
QMName Display the attributes of the Queue Manager QM1? Ans: runmqsc QM1 Display
qmgr

BM Websphere MQ interview Questions Part 2

What is Queue? Ans: A queue is a data structure used to store messages. A queue
manager owns each queue. The queue manager is responsible for maintaining the qu
eues it owns, and for storing all the messages it receives onto the appropriate
queues What is the Default max Queue depth? Ans 5000 Types of Queues? Local Queu
e Remote Queues Alias Queues Model Queue Dynamic Queues Cluster Queues. Queue: A
safe place to store messages for Prior-To-Delivery, it belongs to the Qmgr to w
hich the application is connected. Model Queue: Model queue is a template of a q
ueue definition that uses when creating a dynamic queue. Alias Queue: Queue defi
nition, which is Alias to an actual Local or Remote Q. Used for security and eas
y maintenance. Remote Queue: Object that defines a Queue belongs to another Q Ma
nager (Logical Def). Initiation Queue: An initiation queue is a local queue to w
hich the queue manager writes a trigger message when certain conditions are met
on another local queue Dynamic Queue: Such a queue is defined on the fly when the
application needs it. Dynamic queues may be retained by the queue manager or aut
omatically deleted when the application program ends. Use- To store intermediate
results. Cluster Queue: Custer queue is a local queue that is known throughout
a cluster of queue managers. Reply-To-Queue: A request message must contain the
name of the queue into which the responding program must put the Reply Message.
Queue Manager: Provides Messaging services and manages the Queues, Channels, and
Processes that belongs to it. Alias Q Manager: Queue-manager aliases, are creat
ed using a remote-queue definition with a blank RNAME. What are the attributes r
equired for the Remote Queue Definition? Ans: 1.Name of the Queue 2. Transmissio
n Queue Name. 3. Remote QueueManager name 4. Remote Local Queue Name How can U d
efine Queues in MQ? Ans: Queues are defined to Web Sphere MQ using: 1. The MQSC
command DEFINE

2. The PCF Create Queue command What is Transmission Queue? Ans: Transmission qu
eues are queues that temporarily store messages that are destined for a remote q
ueue manager. You must define at least one transmission queue for each remote qu
eue manager to which the local queue manager is to send messages directly. What
is Initiation Queues? Ans: Initiation queues are queues that are used in trigger
ing. A queue manager puts a trigger message on an initiation queue when a trigge
r event occurs. A trigger event is a logical combination of conditions that is d
etected by a queue manager. What is Dead Letter Queue? Ans: A dead-letter (undel
ivered-message) queue is a queue that stores messages that cannot be routed to t
heir correct destinations. This occurs when, for example, the destination queue
is full. The supplied dead-letter queue is called SYSTEM.DEAD.LETTER.QUEUE. For
distributed queuing, define a deadletter queue on each queue manager involved. W
hat is the Max size that Queues support in MQ v5.3? Ans.They support around 2GB
of Size How can u create a Transmission Queue from a local Queue? Ans. Change th
e usage attribute from normal to Transmission Define a Local Queue LQ using the
MQSC Commands in the QM QM1 Ans: runmqsc QM1 Define qlocal (LQ) What are the Dif
ference B/W Predefined & Dynamic Queues? Ans: Queues can be characterized by the
way they are created: 1. Predefined queues are created by an administrator usin
g the appropriate MQSC or PCF commands. Predefined queues are permanent; they ex
ist independently of the applications that use them and survive Web Sphere MQ re
starts. 2 Dynamic queues are created when an application issues an MQOPEN reques
t specifying the name of a model queue. The queue created is based on a template
queue definition, which is called a model queue. What is the Algorithm followed
in retrieving the Messages from the Queue? Ans: 1.First-in-first-out (FIFO). 2.
Message priority, as defined in the message descriptor. Messages that have the s
ame priority are retrieved on a FIFO basis. 3. A program request for a specific
message.

What is Process Definition and what are the attributes does it contain? Ans: A p
rocess definition object defines an application that starts in response to a tri
gger event on a WebSphere MQ queue manager. The process definition attributes in
clude the application ID, the application type, and data specific to the applica
tion. What is intercommunication and its components to send message ? What is In
tercommunication? Ans: In Web Sphere MQ, intercommunication means sending messag
es from one Queue manager to another. The receiving queue manager could be on th
e same machine or another; nearby or on the other side of the world. It could be
running on the same platform as the local queue manager, or could be on any of
the platforms supported by Web Sphere MQ. This is called a distributed environme
nt. Message channels Message channel agents Transmission queues Channel initiato
rs and listeners Channel-exit programs What is Distributed Queue Management (DQM
). Web Sphere MQ handles communication in a distributed environment such as this
using DQM.The local queue manager is sometimes called the source queue manager
and the remote queue manager is sometimes called the target queue manager or the
partner queue manager. What is the Objects required for the DQM? Ans: On source
QueueManager: 1. Transmission Queue 2. Remote queue definition. 3. Dead Letter
Queue(recommended) 4. Sender Channel On Target Queue Manager 1. Local Queue 2. D
ead Letter Queue 3. Receiver Channel 4.Listenr ***.The sender and receiver chann
els names should be same. What is channel and mention different types of channel
s in MQ? Ans: Channels are objects that provide a communication path from one qu
eue manager to another. Channels are used in distributed queuing to move message
s from one queue manager to another. They shield applications from the underlyin
g communications protocols. The queue managers might exist on the same, or diffe
rent, platforms. Different types of Channels: 1. Sender-Receiver Channels 2. Req
uester-Server Channels 3. Client Connection channels 4. Server Connection Channe
ls. 5. Cluster Sender.

6. Cluster Receiver Channels What are MQI channels and there types? MQI channels
are the channels that carry messages from MQ Client application to the MQ serve
r and vice versa.They are Bi-directional Channels 1. Server-connection 2. Client
-connection How many Channel Combinations? 1.Sender-receiver Channel 4.Requester
-server Channel 2.Requester-sender Channel 5. Server-receiver Channel 3.ClusterSender- Receiver Channel 6.Client-Server Channel What are the attributes require
d for the Sender Channel? Ans: 1. The Name of the Channel 4.Transport Type 2. Th
e Connection name 5.Scyexit What are different Channel status? Ans: Channel Stat
us: 1. Inactive 3.Retrying 2. Running 4.Stopped What about Initializing & Bindin
g states? Ans: Before running state first the channel will initializes the liste
ner & Binds with the Receiver Channel then it goes into running mode. Tell me So
me Channel Attributes? Batch Heartbeat Interval (BATCHHB): This heartbeat interv
al allows a sending channel to verify that the receiving channel is still active
just before committing a batch of messages. If the receiving channel is not act
ive, the batch can be backed out rather than becoming in-doubt, Batch interval (
BATCHINT), Batch size (BATCHSZ), Channel type (CHLTYPE), Cluster (CLUSTER), Clus
ter namelist (CLUSNL), Connection name (CONNAME), Convert message (CONVERT), Dis
connect interval (DISCINT), Heartbeat interval (HBINT), KeepAlive Interval (KAIN
T), Long retry count (LONGRTY), Long retry interval (LONGTMR), Maximum message l
ength (MAXMSGL) Why is Channel RETRYINT attribute used? If a message is places i
n DLQ because of put inhibited or queue full condition, the DLQ handler attempts
to put the message back to the destination queue. This interval is called as RE
TRYINT by default the retry interval is 60 seconds. Receiver Cluster Receiver Re
quester What is channel disconnect interval? This is a time-out attribute, speci
fied in seconds, for the server, cluster-sender, and cluster-receiver channels.
The interval is measured from the point at which a batch ends, that is when the
batch size is reached or when the batch interval expires and the transmission qu
eue becomes empty. If no messages

arrive on the transmission queue during the specified time interval, the channel
closes down Explain the channel attribute BATCHSIZE? BATCHSIZE denotes the maxi
mum number of messages that can be sent through a channel before taking a checkp
oint. This parameter is valid only for channels with a channel type (CHLTYPE) of
SDR, SVR, RCVR, RQSTR, CLUSSDR, or CLUSRCVR. The value must be in the range 1 t
hrough 9999. What is BATCH HEARTBEAT INTERVAL? Ans: The batch heartbeat interval
allows a sending channel to verify that the receiving channel is still active j
ust before committing a batch of messages, so that if the receiving channel is n
ot active, the batch can be backed out rather than becoming in-doubt, as would o
therwise be the case. By backing out the batch, the messages remain available fo
r processing so they could, for example, be redirected to another channel. What
is Keep Alive Interval? Ans: The Keep Alive Interval parameter is used to specif
y a time-out value for a channel. The Keep Alive Interval parameter is a value p
assed to the communications stack specifying the Keep Alive timing for the chann
el. It allows you to specify a different keep alive value for each channel. The
value indicates a time, in seconds, and must be in the range 0 to 99999. What is
LONG Retry count? Ans: Specify the maximum number of times that the channel is
to try allocating a session to its partner. If the initial allocation attempt fa
ils, the short retry count number is decremented and the channel retries the rem
aining number of times. What are the ways to start a channel? Use the MQSC comma
nd START CHANNEL Use the control command runmqchl to start the channel as a proc
ess Use the channel initiator to trigger the channel Type of channel states: Ina
ctive and Current- Stopped, Starting, Retrying and Active What are the three opt
ions for stopping channels? QUIESCE FORCE TERMINATE What are the components of m
essage channel? A queue manager to communicate with another queue manager uses m
essage channel. The components of a message channel are 1. Sender Message channe
l agent: Sender MCA is a program that transfers messages from a transmission que
ue to a communication link 2. Receiver MCA: It transfers messages from the commu
nication link into the target queue 3. Communication protocol: Responsible for t
ransferring messages A message channel is unidirectional. What is Message Channe
l agent (MCA)?

Ans: A message channel agent (MCA) is a program that controls the sending and re
ceiving of messages. There is one message channel agent at each end of a channel
. One MCA takes messages from the transmission queue and puts them on the commun
ication link. The other MCA receives messages and delivers them onto a queue on
the remote queue manager. A message channel agent is called a caller MCA if it i
nitiated the communication; otherwise it is called a responder MCA. What is Chan
nel initiator and Listeners? Ans: A channel initiator acts as a trigger monitor
for sender channels, because a transmission queue may be defined as a triggered
queue. When a message arrives on a transmission queue that satisfies the trigger
ing criteria for that queue, a message is sent to the initiation queue, triggeri
ng the channel initiator to start the appropriate sender channel. You can also s
tart server channels in this way if you specified the connection name of the par
tner in the channel definition. This means that channels can be started automati
cally, based upon messages arriving on the appropriate transmission queue. You n
eed a listener program to start receiving (responder) MCAs. Responder MCAs are s
tarted in response to a startup request from the caller MCA; the channel listene
r detects incoming network requests and starts the associated channel. Channel E
rrors? Due to: 1. Xmitq is set to get disabled 2. Network Issues 3.QueueManager
Stopped 4. Listener is not running 5.TriggerTurned Off Explain Channel-Exit prog
rams and what are the types? Channel-exit programs are called at defined places
in the processing carried out by MCA programs Security Exit: You can use securit
y exit programs to verify that the partner at the other end of a channel is genu
ine Message Exit: Message Exit can be used for Encryption on the link, message d
ata conversion, validation of user ID, Message-retry Exit: Message-retry exit is
called when an attempt to open the target queue is unsuccessful Sender and rece
iver Exit: You can use the send and receive exits to perform tasks such as data
compression and decompression Channel auto-definition Exit Transport-retry Exit
What is the Different Logging Methods available? Ans: There are two different ty
pes available 1. Circular: The circular logging is used for restart recovery. It
is the default logging method. Circular is used in Development and Testing Queu
es. Circular logging keeps all restart Data in a ring of log files. Logging fill
s the first file in the ring, then moves on to the and so on, until all the file
s are full. It then goes back to the first file in the ring and starts This cont
inues as long as the product is in use, and has the advantage that you never run
out of log files.

2. Linear: Linear logging gives you both restart recovery and media recovery. It
is used in Production. Linear logging keeps the log data in a continuous Sequen
ce of files. Space is not reused, so you can always retrieve any record logged f
rom the time that the queue manager was created. As disk space is finite, you mi
ght have to think about some form of archiving. It is an administrative task to
manage your disk space for the log, reusing Or extending the existing space as n
ecessary. What is the Default location where the logs are stored and mention the
default sizes? Ans: Default location: Windows: C:\Program Files\IBM\WebSphere M
Q\log\qmgr UNIX: /var/mqm/log What is the log file size? Ans: In Web Sphere MQ f
or Windows NT and Win 2000, the minimum value is 32, and the maximum is 16 384.
The default value is 256, giving a default log size of 1 MB. In Web Sphere MQ fo
r UNIX systems, the minimum value is 64, and the maximum is 16 384. The default
value is 1024, giving a default log size of 4 MB. How will you change the log fi
le size? Ans ; You cannot change the log file size. For this you need to drop an
d re-create the queue manager. The number of log files primary & secondary can b
e changed but you need to restart the Q manager for the changes to take effect.
what is the number for log primary and secondary file allocated? Ans: Primary lo
g files: The number of primary log files to be allocated is 3 by default the min
imum is 2 and MAX in Win 253 / Unix 510 Secondary log files: The number of secon
dary log files to be allocated is 2 by default the minimum is 1 and MAX in Win 2
52 / Unix 509 What is the command used for creating the listener? Ans: crtmqlsr
-t tcp -m QMNAME -p portno What is the commands used for running listener in 5.3
Version? Ans: runmqlsr -t tcp -m QMNAME -p portno What is command used to perfo
rm task on the MQ services? Ans: amqmdain What are commands used on the Command
server? Ans: 1.strmqcsv: to start the command server 2. dspmqcsv: to display the
command server 3. endmqcsv: To end the command server.

Is there is any chance for the Message lost? Ans: If the target queuemanager doe
sn.t contain the dead letter queue defined and if the messages are running on a
fast channel and of non persistant,Then there is a chance of the message loss. W
hat is the command that is used to provide authorization for the clients? Ans: s
etmqaut -m QMName -t queue -n Queuename -p GUEST +all What are the common errors
u get in DQM? Explain how to resolve ? Ans: mqrc 2058: MQRC_Q_MGR_NAME_ERROR Mq
rc 2059: MQRC_Q_MGR_NOT_AVAILABLE. Mqrc 2033: MQRC_NO_MSG_AVAILABLE. Mqrc 2085:
MQRC_UNKNOWN_OBJECT_NAME. Mqrc 2009: MQRC_CONNECTION_BROKEN. Mqrc 2043: MQRC_OBJ
ECT_TYPE_ERROR. Mqrc 2086: MQRC_UNKNOWN_OBJECT_Q_MGR. Mqrc 2035: MQRC_NOT_AUTHOR
IZED. What are different modes in which a application can connect to a Queuemana
ger? Ans: 1.Binding mode: In binding mode, also known as server connection, the
communication to the queue manager utilizes inter-process communications. One of
the key factors that should be kept in mind is that binding mode is available o
nly to programs running on the MQSeries server that hosts the queue manager. A p
rogram using binding mode will not run from an MQSeries client machine. Binding
mode is a fast and efficient way to interact with MQSeries. Certain Facilities,
such as XA transaction co-ordination by queue manager, are available only in bin
ding mode. 2. Client Connection: Client connection uses a TCP/IP connection to t
he MQSeries Server and enables communications with the queue manager. Programs u
sing client connections can run on an MQSeries client machine as well as on an M
QSeries server machine. Client connections use client channels on the queue mana
ger to communicate with the queue manager. The client connection does not suppor
t XA transaction coordination by the queue manager. What are the different types
of messaging systems used by JMS? Ans: JMS applications use either the point-to
-point (PTP) or publish/subscribe style of messaging. Point-to-Point: Point-to-p
oint messaging involves working with queues of messages. The sender sends messag
es to a specific queue to be consumed normally by a single receiver. In point-to
-point communication, a message has at most one recipient. A sending client addr
esses the message to the queue that holds the messages for the intended (receivi
ng) client. Publish/Subscribe: In contrast to the point-to-point model of commun
ication, the publish/subscribe model enables the delivery of a message to multip
le recipients. A sending client addresses, or publishes, the message to a topic
to which multiple clients can be subscribed. There can be multiple publishers, a
s well as subscribers, to a topic.

Is It Possible to use one transmission Queue for the multiple message channels?
Ans: It is possible to define more than one channel per transmission queue, but
only one of these channels can be active at any one time. This is recommended fo
r the provision of alternative routes between queue managers for traffic balanci
ng and link failure corrective action. A transmission queue cannot be used by an
other channel if the previous channel to use it terminated leaving a batch of me
ssages in-doubt at the sending end. What is the command used to test whether the
channel is active or not? Ans: runmqsc QMName Ping channel (channel name). What
are the administrative commands that are used in Publish and Subscribe? Ans: Th
e strmqbrk command is used to start a broker. The first time this command is run
on a queue manager, all the relevant MQSeries objects are automatically created
. strmqbrk -m MYQMGRNAME The dspmqbrk command is used to check the status of the br
oker. Possible states are: starting, running, stopping, quiescing, not active an
d ended abnormally. dspmqbrk -m MYQMGRNAME The endmqbrk command is used to stop a b
roker. There are two options: -c requests a controlled shutdown (default), -i re
quests an immediate shutdown. -endmqbrk -i -m MYQMGRNAME What is multiple hoping?
Ans: If there is no direct communication link between the source queue manager a
nd the target queue manager, it is possible to pass through one or more intermed
iate queue managers on the way to the target queue manager. This is known as a m
ulti-hop. What is Local administration and Remote administration? Local Administ
ration: Means carrying out administration tasks on any queue managers you have d
efined on your local system. Remote Administration: This allows you to issue com
mands from your local system that are processed on another system. For example,
you can issue a remote command to change a queue definition on a remote queue ma
nager. You do not have to log on to that system, although you do need to have th
e appropriate channels defined. The queue manager and command server on the targ
et system must be running Difference between Control Commands used in Windows an
d other Os? Control commands on are case sensitive other OS but Windows they can
be used any way. What is MQOO_BIND_ON_OPEN option on the MQOPEN call ? When thi
s attribute is set it forces all the messages sent to this queue to be sent to t
he same instance of the queue (go to the same queue in cluster) Difference betwe
en MQPUT and MQPUT1 call ? The MQPUT1 call always operates as though MQOO_BIND_N
OT_FIXED were in effect, that is, it always

invokes the workload management routine. When is Channel security exit program c
alled? Are called at MCA initiation and termination Stopping unauthorized queue
managers putting messages on your queues Use OS security, Object Authority Manag
er (OAM) on WebSphere MQ user-written procedures What happens if DEAD letter Que
ue is not defined? If dead letter queue are not defined the Messages are placed
on the Transmission Queue and the Queue Manager become Inactive Explain Remote q
ueue definitions? Advantages? These are definitions for queues that are owned by
another queue manager Advantages: The advantage of remote queue definitions is
that they enable an application to put a message to a remote queue without havin
g to specify the name of the remote queue or the remote queue manager, or the na
me of the transmission queue. This gives you location independence. What happens
if channel terminates when fast non-persistent messages are in transit? If a ch
annel terminates while fast, non-persistent messages are in transit, the message
s are lost and it is up to the application to arrange for their recovery if requ
ired. If the receiving channel cannot put the message to its destination queue t
hen it is placed on the dead letter queue, if one has been defined. If not, the
message is discarded. What happens when a message cannot be delivered? Message-r
etry: If the MCA is unable to put a message to the target queue for a reason tha
t could be transitory (for example, because the queue is full), the MCA has the
option to wait and retry the operation later Return-to-sender: If message-retry
was unsuccessful, or a different type of error was encountered, the MCA can send
the message back to the originator Dead-letter queue: If a message cannot be de
livered or returned, it is put on to the dead-letter queue (DLQ). You can use th
e DLQ handler to process the message Recovery scenario Disk Drive Full, damaged Q
ueue manager object, Damaged single object, Automatic media recovery failure MQ
ensures that messages are not lost by maintaining records (logs) of the activiti
es of the queue managers that handle the receipt, transmission, and delivery of
messages How to Process Messages from the Dead-letter-Queue? We can Process the
DLQ messages using runmqdlq command for sending messages to the destination Queu
es or target Queues. Use the runmqdlq command to start the dead-letter queue (DL
Q) handler, which monitors and handles messages on a dead-letter queue. runmqdlq
QName QMgrName Use the Dead-Letter-Queue-Handler to perform various actions on
selected messages by specifying a set of rules that can both select a message an
d define the action to be performed on that message. The runmqdlq command takes
its input from stdin. When the command is processed, the results and a summary a
re put into a report that is sent to stdout.

Which field of the MQDLH structure contains a reason code that identifies why th
e message is on the DLQ? Reason field What is completion code(MQCC) and reason c
ode(MQRC)? Completion code gives the status of the current transaction it can be
0, 1, 2. 0- for Successful completion (MQCC_OK), 1- Warning (MQCC_WARNING), 2call failed (MQCC_FAILED). Reason code is that which gives the reason for which
the transaction fails it can be MQRC_NONE, MQRC_BACKED_OUT etc. What is Correl I
D? This is a byte string that the application can use to relate one message to a
nother, or to relate the message to other unit of work that the application is p
erforming. The correlation identifier is a permanent property of the message, an
d persists across restarts of the queue manager Explain commit and Back Out unit
s of work? When a program puts a message on a queue within a unit of work, that
message is made visible to other programs only when the program commits the unit
of work. Commit: To commit a unit of work, all updates must be successful to pr
eserve data integrity. If the program detects an error and decides that the put
operation should not be made permanent, it can back out the unit of work. Back O
ut: When a program performs a back out, WebSphere MQ restores the queue by remov
ing the messages that were put on the queue by that unit of work. The way in whi
ch the program performs the commit and back out operations depends on the enviro
nment in which the program is running BackoutCount (MQLONG)? This is a count of
the number of times that the message has been previously returned by the MQGET c
all as part of a unit of work, and subsequently backed out. BackoutCount is the
number of times the application tried and failed to put the messages in the Queu
e What is segmentation and explain segmentation Flag? When a message is too big
for a queue, an attempt to put the message on the queue usually fails. Segmentat
ion is a technique whereby the queue manager or application splits the message i
nto smaller pieces called segments, and places each segment on the queue as a se
parate physical message. The application that retrieves the message can either r
etrieve the segments one by one, or request the queue manager to reassemble the
segments into a single message that is returned by the MQGET call. What are Name
list? when do you use it? A namelist is a WebSphere MQ object that contains a li
st of other WebSphere MQ objects. Typically, namelists are used By trigger monito
rs, where they are used to identify a group of queues. Namelists are also used wi
th queue manager clusters to maintain a list of clusters referred to by more tha
n one WebSphere MQ object. The advantage of using a namelist is that it is mainta
ined independently of applications; it can be updated without stopping any of th
e applications that use it. Also, if one application fails, the namelist is not
affected and other applications can continue using it. Namelists are also used w
ith queue manager clusters to maintain a list of clusters referred to by more th
an one WebSphere MQ object What are name services?

The name service is an installable service that provides support to the queue ma
nager for looking up the name of the queue manager that owns a specified queue.
What is Local units of work (uses a single-phase commit process) and Global unit
of Work (uses a twophase commit process)? Local unit of work: Units of work tha
t involve only the queue manager are called local units of work. Syncpoint coord
ination is provided by the queue manager itself (internal coordination) using a
singlephase commit process. Use global units of work when you also need to inclu
de updates to resources belonging to other resource managers. Here the coordinat
ion can be internal or external to the queue manager uses a two-phase commit How
will we start a command server? Depending on the value of the queue manager att
ribute, SCMDSERV, the command server is either started automatically when the qu
eue manager starts, or must be started manually. Start: Using strmqcsv saturn.qu
eue.manager where saturn.queue.manager is the QM name Display: dspmqcsv Stop: en
dmqcsv When we use CCSID attribute of the ALTER QMGR command to change the CCSID
of the QM what are the components that need to be restarted? Stop and restart t
he queue manager, stop and restart command server (A command server processes co
mmand messages) and channel programs What is a MQ Series Queue manager Configura
tion file (qm.ini)? A queue manager configuration file (qm.ini) to effect change
s for specific queue managers. There is one qm.ini file for each queue manager o
n the node. (A queue manager configuration file, qm.ini, contains config informa
tion relevant to a specific queue manager. There is one queue manager configurat
ion file for each queue manager. The qm.ini file is automatically created when t
he queue manager with which it is associated is created. For example, the path a
nd the name for a configuration file for a queue manager called QMNAME is:/var/m
qm/qmgrs/QMNAME/qm.ini) What is name transformation in naming a Queue manager Co
nfiguration File? A qm.ini file is held in the root of the directory tree occupi
ed by the queue manager. For example, the path and the name for a configuration
file for a queue manager called QMNAME is: /var/mqm/qmgrs/QMNAME/qm.ini A direct
ory name is generated based on the queue manager name. This process is known as
name transformation. What is a Websphere MQ configuration file (mqs.ini)? Contai
ns information relevant to all the queue managers on the node. It is created aut
omatically during installation (The WebSphere MQ configuration file, mqs.ini, co
ntains information relevant to all the queue managers on the node. It is created
automatically during installation. The mqs.ini file for WebSphere MQ for UNIX s
ystems is in the /var/mqm directory. It contains: v The names of the queue manag
ers v The name of the default queue manager The location of the files associated
with each of them) How can we edit the configuration files? Automatically using
commands that change the configuration of queue managers on the node, Manually
using a standard text editor When security checks are made? Connecting to the qu
eue manager (MQCONN or MQCONNX calls), Opening the object (MQOPEN or

MQPUT1 calls), Putting and getting messages (MQPUT or MQGET calls), Closing the
object (MQCLOSE)