MQ Interview Questions

Scenario 1

1. Tell me about self (or) take me through your resume?

2. What are the different types of Logs?

We have two types of logs.
1. Transactional logs:
2. Error logs.
3. Difference between Errors and Qmgr errors?
Errors: This will contain all S/W level errors and Information
QMGR: This will contains all the information of QMGR objects and errors
4. How you enable Trace?
* Or start a high detail trace for one queue manager:
strmqtrc -t all -t detail -m MY.QMGR
* Or start a high detail wrapping trace and limit the file size to 5MB :
strmqtrc -l 5 -t all -t detail -m MY.QMGR

# End all tracing:

endmqtrc -a
# Format the trace files:
dspmqtrc *.TRC
Or format wrapping trace files:
dspmqtrc *.TRC *.TRS
5. What does the FDC contain?
FDC File:Failure data capture, If any S/W related error occurs this file will be created, in
FDC we have PROB_ID based on that we will find the solution in IBM Tech notes.
Probid
Userid
Application name
Major error code
Minor error code
Problem severity
Probtype
Process
5. Channel in doubt and in flight state?
The INDOUBT count specifies the number that was interrupted between phase-1 and
phase-2 of the commit process. These must undergo forward recovery to ensure that
resources modified by them are unavailable until their INDOUBT status is resolved.
 The INFLIGHT count specifies the number that neither completed phase-1 of the
commit process nor began the process of backing out. These must undergo backward
recovery to restore resources modified by them to their previous consistent state
7. Sequence number wrap?
This is the highest number the message sequence number reaches before it restarts at 1.
The value of the number should be high enough to avoid a number being reissued while
it is still being used by an earlier message. The two ends of a channel must have the
same sequence number wrap value when a channel starts up; otherwise, an error occurs.
The value may be set from 100 through 999 999 999
7. Difference between Full & Partial Repository?
Full repository: This will contains all the information of Cluster QMgrs and other
objects.
Partial repository: This will Contains the information of that particular Qmgr and Other
instances for communication.
9. Where do we find the cluster information?
We have one Queue i.e SYSTEM.CLUSTER.REPOSITORY.QUEUE, in that all the
cluster info will stored

10. What does contain in Auto define channel?

It contains channel name, port No. and Ip address That are mentioned in the Receiver
channel
11. What is the backup Queue of the QMGR?
Dead letter queue
12. How you set Authentication?
Using SETMQAUT, this is used assign permissions to the user
SETMQAUT -M QMname -n objname -t objtype -p principle/-g group +all
dmpmqaut -m qmname -n objectname -t objecttype -p user to display set of all users
given permission on the object
dspmqaut ------ to display set of all the permission for the user on the object
13. Will you give permission only for USER or GROUP, if GROUP why?
We can assign permissions to user and if you want assign permissions to group also.if
asign permissions to group that are assign the entire user who are under that group.
14. Difference between Receiver & Requester channel?
Requester and Receiver are same except that the requesters can start the sender from
requester side.
14. Why do we go clustering?
We have so many advantages using cluster
1. Administration task will be reduced
2. Work load balancing
3. Increase resource utilization
4. High availability
16. Components of the cluster?
Clussdr and clusrcvr channels
SYSTEM.CLUSTER.REPOSITORY.QUEUE
SYSTEM.CLUSTER.COMMAND.QUEUE
SYSTEM.CLUSTER.TANSMISSION.QUEUE (NOTE: Don’t disable the put or get
attribute on cluster)
17. Which types of Logs are using in your Organization?
Depending upon client requirement we are using both linear and circular loggings
18. How you check the Status of the Queue?
dis qs(qname) type(handle)
19. Default path of the Error logs & Transaction Logs?
In Windows: \Program files\IBM/Web spear MQ\Log\ Qmgrs\active
C:\Program file\IBM\Web spear MQ\Qmgrs\QMname\Errors
In UNIX: /var/mqm/log/Qmgrs/active
/var/mqm/Qmgrs/Qmname/errors
19. What is the use of PROBID in Fdc?
Using ProbID: we can find the solution in IBM info center, If before anybody face that
problem, otherwise we will rise PMR(problem management report) and it will contains
Application name, major error, minor error and so on..
21. Difference stopping status of QMGRs?
End immediately, End abnormally, ended normally
22. How do you enable the Trigger?
We need to set some properties on queues
Trigger on, Trigtype (First/every/depth), Trigdepth, Trigdata(chalname), initq()
23. Which types of tickets do you mostly resolved?
Instant tickets
24. How to Suspend a Qmgr from the cluster?
Suspend qmgr cluster (clusname)
25. How to add existing Qmgr into the cluster?
If you add it as full repository, you need to add repos keyword to Qm, and create one
clussdr and clusrcvr channels, add cluster attributes to other objects
If you want to add it as partial repository, create clusrcvr channel to that QM and a
clussdr to a queue manager in full repository and set cluster attribute to objects

26. What is the use of alias queue?

This queue is act as reference queue to local, remote and cluster queue’s.
the advantage of alias queue is
1. Hide the details of reference queue to clients.
2. used for follow the naming conventions,
3. Provide different levels of access.
26A. Why do we give ‘Conname’ at Receiver Channel side in Cluster?
In cluster sdr channels are auto generated, based on the receiver channel attributes only
the sdr channel will generated
27. How can you install all the Packages in Linux at a time?
rpm -ivh name of the packages with spaces
28. Tell me the process of installation on Windows and Linux?
on linux
df -k df -h to check the disk space
rpm (redhat package manager)
Create mqm userid and make mqm as its primary group.
the installation directory for mqm are opt/mqm
the working data is stored in var/mqm
./mqlicense.sh -accept --- to accept the license
then run the commands to install all the packages required. rpm -ivh packagename
rpm -ivh ( i- install v- verbose h- hash format)
to check the packages installed rpm -qa ! grep mq
ps -ef ! grep mq to end all the processes.
29. Difference between V5, V6 & V7?
30. Differences between persistent and non persistent messages?
1. Persistent msg’s are important, at any cost those must be deliver to destination QM,if
any problem occur Those are placed in Xmitq or in DLQ.
2. Nonpersistent msg’s are not important; if any problem occurs those are discarded.

31. Types of tickets?

1. Instant tickets
2. Change order tickets
32. How many Qmgrs are in your current project?
Nearly 400.
33. How do you convert linear to circular?
We don’t have that type of operation if you want to change,
1. First stop the channels
2. Stop the Qmgr
3. Take the back up of qmanager using save queue manager
4. Delete the Qmgr
5. Recreate it with linear logging
6. Recreate all the queue definitions and give the permission to the queues
34. How many applications connect to your current project?
Display conn(*)
35. Reason codes for 2033, 2053, 2085, 2035, 2537…
2033: Msg not available
2053: Q full
2085: unknown obj name
2035: Not authorized
2537: channel not available
2016 (07E0) (RC2016): MQRC_GET_INHIBITED
2030 (07EE) (RC2030): MQRC_MSG_TOO_BIG_FOR_Q
2031 (07EF) (RC2031): MQRC_MSG_TOO_BIG_FOR_Q_MGR
2042 (07FA) (RC2042): MQRC_OBJECT_IN_USE
2051 (0803) (RC2051): MQRC_PUT_INHIBITED
2057 (0809) (RC2057): MQRC_Q_TYPE_ERROR
2058 (080A) (RC2058): MQRC_Q_MGR_NAME_ERROR
2059 (080B) (RC2059): MQRC_Q_MGR_NOT_AVAILABLE
36. What are the errors we can get at the time of installation?
1. user is not a member of mqm group.
2. Some mq series processes are running while installing.
 37. How do you connect MQ Client to MQ Server?
We have three types options for connecting client to server
1.MQCONNX
2.MQSERVER
3.Clientchannel tab
38. Qmgr attributes?
dEADQ,REPOS(),REPOSNL(),CLWLUSEQ(),MAXHANDS(),MAXPRTY()
39. What is listener and port?
Listener is a program running continuously listening for request msg from sdr
Port:unique entry point for a QManager
40. Where the configuration information stores on Linux and windows?
in windows it is stored at registry. in linux it is stored in mqs.ini file.
41. What is the difference between qm.ini and mqs.ini file?
A queue manager configuration file, qm.ini, contains information relevant to a specific
queue manager. There is one queue manager configuration file for each queue manager.
The qm.ini file is automatically created when the queue manager with which it is
associated is created.
The WebSphere® MQ configuration file, mqs.ini, contains information relevant to all
the queue managers on a WebSphere MQ installation. It is created automatically during
installation. In particular, the mqs.ini file is used to locate the data associated with each
queue manager
42. How do you configure the Qmgr before you install fix pack?

42. Difference between upgradation and migration?

---->An "upgrade" generally refers to an enhanced version of the software
---->if you migrate from a previous version of WebSphere MQ for Linux,
you must uninstall your current version before installing WebSphere MQ Version
44. Which tool you use to connect with Linux and mainframes?
putty to connect to linux.
telnet or ssh to connect to mainframes.
44. How many channels we can create in Distribution Queuing for a Qmgr?
One sender and receiver channel
46. If you create 100 channels for a Qmgr… How can you create 101 Channel?
Normal way like:Define chl(chlname) chltype(type) conname(Ip&port)
47. How many years of experience you have?
3.3 YEARS
48. Are you supporting for L2 or L3?
l2
49. Who is your Vendor?
wipro
50. Who is your Client?
Carrefour
51. Project name?
Infrastructure engineering services [IES].
52. Which ticketing tool you are using?
BMC REMEDY,RADIX, OPEN HP view
53. Which monitoring tool you are using?
OMEGAMON XE , Q pasa, BMC Main View
54. Your monitoring and ticketing tools belong to?
BMC
55. Your mail server and chat server?
lOTUSNODES, sametime & Microsoft outlook, office communicator
56. At which location your L3 team will be?
Client location
57. How can you recover the damaged object and its syntax?
Using media recovery we can recreate damaged objects
rcrmqobj -m Qmname -t objtype -n objname
58. Channel attributes?
chltype(),discint(),batchhb(),trptype(),maxmsgl(),xmitq() conname() rqmname()
59. Different status of channel?
Initializing, binding, retrying, running, inactive, stopped, paused.
60. Are you supporting for 24*7 or on-call?
I have supported on-call.
61. Why do we go for MQ Client?
. No need for a full WebSphere MQ implementation on the client machine.
. Hardware requirements on the client system are reduced.
. System administration requirements are reduced.
. Application running on a client can connect to multiple queue managers on different
systems.
. Alternative channels using different transmission protocols can be used
. Reduce the burden on other clients
62. In your company which Client-Server architecture is using?

63. Do you raise any PMR so far?

I have never raised PMR (problem management record)
64. Who send the tickets to you?
Users, application team, all the members who are involved in the current project
65. How do you escalate the ticket to L3?

66. Have you ever raised any tickets so far?

yes.
67. Have you ever raised change order?
no
68. Which flavor you are using on Linux?
Red hat
69. Differences between MQI and MSG Channels?
MQI channels are used between MQ client and MQ sever, those are bi-directional
Types: server connection channel
Client connection channel
MSG channels are Uni-directional, and used between QM
1. Sender
2. Receiver
3. Cluster sender
4. Cluster receiver
5. Server
6. Client
7. Requester
70. Default objects in Cluster?
SYSTEM.CLUSTER.REPOSITORY.QUEUE
SYSTEM.CLUSTER.COMMAND.QUEUE
SYSTEM.CLUSTER.TRANSMISSION.QUEUE & Queues and channels.
71. Difference between Dead-Letter Header and Handler?
If messages come to DLQ, QM will add dead letter header to msg, it contains reason for
failure, destination queue and QM details such type of info’n
Using dead letter handler you pick the msgs from DLQ placed it in destination queue
72. What is sync point?
This is nothing but unit of work in two phase commit
73. Tell me something about unit of work?
The period of updates between two sync points is called unit of work.
74. Can you change the log file size?
No.
75. Where the latest information stores in error logs and why?
In the first file.
76. Can you increase the no. of error logs?
no
77. What is the command to check the disk space on Linux?
df -k df -h
78. Which command we use to check the installed packages on Linux?
rpm -qa | grep mq
79. Command to kill the process on Linux?
$ ps ux ----------to list all the processes.
$ kill -9 Pid -------------to kill particular process...
80. Do you run the runmqdlq program every time?
Depending upon the messages those are coming to the DLQ.
81. How can you check the listener port is running from your desktop?
NETSTAT -a
82. What is the use of telnet, ping and tracert?
Ping is used to check the status of remote channel.
Telnet is used for remote access of another system.
It shows path taken to reach a particular destination over a network.

83. How can you connect to remote server from your desktop?
Using MSTSC
84. How many primary and secondary logs we can create on windows &
Linux (Max)?
Windows: primary file: 254, secondary: 253
Linux: primary files: 510, secondary: 509
85. Explain the concept of cluster workload balance?
86. What are the attributes of workload balance?
Defbind(notfixed)
Put()
clwluseq(local/any/QMGR)
clwlrank(0-9)
clwlprty(0-9)
clwlwght()
clwlmruse()
87. Explain client-server architecture?
88. What are the pre-requisites for MQ before install?
1. Hardware requirements----disk space
2. Software requirements----o/s specifications
89. Explain the process migration?
90. Have you ever done migration and how?
91. How can we take the Qmgr backup?
- create the backup queue manager
- copy the data and log files from your primary queue manager over the backup queue
manager's data and logs
- flag backup qmgr as a backup and replay log extents (strmqm -r)
- Periodically copy over the log files prior to the CURRLOG value from the queue
manager
saveqmgr -m MQ_BACKUP -r MQ_C1_01 -f MQ_C1_01.txt
92. Error log file name?
error log file name is:AMQERR01,AMQERR02,AMQERR03
93. What is the use of client channel tables?
Using client channel table we can connect with different QM’s and different clients will
connect to single QM
94. How many max channels can connect to a Qmgr?
The default for maximum channels is 100 for qmgr. it can be set to higher in the qm.ini.
95. How can you find the max channels are connected to a Qmgr?
dis qmstatus conns
96. Channel components?
chltype() conname() trptype() xmitq() batchsz() hbint()
97. What is the use of trig data in channel?
98. What does initiation queue contain?
This will contains trigger massage generated by QM
99. How can we check whether the Qmgr contain Dead-latter queue or not?
DIS QMGR DEADQ(*)
99. How many servers, Qmgrs in your environment?
100servers. 400qmgrs.
101. Which programs you use for running the trigger monitor when you use your own
initiation queue?(in application and channel triggering)
In application triggering we are using RUNMQTRM
in channel RUNMQCHI INITQ()
102. What is the default size of /var /mqm and /opt /mqm?
Allow 130 MB as a minimum for a WebSphere MQ server and 15 MB as a minimum for a
WebSphere MQ client.
x-86 201 mb iseries -183

103. What is the difference between Control & Runmqsc Commands?

RUNMQSC commands are used with in Qm for creating Qm objects and altering
QMGR.
CONTROL commands are used for creating starting and running QM, and for set
authentication.
104. In Cluster for Round-Robin process defbind (open) what is happen?
If you set Defbind open, all msg’s are placed where the first msg is place
105. Explain the distributed queuing setup?
106. What is meant by distribution queuing?
107. What is difference between distribution and clustering?
In distributions queuing we have to create more no of objects like remote queues,
Transmission queues and sender, receiver channels for every remote queue manager.
In clustering we can logically connect queue managers with the creation of less no. of
Qmgr objects.
108. Why we go for clustering?
1. Simplifying system administration
2. Work load management
3. Less no of QM objects like RQD, channels.
4. High availability
109. In cluster we have 4 Qmgrs and having same instance in all Qmgrs I have to send
messages to a particular Qmgr then how u configure?
Assign clwlrank and clwlprty for particular queue.
110. Tel me prerequisites for MQ admin?
111. R u configured SSL setup?
Yes. SSL address following important security considerations.
1. Authentication
2. Confidentiality
3. Integrity

To install and configure SSL we need

1. A server certificate key store. 2. An https connector
112. Which key u r using in SSL?
Symmetric key--- secret keys
Asymmetric key----------public private key pairs
113. What is the command to see the authentications?
DSPMQAUT: It will display the authenticated users
114. What may be reasons for getting channel is in retrying state?
1. If other side receiver channel is not defined
2. May channel was not started
3. Listener not yet started
115. What are the reasons for getting messages in dead letter queue?
1. If queue is full
2. Queue put inhibited.
3. Msg length is exceeded
116. What happen to messages (persistence& non persistence) if destination queue is
full if there is no dead letter queue?
PERSISTENT: if queue is full, messages are coming back to Xmitq and channel will be
going to retrying state.
NON-PERSISTENT: Those types of messages are discarded.
117. What is channel state in above case?
Retrying
118. Tel me some system default queues?
1. SYSTEM.DEFAULT.ALIAS.QUEUE
2. SYSTEM.DEFAULT.INITIATIONS.QUEUE
3. SYSTEM.DEFAULT.LOCAL.QUEUE
4. SYSTEM.DEFAULT.MODELS.QUEUE AND 5.
SYSTEM.DEFAULT.REMOTE.QUEUE
121. Can we define remote queue definition without XMITQ? Is it working?
We can define remote queue definition without XMITQ, but XMITQ name should be
remote Queue manager name.
121. Can we take the backup from XMIT queue massages?
When you are trying to get the backup of xmit queue massages,it will store error
information the file. i.e 2016=MQRC_GET_INHIBITED.
122. How to take backup of massages from queue?
AMQSBCG Qname QMname > E:/mq
123. How to increase no. of primary and secondary log files size?
Go to registry edit, in that only you can change the number of primary and secondary
files. After changing the number, immediately those are not affected, when the default
primary files are full than only other files are come into picture.

    Scenario 2

INTERVIEW QUESTIONS
 Tell me about self (or) take me through your resume?
1. What are the different types of Logs?
We have two types of logs.
1. Transactional logs:
2. Error logs.
3. Difference between Errors and Qmgr errors?
Errors: This will contain all S/W level errors and Information
QMGR:This will contains all the information of QMGR objects and errors
4. How you enable Trace?
* Or start a high detail trace for one queue manager:
strmqtrc -t all -t detail -m MY.QMGR
* Or start a high detail wrapping trace and limit the file size to 5MB :
strmqtrc -l 5 -t all -t detail -m MY.QMGR
 # End all tracing:
endmqtrc -a
# Format the trace files:
dspmqtrc *.TRC
Or format wrapping trace files:
dspmqtrc *.TRC *.TRS

5. What does the FDC contain?

FDC File:Failure data capture,If any S/W related error occurs this file will be created,in
FDC we have prob-Id based on that we will find the solution in IBM Tech notes.
probid
userid
application name
major error code
minor error code
problem civierty
probtype
process
6. Channel in doubt and in flight state?
The INDOUBT count specifies the number that were interrupted between phase-1 and
phase-2 of the commit process. These must undergo forward recovery to ensure that
resources modified by them are unavailable until their INDOUBT status is resolved.
 The INFLIGHT count specifies the number that neither completed phase-1 of the
commit process nor began the process of backing out. These must undergo backward
recovery to restore resources modified by them to their previous consistent state
7. Sequence number wrap?
This is the highest number the message sequence number reaches before it restarts at 1.
The value of the number should be high enough to avoid a number being reissued while
it is still being used by an earlier message. The two ends of a channel must have the
same sequence number wrap value when a channel starts up; otherwise, an error occurs.
The value may be set from 100 through 999 999 999 

8. Difference between Full & Partial Repository?

Full repository: This will contains all the information of Cluster QMgrs and other
objects.
Partial repository: This will Contains the information of that particular Qmgr and Other
instances for communication.
9. Where do we find the cluster information?
We have one Queue i.e SYSTEM.CLUSTER.REPOSITORY.QUEUE, in that all the
cluster info will stored
10. What does contain in Auto define channel?
It contains channel name, port No. and Ip address That are mentioned in the Receiver
channel
11. What is the backup Queue of the QMGR?
Dead letter queue
12. How you set Authentication?
Using SETMQAUT, this is used assign permissions to the user
SETMQAUT -M QMname -n objname -t objtype -p principle/-g group +all
dmpmqaut -m qmname -n objectname -t objecttype -p user to display set of all users
given permission on the object
dspmqaut ------ to display set of all the permission for the user on the object
13. Will you give permission only for USER or GROUP, if GROUP why?
We can assign permissions to user and if you want assign permissions to group also.if
asign permissions to group that are assign all the user who are under that group.
14. Difference between Receiver & Requester channel?
requester and reciver are same except that the reuqesters can starts the sender from
requester side.

15. Why do we go clustering?

we have so many advantages using cluster
1.administration task will be redused
2.work load balancing
3.increase resource utilization
4.high availability
16. Components of the cluster?
Clussend and clusrcvr channels
SYSTEM.CLUSTER.REPOSITORY.QUEUE
SYSTEM.CLUSTER.COMMAND.QUEUE
SYSTEM.CLUSTER.TANSMISSION.QUEUE (Please do not disable the put or get
attribute on cluster)
17. Which types of Logs are using in your Organization?
Depending upon client requirement we are using both linear and circular loggings
18. How you check the Status of the Queue?
dis qs(qname) type(handle)
19. Default path of the Error logs & Transaction Logs?
In windows:\Program files\IBM/Web spear MQ\Log\ Qmgrs\active
C:\Program file\IBM\Web spear MQ\Qmgrs\QMname\Errors
In Unix:/var/mqm/log/Qmgrs/active
/var/mqm/Qmgrs/Qmname/errors

20. What is the use of PROBID in Fdc?

Using ProbID: we can find the solution in IBM info center, If before anybody face that
problem, otherwise we will rise PMR(problem management report) and it will contains
Application name, major error, minor error and so on..
21. Difference stopping status of QMGRs?
End immediately, End abnormally, ended normally
22. How do you enable the Trigger?
we need to set some properties on queue’s
Trigger on
Trigtype (First/every/depth)
Trigdepth
Trigdata(chalname)
initq()
23. Which types of tickets do you mostly resolved?
instant tickets
24. How to Suspend a Qmgr from the cluster?
Suspend qmgr cluster (clusname)
25. How to add existing Qmgr into the cluster?
If you add it as full repository, you need to add repos keyword to Qm, and create one
clussdr and clusrcvr channels, add cluster attributes to other objects
If you want to add it as partial repository, create clusrcvr channel to that QM and a
clussdr to a queue manager in full repository and set cluster attribute to objects

26. What is the use of alias queue?

This queue is act as reference queue to local, remote and cluster queue’s.
the advantage of alias queue is
1. Hide the details of reference queue to clients.
2. used for follow the naming conventions,
3. Provide different levels of access.
Why do we give ‘Conname’ at Receiver Channel side in Cluster?
In cluster sdr channels are auto generated, based on the receiver channel attributes only
the sdr channel will generated
27. How can you install all the Packages in Linux at a time?
rpm -ivh name of the packages with spaces
28. Tell me the process of installation on Windows and Linux?
on linux
df -k df -h to check the disk space
rpm (redhat package manager)
Create mqm userid and make mqm as its primary group.
the installation directory for mqm are opt/mqm
the working data is stored in var/mqm
./mqlicense.sh -accept --- to accept the license
then run the commands to install all the packages required. rpm -ivh packagename
rpm -ivh ( i- install v- verbose h- hash format)
to check the packages installed rpm -qa ! grep mq
ps -ef ! grep mq to end all the processes.

29. Difference between V5, V6 & V7?

30. Differences between persistent and non persistent messages?
1. Persistent msg’s are important, at any cost those must be deliver to destination QM,if
any problem occur Those are placed in Xmitq or in DLQ.
2. Nonpersistent msg’s are not important; if any problem occurs those are discarded.
31. Types of tickets?
1. Instant tickets
2. Change order tickets
32. How many Qmgrs are in your current project?
Nearly 400.
33. How do you convert linear to circular?
we don’t have that type of operation if you want to change,
1. First stop the channels
2. Stop the Qmgr
3. Take the back up of qmanager using save queue manager
4. Delete the Qmgr
5. Recreate it with linear logging
6. Recreate all the queue definitions and give the permission to the queues
34. How many applications connect to your current project?
Display conn(*)
35. Reason codes for 2033, 2053, 2085, 2035, 2537…
2033: Msg not available
2053: Q full
2085: unknown obj name
2035: Not authorized
2537: channel not available
2016 (07E0) (RC2016): MQRC_GET_INHIBITED
2030 (07EE) (RC2030): MQRC_MSG_TOO_BIG_FOR_Q
2031 (07EF) (RC2031): MQRC_MSG_TOO_BIG_FOR_Q_MGR
2042 (07FA) (RC2042): MQRC_OBJECT_IN_USE
2051 (0803) (RC2051): MQRC_PUT_INHIBITED
2057 (0809) (RC2057): MQRC_Q_TYPE_ERROR
2058 (080A) (RC2058): MQRC_Q_MGR_NAME_ERROR
2059 (080B) (RC2059): MQRC_Q_MGR_NOT_AVAILABLE
36. What are the errors we can get at the time of installation?
1. user is not a member of mqm group.
2. Some mq series processes are running while installing.
37. How do you connect MQ Client to MQ Server?
we have three types options for connecting client to server
1.MQCONNX
2.MQSERVER
3.Clientchannel tab
38. Qmgr attributes?
dEADQ,REPOS(),REPOSNL(),CLWLUSEQ(),MAXHANDS(),MAXPRTY()
39. What is listener and port?
Listener is a program running continuously listening for request msg from sdr
Port:unique entry point for a QManager
40. Where the configuration information stores on Linux and windows?
in windows it is stored at registry. in linux it is stored in mqs.ini file.
41. What is the difference between qm.ini and mqs.ini file?
A queue manager configuration file, qm.ini, contains information relevant to a specific
queue manager. There is one queue manager configuration file for each queue manager.
The qm.ini file is automatically created when the queue manager with which it is
associated is created.
The WebSphere® MQ configuration file, mqs.ini, contains information relevant to all
the queue managers on a WebSphere MQ installation. It is created automatically during
installation. In particular, the mqs.ini file is used to locate the data associated with each
queue manager
42. How do you configure the Qmgr before you install fix pack?
43. Difference between upgradation and migration?
---->An "upgrade" generally refers to an enhanced version of the software
---->if you migrate from a previous version of WebSphere MQ for Linux,
you must uninstall your current version before installing WebSphere MQ Version
44. Which tool you use to connect with Linux and mainframes?
putty to connect to linux.
telnet or ssh to connect to mainframes.
45. How many channels we can create in Distribution Queuing for a
Qmgr?
One sender and receiver channel
46. If you create 100 channels for a Qmgr… How can you create 101
Channel?
Normal way like:Define chl(chlname) chltype(type) conname(Ip&port)
47. How many years of experience you have?
3.3 YEARS
48. Are you supporting for L2 or L3?
l2

49. Who is your Vendor?

wipro
50. Who is your Client?
Carrefour
51. Project name?
Infrastructure engineering services.
52. Which ticketing tool you are using?
BMC REMEDY,RADIX, OPEN HP view
53. Which monitoring tool you are using?
OMEGAMON XE , Q pasa, BMC Main View
54. Your monitoring and ticketing tools belong to?
BMC
55. Your mail server and chat server?
lOTUSNODES, sametime
Microsoft outlook, office communicator
56. At which location your L3 team will be?
Client location
57. How can you recover the damaged object and its syntax?
using media recovery we can recreate damaged objects
rcrmqobj -m Qmname -t objtype -n objname
58. Channel attributes?
chltype(),discint(),batchhb(),trptype(),maxmsgl(),xmitq() conname() rqmname()

59. Different status of channel?

initializing,binding,retrying,running,inactive,stopped,paused
60. Are you supporting for 24*7 or on-call?
i have supported on-call .
61. Why do we go for MQ Client?
. No need for a full WebSphere MQ implementation on the client machine.
. Hardware requirements on the client system are reduced.
. System administration requirements are reduced.
. Application running on a client can connect to multiple queue managers on different
systems.
. Alternative channels using different transmission protocols can be used
. Reduce the burden on other clients
62. In your company which Client-Server architecture is using?
63. Do you raise any PMR so far?
i have never raised PMR(problem management record)
64. Who send the tickets to you?
users, application team, all the members who are involved in the current project
65. How do you escalate the ticket to L3?
66. Have you ever raised any tickets so far?
yes.
67. Have you ever raised change order?
no
68. Which flavor you are using on Linux?
Red hat
69. Differences between MQI and MSG Channels?
MQI channels are used between MQ client and MQ sever, those are bi-directional
Types: server connection channel
Client connection channel
MSG channels are uni-directional, and used between QM
1. Sender
2. Receiver
3. Cluster sender
4.cluster rceiver
5.server
6. Client
7.requster
70. Default objects in Cluster?
SYSTEM.CLUSTER.REPOSITORY.QUEUE
SYSTEM.CLUSTER.COMMAND.QUEUE
SYSTEM.CLUSTER.TRANSMISSION.QUEUE
Queues and channels.
71. Difference between Dead-Letter Header and Handler?
if msg’a are come to DLQ, QM will add dead letter header to msg,it contains reason for
failure, destination queue and QM details such type of info’n
using dead letter handler you pick the msg’s from DLQ placed it in destination queue
72. What is sync point?
This is nothing but unit of work in two phase commit

73. Tell me something about unit of work?

the period of updates between two sync points is called unit of work.
74. Can you change the log file size?
No.
75. Where the latest information stores in error logs and why?
In the first file.
76. Can you increase the no. of error logs?
no
77. What is the command to check the disk space on Linux?
df -k df -h
78. Which command we use to check the installed packages on Linux?
rpm -qa | grep mq
79. Command to kill the process on Linux?
$ ps ux ----------to list all the processes.
$ kill -9 Pid -------------to kill particular process...
80. Do you run the runmqdlq program every time?
Depending upon the messages those are coming to the DLQ.
81. How can you check the listener port is running from your desktop?
NETSTAT -a
82. What is the use of telnet, ping and tracert?
ping is used to check the status of remote channel.
telnet is used for remote access of another system.
it shows path taken to reach a particular destination over a network.
83. How can you connect to remote server from your desktop?
Using MSTSC
84. How many primary and secondary logs we can create on windows &
Linux (Max)?
windows:primary file:254 ,secondary:253
linux:primary files:510,secondary:509
85. Explain the concept of cluster workload balance?
86. What are the attributes of workload balance?
Defbind(notfixed)
put()
clwluseq(local/any/QMGR)
clwlrank(0-9)
clwlprty(0-9)
clwlwght()
clwlmruse()
87. Explain client-server architecture?
88. What are the pre-requisites for MQ before install?
1. Hardware requirements----disk space
2. Software requirements----o/s specifications
89. Explain the process migration?
90. Have you ever done migration and how?
91. How can we take the Qmgr backup?
- create the backup queue manager
- copy the data and log files from your primary queue manager over the backup queue
manager's data and logs
- flag backup qmgr as a backup and replay log extents (strmqm -r)
- periodically copy over the log files prior to the CURRLOG value from the queue
manager
saveqmgr -m MQ_BACKUP -r MQ_C1_01 -f MQ_C1_01.txt
92. Error log file name?
error log file name is:AMQERR01,AMQERR02,AMQERR03
93. What is the use of client channel tables?
Using client channel table we can connect with different QM’s and different clients will
connect to single QM
94. How many max channels can connect to a Qmgr?
The default for maximum channels is 100 for qmgr. it can be set to higher in the qm.ini.
95. How can you find the max channels are connected to a Qmgr?
dis qmstatus conns
96. Channel components?
chltype() conname() trptype() xmitq() batchsz() hbint()
97. What is the use of trig data in channel?
which chnnel you want to up at trigger event fired.provide channel name
98. What does initiation queue contain?
This will contains trigger massage generated by QM
99. How can we check whether the Qmgr contain Dead-latter queue or
not?
DIS QMGR DEADQ(*)
100. How many servers, Qmgrs in your environment?
100 servers. 400 qmgrs.

101. Which programs you use for running the trigger monitor when you
use your own initiation queue?(in application and channel triggering)
In application triggering we are using RUNMQTRM
in channel RUNMQCHI INITQ()
102. What is the default size of /var /mqm and /opt /mqm?
Allow 130 MB as a minimum for a WebSphere MQ server and 15 MB as a minimum for a
WebSphere MQ client.
x-86 201 mb iseries -183
103. What is the difference between Control & Runmqsc Commands?
RUNMQSC commands are used with in Qm for creating Qm objects and altering
QMGR.
CONTROL commands are used for creating starting and running QM, and for set
authentication
104. In Cluster for Round-Robin process defbind (open) what is happen?
if you set defbind open, all msg’s are placed where the first msg is place
105. Explain the distributed queuing setup?

106. What is meant by distribution queuing?

107. What is difference between distribution and clustering?
in distributions queing we have to create more no of objects like remoteqs. transmission
ques and sender, reciever channels for every remote queue manager.
in clustering we can logically connect queue managers with the creation of less no.of
qmgr objects .
108. Why we go for clustering?
1.simplifying system administration
2.work load management
3.less no of qm objects like rqd, channels.
4.high availability
109. In cluster we have 4 Qmgrs and having same instance in all Qmgrs I
have to send messages to a particular Qmgr then how u configure?
assign clwlrank and clwlprty for particular queue.
110. Tel me prerequisites for MQ admin?
111. R u configured SSL setup?
yes.
ssl address following important security considerations.
1.authantication
2.confidentiality
3.integrity
to install and configure ssl we need
1. a server certificate key store.
2. an https connector
112. Which key u r using in SSL?
symmetric key--- secret keys
Asymmetric key----------public private key pairs
113. What is the command to see the authentications?
DSPMQAUT: It will display the authenticated users
114. What may be reasons for getting channel is in retrying state?
1. if other side receiver channel is not defined
2. may channel was not started
115. What are the reasons for getting messages in dead letter queue?
1.if queue is full
2. Queue put inhibited. 3.Mag’s length is exceeded
116. What happen to messages (persistence& non persistence) if
destination queue is full if there is no dead letter queue?
PERSISTENT: if queue is full, msg are coming back to xmitq and channel will be going
to retrying state.
NON-PERSISTENT: That type of msg’s are discarded.
117. What is channel state in above case?
retrying
118. Tel me some system default queues?
1.SYSTEM.DEFAULT.ALIAS.QUEUE
2.SYSTEM.DEFAULT.INITIATIONS.QUEUE
3.SYSTEM.DEFAULT.LOCAL.QUEUE
4.SYSTEM.DEFAULT.MODELS.QUEUE
5.SYSTEM.DEFAULT.REMOTE..QUEUE
119. can we define remote queue defination without XMITQ? is it working?
we can define remote queue defination without XMITQ,but XMITQ name should be
remote Queue manager name.
121.can we take the backup from XMIT queue massages?
when you are trying to get the backup of xmit queue massages,it will store error
information the file. i.e 2016=MQRC_GET_INHIBITED.
122.How to take backup of massages from queue?
amqbcg Qname QMname > E:/mq
123.how to increase no. of primary and secondary log files size?
Go to registry edit,in that only you can change the number of primary and secondary
files.after changing the number ,imediatlly those are not effected,when the default
primary files are full than only other files are come into picture.

  Scenario3

What is MQ and what does it do?Ans. 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.What is
Message driven process?Ans . 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. 
What are advantages of the MQ?Ans. 1. Integration.2. Asynchrony3. Assured
Delivery4. Scalability.How does it support the Integration?Ans. 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
What is Asynchrony?
Ans. 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.

What are the hardware and Software 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 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:
1. TCP/IP
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

What are the software and hardware requirements for installing MQ on

Windows?
Ans: 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:
1. TCP/IP
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

what is a Message and what does it contain?

Ans: 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, 

What is the Max Length of the message does MQ support/

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 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. 

What is the effect of using Persistant messages?

Ans: 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
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 eventEx COA/COD
Sizes ?
 
Qmanagerà10000 Msgs Maxmsglengthà4 Mb
Queueà5000 Msgs Maxmsglengthà4 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 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.

 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 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 
What are the Objects used in Web sphere MQ?
Ans: 1. Queue Manager
2. Queues
3. Channels
4. Processes
5. Name lists.

Mention the No of Characters required for creating names of the MQ

objects?
Ans: For MQ Channels it is 20 Characters
For Remaining objects it is 48 characters.What about is the Default port number
for MQ Queue Manager?
Ans: 1414

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…

Is the MQSC attributes are Case sensitive?

Ans: 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.

SCRIPT COMMANDS:-
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)
· DEFINE :-To define/create 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 manager
· 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 stop particular channel or listener
· REFRESH :-used to refresh the security every time after giving or executing, set mgr or
command for queue manager or object
· RESET :-used to reset channel,cluster,queue manager
· RESOLVE :-to resolve the channel 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 can we write the MQSC commands that have too many parameters/
Ans: 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.

What is programmable command format (PCF) commands?

These commands are issued from a programme for local or remote administration done
by programmers. 

What are commands used for creating the Queue manager from the
Command prompt?
Ans: 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 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. 

Where the backup files are present after creating the Queue Manager?
Ans: 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.

What is the command 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 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. 

What’s the message code for Stopping a Queue Manager?

AMQ4044 Queue manager 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

IBM 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 queues 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 Queue
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
which the application is connected. 

Model Queue: Model queue is a template of a queue definition that uses when creating
a dynamic queue. 

Alias Queue: Queue definition, which is Alias to an actual Local or Remote Q. Used for
security and easy maintenance. 

Remote Queue: Object that defines a Queue belongs to another Q Manager (Logical

Def). 

Initiation Queue: An initiation queue is a local queue to which 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 automatically 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 created using a remote-queue

definition with a blank RNAME.

 
What are the attributes required for the Remote Queue Definition?
Ans: 1.Name of the Queue
2. Transmission Queue Name.
3. Remote Queue Manager name
4. Remote Local Queue Name 

How can U define 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 queues are queues that temporarily store messages that are destined
for a remote queue manager. You must define at least one transmission queue for each
remote queue 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 triggering. A queue manager puts a
trigger message on an initiation queue when a trigger event occurs. A trigger event is a
logical combination of conditions that is detected by a queue manager. 

What is Dead Letter Queue?

Ans: A dead-letter (undelivered-message) queue is a queue that stores messages that
cannot be routed to their 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 dead-letter queue
on each queue manager involved. 
What 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 the usage attribute from normal to TransmissionDefine a Local Queue
LQ using the MQSC Commands in the QM QM1
Ans: runmqsc QM1
Define qlocal (LQ) 

What are the Difference B/W Predefined & Dynamic Queues?

Ans: Queues can be characterized by the way they are created:
1. Predefined queues are created by an administrator using the appropriate MQSC or
PCF commands. Predefined queues are permanent; they exist independently of the
applications that use them and survive Web Sphere MQ restarts.

2 Dynamic queues are created when an application issues an MQOPEN request

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 same
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 process definition object defines an application that starts in response to a
trigger event on a WebSphere MQ queue manager. The process definition attributes
include the application ID, the application type, and data specific to the application.
What is intercommunication and its components to send message ? 

What is Intercommunication?
Ans: In Web Sphere MQ, intercommunication means sending messages from one
Queue manager to another. The receiving queue manager could be on the 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 environment.
Message channels Message channel agents
Transmission queues Channel initiators 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. Dead Letter Queue
3. Receiver Channel 4.Listenr

***.The sender and receiver channels names should be same.

 What is channel and mention different types of channels in MQ?

Ans: Channels are objects that provide a communication path from one queue manager
to another. Channels are used in distributed queuing to move messages from one queue
manager to another. They shield applications from the underlying communications
protocols. The queue managers might exist on the same, or different, platforms.
Different types of Channels:
1. Sender-Receiver Channels
2. Requester-Server Channels
3. Client Connection channels
4. Server Connection Channels.
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 server and vice versa.They are Bi-directional Channels
1. Server-connection
2. Client-connection

How many Channel Combinations?

1.Sender-receiver Channel
2.Requester-sender Channel
3.Cluster-Sender- Receiver Channel
4.Requester-server Channel
5. Server-receiver Channel
6.Client-Server Channel

What are the attributes required for the Sender Channel?

Ans: 1. The Name of the Channel
2. The Connection name
4.Transport Type
5.Scyexit 

What are different Channel status?

Ans: Channel Status:
1. Inactive
2. Running
3.Retrying
4.Stopped

What about Initializing & Binding states?

Ans: Before running state first the channel will initializes the listener & Binds with the
Receiver Channel then it goes into running mode. 

Tell me Some Channel Attributes?

Batch Heartbeat Interval (BATCHHB): This heartbeat interval 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 active, the batch can be backed out rather than
becoming in-doubt, Batch interval (BATCHINT), Batch size (BATCHSZ), Channel type
(CHLTYPE), Cluster (CLUSTER), Cluster namelist (CLUSNL), Connection name
(CONNAME), Convert message (CONVERT), Disconnect interval (DISCINT), Heartbeat
interval (HBINT), KeepAlive Interval (KAINT), Long retry count (LONGRTY), Long
retry interval (LONGTMR), Maximum message length (MAXMSGL)

Why is Channel RETRYINT attribute used?

If a message is places in 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 RETRYINT by default the retry interval is 60 seconds.
Receiver Cluster Receiver Requester

What is channel disconnect interval?

This is a time-out attribute, specified 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 queue 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 maximum number of messages that can be sent through a
channel before taking a checkpoint. 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 through 9999. 

What is BATCH HEARTBEAT INTERVAL?

Ans: The batch heartbeat interval allows a sending channel to verify that the receiving
channel is still active just before committing a batch of messages, so that if the receiving
channel is not active, the batch can be backed out rather than becoming in-doubt, as
would otherwise be the case. By backing out the batch, the messages remain available
for 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 specify a time-out value for a
channel. The Keep Alive Interval parameter is a value passed to the communications
stack specifying the Keep Alive timing for the channel. 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 fails, the short retry count number
is decremented and the channel retries the remaining number of times.

What are the ways to start a channel?

Use the MQSC command START CHANNEL
Use the control command runmqchl to start the channel as a process
Use the channel initiator to trigger the channelType of channel states:
Inactive and Current- Stopped, Starting, Retrying and Active

What are the three options for stopping channels?

QUIESCE FORCE TERMINATE

What are the components of message channel?

A queue manager to communicate with another queue manager uses message channel.
The components of a message channel are
1. Sender Message channel agent: Sender MCA is a program that transfers messages
from a transmission queue to a communication link
2. Receiver MCA: It transfers messages from the communication link into the target
queue
3. Communication protocol: Responsible for transferring messages A message channel
is unidirectional. 
What is Message Channel agent (MCA)?
Ans: A message channel agent (MCA) is a program that controls the sending and
receiving 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 communication
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 initiated the communication;
otherwise it is called a responder MCA. 

What is Channel 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 triggering criteria for that queue, a message is sent
to the initiation queue, triggering the channel initiator to start the appropriate sender
channel. You can also start server channels in this way if you specified the connection
name of the partner in the channel definition. This means that channels can be started
automatically, based upon messages arriving on the appropriate transmission queue.
You need a listener program to start receiving (responder) MCAs. Responder MCAs are
started in response to a startup request from the caller MCA; the channel listener
detects incoming network requests and starts the associated channel.

Channel Errors?
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 programs and what are the types?

Channel-exit programs are called at defined places in the processing carried out by MCA
programsSecurity Exit: You can use security exit programs to verify that the partner at
the other end of a channel is genuineMessage Exit: Message Exit can be used for
Encryption on the link, message data conversion, validation of user ID,Message-retry
Exit: Message-retry exit is called when an attempt to open the target queue is
unsuccessfulSender and receiver 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 types available
1. Circular: The circular logging is used for restart recovery. It is the default logging
method. Circular is used in Development and Testing Queues. Circular logging keeps all
restart Data in a ring of log files. Logging fills the first file in the ring, then moves on to
the and so on, until all the files are full. It then goes back to the first file in the ring and
starts This continues 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 Sequence of files. Space
is not reused, so you can always retrieve any record logged from the time that the queue
manager was created. As disk space is finite, you might 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 necessary. 

What is the Default location where the logs are stored and mention the
default sizes?
Ans: Default location:
Windows: C:\Program Files\IBM\WebSphere MQ\log\qmgr
UNIX: /var/mqm/log 

What is the log file size?

Ans: In Web Sphere MQ for 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 for 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 file size?

Ans ; You cannot change the log file size. For this you need to drop and re-create the
queue manager. The number of log files primary & secondary can be 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 log files: The number of primary log files to be allocated is 3 by default the
minimum is 2 and MAX in Win 253 / Unix 510
Secondary log files: The number of secondary log files to be allocated is 2 by default the
minimum is 1 and MAX in Win 252 / 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 perform 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 doesn.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. 

What is the command that is used to provide authorization for the clients?
Ans: setmqaut -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
Mqrc 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_OBJECT_TYPE_ERROR.
Mqrc 2086: MQRC_UNKNOWN_OBJECT_Q_MGR.
Mqrc 2035: MQRC_NOT_AUTHORIZED. 

What are different modes in which a application can connect to a

Queuemanager?
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 only to
programs running on the MQSeries server that hosts the queue manager. A program
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 binding mode.

2. Client Connection: Client connection uses a TCP/IP connection to the MQSeries

Server and enables communications with the queue manager. Programs using client
connections can run on an MQSeries client machine as well as on an MQSeries server
machine. Client connections use client channels on the queue manager to communicate
with the queue manager. The client connection does not support 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-point messaging involves working with queues of messages.
The sender sends messages 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 addresses the message to the queue that holds the messages for the
intended (receiving) client.
Publish/Subscribe: In contrast to the point-to-point model of communication, the
publish/subscribe model enables the delivery of a message to multiple recipients. A
sending client addresses, or publishes, the message to a topic to which multiple clients
can be subscribed. There can be multiple publishers, as 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 for the
provision of alternative routes between queue managers for traffic balancing and link
failure corrective action. A transmission queue cannot be used by another channel if the
previous channel to use it terminated leaving a batch of messages 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: The 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 broker. Possible states are:
starting, running, stopping, quiescing, not active and ended abnormally.

——–dspmqbrk -m MYQMGRNAME

The endmqbrk command is used to stop a broker. There are two options: -c requests a
controlled shutdown (default), -i requests an immediate shutdown.

——-endmqbrk -i -m MYQMGRNAME 

What is multiple hoping?

Ans: If there is no direct communication link between the source queue manager and
the target queue manager, it is possible to pass through one or more intermediate queue
managers on the way to the target queue manager. This is known as a multi-hop.

What is Local administration and Remote administration?

Local Administration: Means carrying out administration tasks on any queue managers
you have defined on your local system. 
Remote Administration: This allows you to issue commands 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 manager. You do not have to log on to that
system, although you do need to have the appropriate channels defined. The queue
manager and command server on the target system must be running

Difference between Control Commands used in Windows and 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 this attribute is set it forces all the messages sent to this queue to be sent to the
same instance of the queue (go to the same queue in cluster)

Difference between MQPUT and MQPUT1 call ?

The MQPUT1 call always operates as though MQOO_BIND_NOT_FIXED were in
effect, that is, it always invokes the workload management routine.

When is Channel security exit program called?

Are called at MCA initiation and termination
Stopping unauthorized queue managers putting messages on your queues
Use OS security, Object Authority Manager (OAM) on WebSphere MQ user-written
procedures

What happens if DEAD letter Queue 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 queue 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 having to specify the name of
the remote queue or the remote queue manager, or the name of the transmission queue.
This gives you location independence.

What happens if channel terminates when fast non-persistent messages are

in transit?
If a channel terminates while fast, non-persistent messages are in transit, the messages
are lost and it is up to the application to arrange for their recovery if required. If the
receiving channel cannot put the message to its destination queue then 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-retry: If the MCA is unable to put a message to the target queue for a reason
that could be transitory (for example, because the queue is full), the MCA has the option
to wait and retry the operation laterReturn-to-sender: If message-retry was
unsuccessful, or a different type of error was encountered, the MCA can send the
message back to the originatorDead-letter queue: If a message cannot be delivered or
returned, it is put on to the dead-letter queue (DLQ). You can use the DLQ handler to
process the message
Recovery scenario –Disk Drive Full, damaged Queue manager object, Damaged single
object, Automatic media recovery failure
MQ ensures that messages are not lost by maintaining records (logs) of the activities 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 Queues or target Queues. Use the runmqdlq command to start the dead-
letter queue (DLQ) 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 and 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 are put into a report that is sent to stdout. 

Which field of the MQDLH structure contains a reason code that identifies
why the message is on the DLQ?
Reason field

What is completion code(MQCC) and reason code(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), 2- call 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 ID?

This is a byte string that the application can use to relate one message to another, or to
relate the message to other unit of work that the application is performing. The
correlation identifier is a permanent property of the message, and persists across
restarts of the queue manager

Explain commit and Back Out units 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 preserve 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 Out: When a program performs a back out, WebSphere MQ restores the queue by
removing the messages that were put on the queue by that unit of work. The way in
which the program performs the commit and back out operations depends on the
environment 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 call 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 Queue

 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. Segmentation
is a technique whereby the queue manager or application splits the message into smaller
pieces called segments, and places each segment on the queue as a separate physical
message. The application that retrieves the message can either retrieve 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 Namelist? when do you use it?

A namelist is a WebSphere MQ object that contains a list of other WebSphere MQ
objects. Typically, namelists are used
1.By trigger monitors, where they are used to identify a group of queues.
2.Namelists are also used with queue manager clusters to maintain a list of clusters
referred to by more than one WebSphere MQ object.
3. The advantage of using a namelist is that it is maintained independently of
applications; it can be updated without stopping any of the 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 with queue manager clusters to maintain a list of
clusters referred to by more than one WebSphere MQ object

 What are name services?

The name service is an installable service that provides support to the queue manager
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 two-phase commit process)?
Local unit of work: Units of work that involve only the queue manager are called local
units of work. Syncpoint coordination is provided by the queue manager itself (internal
coordination) using a single-phase commit process.
Use global units of work when you also need to include updates to resources belonging
to other resource managers. Here the coordination 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 attribute, SCMDSERV, the command
server is either started automatically when the queue manager starts, or must be started
manually.
Start: Using strmqcsv saturn.queue.manager where saturn.queue.manager is the QM
name
Display: dspmqcsv Stop: endmqcsvWhen 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 the queue manager, stop and restart command server (A command
server processes command messages) and channel programs

What is a MQ Series Queue manager Configuration file (qm.ini)?

A queue manager configuration file (qm.ini) to effect changes for specific queue
managers. There is one qm.ini file for each queue manager on the node. (A queue
manager configuration file, qm.ini, contains config information relevant to a specific
queue manager. There is one queue manager configuration file for each queue manager.
The qm.ini file is automatically created when the queue manager with which it is
associated is created. For example, the path and the name for a configuration file for a
queue manager called QMNAME is:/var/mqm/qmgrs/QMNAME/qm.ini)

What is name transformation in naming a Queue manager Configuration

File?
A qm.ini file is held in the root of the directory tree occupied 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 directory 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)?

Contains information relevant to all the queue managers on the node. It is created
automatically during installation (The WebSphere MQ configuration file, mqs.ini,
contains 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 systems
is in the /var/mqm directory. It contains: v The names of the queue managers 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 queue manager (MQCONN or MQCONNX calls), Opening the object
(MQOPEN or MQPUT1 calls), Putting and getting messages (MQPUT or MQGET calls),
Closing the object (MQCLOSE)

1) What Is Mq And What Does It Do?

Ans:

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.

2) What Is Message Driven Process?

Ans:
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.

3) What Are Advantages Of The Mq?

Ans:

 Integration.
 Asynchrony
 Assured Delivery
 Scalability.

4) How Does It Support The Integration?

Ans:

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

5) What Is Asynchrony?

Ans:

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.

6) What Are The Hardware And Software 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:

 Server installation: 50 MB
 Client installation: 15 MB
  Data storage (server): 50 MB
 Data storage (client): 5 MB.

Software Requirements: Operating system: The operating systems supported by WebSphere

MQ for AIX, V5.3 are:

 AIX V4.3.3, with PTF U472177, running in a 32 bit environment, on 32 or 64 bit hardware.
 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.
 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:
o TCP/IP
o SNA LU 6.2.

Databases: DB2 7.1, 7.2

Oracle 8i and 9i

Sybase v12 or v 12.5

7) What Are The Software And Hardware Requirements For Installing Mq On Windows?

Ans:

MQ v 5.3 supports Windows 2000, Windows 2000XP,Windows 2000NT,

Windows 2003 SE, Windows 2003EE.

Disk Storage:

Typical storage requirements are as follows:

 Server installation: 50 MB
 Client installation: 15 MB
 Data storage (server): 50 MB
 Data storage (client): 5 MB.

Connectivity The network protocols supported by WebSphere MQ for AIX, V5.3 are: 

 TCP/IP
 SNA LU 6.2.
 LU 6.2
  NetBIOS 

Databases: DB2 7.1, 7.2

Oracle 8i and 9i

Sybase v12 or v 12.5

8) What Is A Message And What Does It Contain?

Ans:

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:

 The application data. The content and structure of the application data is defined by the
application programs that use it.
 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,

9) What Is The Max Length Of The Message Does Mq Support?

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).

10) What Is The Difference Between Persistent And Non Persistent Messages?

Ans:

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.

11) What Is The Effect Of Using Persistent Messages?

Ans:

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

12) What Is The Sizes Of Messages?

Ans:

 Qmanagerà10000 Msgs Maxmsglengthà4 Mb

 Queueà5000 Msgs Maxmsglengthà4 Mb
 Question 13. What Is The Attribute Used To See The Message Length?
Answer :
MaxMsgLength
 Question 14. What Is Mq Client?
Answer :
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.

13) 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 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

14) What Are The Objects Used In Web Sphere Mq?

Ans:

 Queue Manager
 Queues
 Channels
 Processes
 Name lists.
15) Mention The No Of Characters Required For Creating Names Of The Mq Objects?

Ans:

 For MQ Channels it is 20 Characters

 For Remaining objects it is 48 characters.

16) What About Is The Default Port Number For Mq Queue Manager?

Ans:

1414

17) Difference Between Mqsc Commands And Control Commands?

Ans:

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…

18) Is The Mqsc Attributes Are Case Sensitive?

Ans:

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.
SCRIPT COMMANDS : 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)

 DEFINE: To define/create 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 manager
 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 stop particular channel or listener
 REFRESH :-used to refresh the security every time after giving or executing, set mgr or
command for queue manager or object
 RESET :-used to reset channel,cluster,queue manager
 RESOLVE :-to resolve the channel 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

19) How Can We Write The Mqsc Commands That Have Too Many Parameters?

Ans:

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:

 A minus sign ( ) indicates that the command is to be continued from the start of _ the
following line.
 A plus sign (+) indicates that the command is to be continued from the first nonblank
character on the following line. 

20) How Can U Make The Existing Queue Manager As An Default Queue Manager?

Ans:

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.

Subscribe For Free Demo

SUBSCRIBE 

21) Where Are The Backup Files Are Present After Creating The Queue Manager?
Ans:

Windows systems:

If you use Web Sphere MQ for Windows NT and Windows 2000, configuration information is
stored in the Windows Registry.

UNIX Systems:

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.

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.

22) What Is The Command Used For Starting The Queue Manager?

Ans:

strmqm QMName

23) What Is The Command Used For Stopping The Queue Manager?

Ans:

 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.

24) What’s The Message Code For Stopping A Queue Manager?

Ans:

AMQ4044 Queue manager stopping

25) What Is The Command Used To Delete The Queue Manager?

Ans:

dltmqm QMName

26) Display The Attributes Of The Queue Manager Qm1?

Ans:

runmqsc QM1 Display qmgr

27) What Is Programmable Command Format (pcf) Commands?

Ans:

These commands are issued from a programme for local or remote administration done by
programmers.

28) What Is Ibm Mq Series? What Is The Significance Of Mq Series?

Ans:

A middle ware from IBM

 It has runtime managers such as Queue Managers and Queues

 Queue is an object which holds messages of various formats – XML/text/byte
 Queue manger maintains and manages objects like Queues, channels
 Various listener applications listen to these queues for grabbing the messages, followed
by processing these messages
 Java Messaging Service is one of the standards provided by JEE specification for
asynchronous messaging
 The queues can be defined in JEE container and send messages on these queues
 Message Driven Bean can be configured for listening the JMS queues
 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:
o WebSphere MQ will significantly improves the flow of information across an
enterprise
o The message is placed and adjusted for dynamic business requirements
o MQ series reduce maintenance, integration costs and acts as a bridge to various
technologies
o MQ Series reduces costs and all the disruptions are processed from data loss
o Allows ongoing maintenance efforts through universal service delivery
o Security breaches are eliminated and insures the compliance through message
and transaction integrity
Enhance Your Career with IBM Websphere MQ Training from
Certified Experts
 Instructor-led Sessions
 

 Real-life Case Studies

 Assignments
Explore Curriculum
29) How To Define A Buffer Pool For Holding Messages In Main Storage? Explain?

Ans:

 Buffer pool is defined by using DEFINE BUFFPOOL

 DEFINE BUFFPOOL can be issued only from CSQINP1 data set
 DISPLAY USAGE TYPE(PAGESET) can be used for displaying buffer pool information
 The synonym DEF BP can also be used instead of DEFINE BUFFPOOL
 Example:
DEFINE BUFFPOOL
BUFFERS(1000)
DEFINE BUFFPOOL(buf-pool-id)
BUFFERS(integer)

Parameter descriptions

o (buf-pool-id) Buffer pool identifier, and a mandatory entry

o An integer which in the range from zero through 15.

 BUFFERS(integer)
 o Integer represents the number of 4096-byte buffers

30) What Are The Telemetry Capabilities?

Ans:

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

31) What Are The Integration And Supported Environments In Ibm Mq?

Ans:

 IBM MQ supports in virtual integration

 Supports more than 80 platform configurations, including z/OS support
 Integrates with CICS,IMS,DB2,Microsoft .Net and JEE environments
 Supports Message Queue Interface and Industry standards such as JMS interface along
with integrated public-and-subscribe support
 Internet secure communication is supported with industry standard SSL
 IBM MQ supports IP V6
 Awarded Common Criteria certification
 Supports end-to-end governance with Extended Security Edition

32) Mention Some Rules For Using Mqsc Commands?

Ans:

Each command of MQSC starts with a primary parameter, followed by a secondary parameter

 The name or generic name of the object should be followed by secondary parameter
  The keywords, parentheses and values could be separated by unlimited number of
blanks and commas
 At least one blank immediately preceding each parameter is mandatory, except on z/OS
 Blanks enclosed within a pair of quotations marks are significant
 Repeated parameters are not allowed
 String can contain blanks, lowercase alphabets or special characters other than
period(.), forward slash(/), underscore(_) percent sign(%) must be enclosed in a single
quote
 A blank pair of parenthesis is invalid with out significant information enclosed in
between
 Keywords are not case sensitive

33) What Is Queuemanager In Ibm Websphere Mq ? What Does Queuemanager Do?

Ans:

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.

34) What Is Channel In Ibm Websphere Mq?

Ans:

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.

35) What Is Dead Letter Queue In Ibm Mq Series?

Ans:

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.

36) What Is Ccdt File On Websphere Mq Or Wmq?

Ans:
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.

37) What Is Difference Between Dead Letter Queue And Backout Queue In Websphere
Mq?

Ans:

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.

38) What Is Sslpeer In Ibm Websphere Mq?

Ans:

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 the client. In case of Java or JMS client, SSLPEER is DN of client certificate stored
in its keyStore and sent to the server during SSL handshake.

39) What are the benefits that corporations can have through IBM Websphere MQ?

Ans:

Organizations and corporations can simply send bulk messages over complex networks. There
are no strict protocols that need to be followed. Even if they are, the same can be managed
very easily. Enterprises can make sure of quick information delivery to the destinations and can
always have the things done in the best possible manner.

40) What do you mean by Asynchrony in IBM Websphere MQ?

Ans:

In the queue process, the process of sending or exchange of any message doesn’t depend on
the time. This is exactly what that makes both the sender, as well as the receiver to be
decoupled if the need of same is there. There is actually no need for the sender to wait for
getting the acknowledgment regarding the delivery of the message from the receiver. IT can
continue with this next task. This process is basically considered as Asynchrony in IBM
Websphere MQ.

41) What is the difference between the dead letter queue and backout queue in
Websphere MQ?

Ans:

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

42) What are the Different Types Of Queues?

Ans:

Queues can be characterized by the way they are created:

1. Predefined queues are created by an administrator using the appropriate MQSC or PCF
commands. Predefined queues are permanent; they exist independently of the applications
that use them and survive Web Sphere MQ restarts.

2 Dynamic queues are created when an application issues an MQOPEN request specifying the
name of a model queue. The queue created is based on a template queue definition, which is
called a model queue.

43) How to determine if full repositories are in Synch?

Ans:
SYSTEM.CLUSTER.REPOSITORY.QUEUES should have the same depth. Also, you should find
something in your error logs if it fails. If the channels between the two FRs are able to run, trust
IBM, and assume all good use runmqsc to display all cluster objects. Redirect the output into a
file Analyze both files for differences. 

44) Is the procedure of installation the IBM WebSphere MQ on Aix similar to that for
Windows?

Ans:

Yes, all the requirements are the same except for a few basic ones. For older versions of
Windows such as 2000 and XP, it needs some customized settings in the application. It is
actually free from the network protocols and thus users have no reasons to worry about this.

45) What is the concept of switching?

Ans:

Ina network, there can be a very large number of nodes. Practically it is not possible to establish
a direct physical connection between them all. Of course, this can enhance the cost up to a
great extent and can make the network very complex. Thus, the concept of switching is
considered. It basically acts as a temporary path that is established between a sender and a
receiver for message transfer. The connection is terminated after the message is sent. Because
not all the nodes need channels all the time, this concept can be applied. It is having a lot of
advantages. All the data that seems to be sent on priority can be assigned sent immediately by
stopping other operations.

46) What is the Metrics application?

Ans:

The new IBM Connections Metrics application provides a comprehensive set of quantitative and
qualitative metrics that help measure the business value of IBM Connections to your
organization. IBM Connections uses IBM Cognos Business Intelligence to generate reports that
users can view directly in IBM Connections. Metrics reports can provide your organization with
the information and insight to make the right, fact-based business decisions.

For example, you can generate the following Metrics reports at the global level:
Number of unique authenticated (and anonymous) visitors for the entire system and for
individual components Number of users who created or updated content Most popular
content, based on number of visits, follows, or recommendations At the community level, you
can generate Metrics reports such as the following: Number of unique authenticated (and
anonymous) visitors for the community, including its widgets Number of contributors for each
widget in a community Most active contributors. Most popular content, based on a number of
visits, follows, or recommendations for more information about Metrics, refer to: What are
Metrics.

47) What are the differences between the Metrics reporting functionality for IBM
Connections 3.0 and IBM Connections 4.0?

Ans:

IBM Connections 3.0.1Metrics provides separate reports for each application. Metrics in IBM
Connections 4.0 provides one central user interface to display global metrics reports and
community metrics reports.

Metrics reports in IBM Connections 3.0.1 are presented using simple Metrics reports in IBM
Connections 4.0 are presented in various formats including tables, charts, and other kinds of
graphs.

Metrics in IBM Connections 4.0 employs the powerful capabilities of IBM Cognos Business
Intelligence to provide customers with more features, including reports, dimensions,
customization, and drill up/down.

48) What exactly do you understand with the term MQ and what it is responsible for?

Ans:

MQ abbreviates Message Queuing. When it comes to message-driven processes, IBM enables

users to simply keep up the pace with the WebSphere with which all application programs can
simply be managed. There is no strict upper limit on the platforms when it comes to
communicating and the good thing is a vast support is available from IBM to enable the users
to manage everything simply.
Enroll in IBM Websphere MQ Training Course to Build Your Skill
Sets
Weekday / Weekend BatchesSee Batch Details

49) What is the difference between the local queue and the remote queue in WMQ?

Ans:

Rather simple and fact-based MQ Series interview question. This is asked to see whether the
candidate is familiar with MQ Series terminology or not. In WebSphere MQ, local queues are a
queue on the same queue manager while remote queue refers to queue on different
QueueManager.

50) What are the advantages of the MQ?

Ans:

1. Integration.

2. Asynchrony

3. Assured Delivery

4. Scalability.

51) Mention the Different Types of MQ Queues?

Ans:

There are four types of Queues Available in Web sphere MQ

Local queue object: A local queue object identifies a local queue belonging to the queue
manager to which the application is connected. All queues are local queues in the sense that
each queue belongs to a queue manager and, for that queue manager; the queue is a local
queue.

Remote queue object: A remote queue object identifies a queue belonging to another queue
manager. This queue must be defined as a local queue to that queue manager. The information
you specify when you define a remote queue object allows the local queue manager to find the
remote queue manager so that any messages destined for the remote queue go to the correct
queue manager.

Alias queue object An alias queue allows applications to access a queue by referring to it
indirectly in MQI calls. When an alias queue name is used in an MQI call, the name is resolved to
the name of either a local or a remote queue at run time. This allows you to change the queues
that applications use without changing the application in any way; you merely change the alias
queue definition to reflect the name of the new queue to which the alias resolves. An alias
queue is not a queue, but an object that you can use to access another queue.

Model queue object A model queue defines a set of queue attributes that are used as a
template for creating a dynamic queue.

52) What is Process Definition and what are the attributes does it contain?

Ans:

A process definition object defines an application that starts in response to a trigger event on a
WebSphere MQ queue manager. The process definition attributes include the application ID,
the application type, and data specific to the application.

53) What is Intercommunication?

Ans:

In Web Sphere MQ, intercommunication means sending messages from one Queue manager to
another. The receiving queue manager could be on the 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 environment. Web Sphere MQ handles communication in a distributed
environment such as this using Distributed Queue Management (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.

54) What do you mean by message descriptor?

Ans:

A massage doesn’t just contain information that needs to be transferred but it contains other
information too. For example, type of message and what exactly its priority is. The same is
described in the message descriptor which is defined by WebSphere MQ. It contains all other
relevant information about the message and among all of the same, its priority that largely
matters.

55) What Is The Difference Between Persistent And Non-Persistent Messages?

Ans:

In the Web Sphere MQ, messages can be either persistent or nonpersistent.

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.

56)  What are the advantages of creating Aliases?

Ans:

When sending messages Remapping the queue-manager name, Altering or specifying the
transmission queue and Determining the destination.

When receiving messages, Using a queue manager as a gateway into the cluster. Gives the
different application to different levels of access authority to the target Queue Allows different
applications to work with the same queue in a different way Simplifies maintenance, migration
and workload balance. 

57) What is Transmission Queue?

Ans:

Transmission queues are queues that temporarily store messages that are destined for a
remote queue manager. You must define at least one transmission queue for each remote
queue manager to which the local queue manager is to send messages directly.

58) What are the channel and mention different types of channels in MQ?

Ans:

Channels are objects that provide a communication path from one queue manager to another.
Channels are used in distributed queuing to move messages from one queue manager to
another. They shield applications from the underlying communications protocols. The queue
managers might exist on the same, or different, platforms.

Different types of Channels:

1. Sender-Receiver Channels

2. Requester-Server Channels

3. Client Connection channels

4. Server Connection Channels.

5. Cluster Sender.

6. Cluster Receiver Channels

59) What do MQSC Commands are used for?

Ans:

You can use MQSC commands to manage queue manager objects, including the queue
manager itself, clusters, channels, queues, name lists, process definitions, and authentication
information objects.

60) Are the MQSC attributes are Case sensitive?

Ans:

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.

61) What is the Different Logging Methods available?

Ans:

There are two different types available:

1. Circular: The circular logging is used for restart recovery. It is the default logging method.
Circular is used in Development and Testing Queues. Circular logging keeps all restart Data in a
ring of log files. Logging fills the first file in the ring, then moves on to the and so on, until all the
files are full. It then goes back to the first file in the ring and starts This continues 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 Sequence of files. (COMPANY)
Space is not reused, so you can always retrieve any record logged from the time that the queue
manager was created. As disk space is finite, you might 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 necessary.

62) What is Channel initiators 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 triggering criteria for that queue, a message is sent to the initiation queue,
triggering the channel initiator to start the

appropriate sender channel. You can also start-server channels in this way if you specified the
connection name of the partner in the channel definition. This means that channels can be
started automatically, based upon messages arriving on the appropriate transmission queue.

You need a channel listener program to start receiving (responder) MCAs. Responder MCAs are
started in response to a startup request from the caller MCA; the channel listener detects
incoming network requests and starts the associated channel.
IBM WMQ Sample Resumes! Download & Edit, Get Noticed by Top Employers!

DOWNLOAD

63) What is triggering and what are the components?

Ans:

WebSphere MQ can start an application automatically when certain conditions on a queue are
met. For example, you might want to start an application when the maximum number of
messages on a queue reaches a specified number.

This facility is called triggering

There are two ways of triggering:

a. Application triggering

b. Channel Triggering

a) In the case of application triggering the components is Application queue: This is the
message queue associated with an application Process: A process definition defines the
application to be used to process messages from the application queue. Initiation queue: The
queue manager monitors the application queue. If the trigger type of the application queue is
set to Every then whenever a message is put to the application queue, the q manager looks into
the process definition and puts a message having the application name and other details to the
initiation queue Trigger monitor: The trigger monitor gets the trigger message from the
initiation queue and starts the program specified.

b) For channel triggering the transmission, queue is monitored and when messages are put in
the transmission queue, the q manager puts a message in the channel initiation queue. The
channel initiator is the program which monitors the initiation queue and starts the sender MCA.
For the message to reach the target queue, the channel listener has to be running in the target
queue manager

64) In IBM WebSphere MQ, how you will define a message?

Ans:

A message is basically considered as a string of bytes which contains something useful for the
machine or for the user. Generally, messages are deployed when it comes to the sharing of
information among different nodes. It doesn’t matter whether the application runs on
platforms which are different from each other.

65) What is the difference between the control commands and the MQS commands?

Ans:

Control commands are used when it comes to managing the services, as well as different
processes related to messaging. Most of the time, these commands are deployed for the
channel listener, triggering or for the integration of the same. On the other side, the MQS
commands are useful when it comes to functions which are related to the tasks performed by
an administrator. It is also possible to create Queue Managers and channels through these
commands

66) What is Message Channel agent (MCA)?

Ans:

A message channel agent (MCA) is a program that controls the sending and receiving 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 communication 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 initiated the communication; otherwise, it is
called a responder MCA.

67) How can U make the existing Queue Manager as a default Queue Manager?

Ans:

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.

68) What is the dead letter queue in IBM MQ Series?

Ans:

Dead letter Queue in WebSphere MQ is a queue which is used by QueueManager to archive

messages for a nonexistent queue.
For an example of QueueManagerQMGR, receives a message for queue ABC and if it didn’t exist
on that QueueMangaer then the message will be routed to dead letter queue.

69) What is commit and Back Out units of work?

Ans:

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 preserve 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 Out: When a program performs a back out, WebSphere MQ restores the queue by
removing the messages that were put on the queue by that unit of work. The way in which the
program performs the commit and back out operations depends on the environment in which
the program is running.

 What is IBM WebSphere MQ?

Answer: IBM WebSphere MQ is a messaging middleware software that allows

applications to communicate with each other using message queues.

 What is a message queue?

Answer: A message queue is a data structure used to store messages in transit between

applications. The sending application writes a message to a queue and the receiving

application reads it from the same queue.

 What is a channel in IBM WebSphere MQ?

Answer: A channel is a communication link between two queue managers that allows

messages to be sent between them.

 What are the different types of channels in IBM WebSphere MQ?

Answer: The different types of channels in IBM WebSphere MQ are Sender, Receiver,

Server Connection, Cluster Sender, Cluster Receiver, Requester, and Server.

 What is a queue manager in IBM WebSphere MQ?

Answer: A queue manager is a program that manages the queue and channel objects

that make up the messaging system.

 How do you create a queue in IBM WebSphere MQ?

Answer: You can create a queue in IBM WebSphere MQ using the MQSC (MQ Script

Command) command “DEFINE QLOCAL”.

 What is a trigger message in IBM WebSphere MQ?

Answer: A trigger message is a message that causes a queue manager to perform an

action, such as starting an application or sending a message.

 What is a listener in IBM WebSphere MQ?

Answer: A listener is a program that waits for incoming connection requests from

applications and creates channels to handle those requests.

 What is a dead-letter queue in IBM WebSphere MQ?

Answer: A dead-letter queue is a queue where messages are sent when they cannot be

delivered to their intended destination.

 What is a backout queue in IBM WebSphere MQ?

Answer: A backout queue is a queue where messages are sent if they fail to be

processed correctly, allowing them to be retried.

 What is a queue depth in IBM WebSphere MQ?

Answer: Queue depth refers to the number of messages currently held in a queue.
 What is a message group in IBM WebSphere MQ?

Answer: A message group is a set of related messages that need to be processed in a

specific order.

 What is an MQ client?

Answer: An MQ client is a program that connects to a remote queue manager to send

or receive messages.

 What is an MQ server?

Answer: An MQ server is a program that runs on a machine that hosts a queue

manager and handles incoming requests from MQ clients.

 What is the difference between an MQ client and an MQ server?

Answer: An MQ client is a program that connects to an MQ server to send or receive

messages, while an MQ server hosts the queue manager and handles incoming

requests from MQ clients.

 What is the difference between a point-to-point and publish-subscribe messaging model

in IBM WebSphere MQ?

Answer: In a point-to-point model, messages are sent directly between two applications

using a queue. In a publish-subscribe model, messages are sent to a topic, and any

application that is subscribed to that topic will receive the message.

 What is the maximum size of a message in IBM WebSphere MQ?

Answer: The maximum size of a message in IBM WebSphere MQ is 100 MB.

 What is an MQ header?

Answer: An MQ header is a section of the message that contains information about the

message, such as its type, format, and size.

 What is an MQ trace?

Answer: An MQ trace is a record of the events and messages that occur in an IBM

WebSphere MQ system, which can be used for troubleshooting and performance

analysis.

