Different Types Queues in Websphere MQ There are four types of queue object available in WebSphere MQ.

Each type of object can bemanipulated by the product commands and is associated with real queues in different ways. 1.Local queue object A local queue object identifies a local queue belon in to the queue mana er to which theapplication is connected. All queues are local queues in the sense that each queue belon s to aqueue mana er and! for that queue mana er! the queue is a local queue. 2.A remote queue object A remote queue object identifies a queue belon in to another queue mana er. This queuemust be defined as a local queue to that queue mana er. The information you specify whenyou define a remote queue object allows the local queue mana er to find the remote queuemana er! so that any messa es destined for the remote queue o to the correct queuemana er."efore applications can send messa es to a queue on another queue mana er! you must havedefined a transmission queue and channels between the queue mana ers!unless you have rouped one or more queue mana ers to ether into a cluster . #or more information aboutclusters! seeWebSphere MQ Queue Mana er $lusters 3.An alias queue object An alias queue allows applications to access a queue by referrin to it indirectly in MQ% calls.When an alias queue name is used in an MQ% call! the name is resolved to the name of eithera local or a remote queue at run time. This allows you to chan e the queues that applicationsuse without chan in the application in any way. &ou just chan e the alias queue definition toreflect 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. .A mo!el queue object A model queue defines a set of queue attributes that are used as a template for creatin adynamic queue. 'ynamic queues are created by the queue mana er when an applicationissues an MQ()E* request specifyin a queue name that is the name of a model queue. Thedynamic queue that is created in this way is a local queue whose attributes are ta+en from themodel queue definition. The dynamic queue name can be specified by the application or thequeue mana er can enerate the name and return it to the application.'ynamic queues defined in this way are either temporary queues! which do not surviveproduct restarts! or permanent queues! which do. Specific local queue types and their uses WebSphere MQ uses some local queues for specific purposes related to its operation. These are, a" Application queues This is a queue that is used by an application throu h the MQ%. %t can be a local queue on thequeue mana er to which an application is lin+ed! or it can be a remote queue that is owned byanother queue mana er. Applications can put messa es on local or remote queues. -owever! they can only etmessa es from a local queue. b" #nitiation queues %nitiation queues are queues that are used in tri erin . A queue mana er puts a tri ermessa e on an initiation queue when a tri er event occurs. A tri er event is a lo icalcombination of conditions that is detected by a queue mana er. #or e.ample! a tri er eventmi ht be enerated

when the number of messa es on a queue reaches a predefined depth.This event causes the queue mana er to put a tri er messa e on a specified initiation queue.This tri er messa e is retrieved by a tri er monitor! a special application that monitors aninitiation queue. The tri er monitor then starts up the application pro ram that was specifiedin the tri er messa e.%f a queue mana er is to use tri erin ! at least one initiation queue must be defined for that queue mana er. c" Transmission queues Transmission queues are queues that temporarily stores messa es that are destined for aremote queue mana er. &ou must define at least one transmission queue for each remotequeue mana er to which the local queue mana er is to send messa es directly. These queuesare also used in remote administration. !" $luster transmission queues Each queue mana er within a cluster has a cluster transmission queue calledS&STEM.$/0STE1.T1A*SM%T.Q0E0E. A definition of this queue is created by default on everyqueue mana er on WebSphere MQ for A%2314! iSeries! -)502! Solaris! and Windows314 .A queue mana er that is part of the cluster can send messa es on the cluster transmissionqueue to any other queue mana er that is in the same cluster.$luster queue mana ers can communicate with queue mana ers that are not part of thecluster. To do this! the queue mana er must define channels and a transmission queue to theother queue mana er in the same way as in a traditional distributed5queuin environment. e" Dea!%letter queues A dead5letter queue is a queue that stores messa es that cannot be routed to their correctdestinations. This occurs when! for e.ample! the destination queue is full. The supplied dead5letter queue is called S&STEM.'EA'./ETTE1.Q0E0E. These queues are sometimes referred toas undelivered5messa e queues.A dead5letter queue is defined by default when each queue mana er is created. -owever! you must ensure that the queue mana er on which this queue resides points to the dead5letterqueue that it is oin to use.The followin command creates an undelivered5messa e queue on queue mana erneptune.queue.mana er, $1TMQM MQM*AME3neptune.queue.mana er4 0'/MS6Q3A*(T-E1'/Q4 f" $omman! queues The command queue! named S&STEM.A'M%*.$(MMA*'.Q0E0E! is a local queue to whichsuitably authori7ed applications can send WebSphere MQ commands for processin . Thesecommands are then retrieved by a WebSphere MQ component called the command server.The command server validates the commands! passes the valid ones on for processin by thequeue mana er! and returns any responses to the appropriate reply5to queue.A command queue is created automatically for each queue mana er when that queuemana er is created. &" 'eply%to queues When an application sends a request messa e! the application that receives the messa e cansend bac+ a reply messa e to the sendin application. This messa e is put on a queue! calleda reply5to queue! which is normally a local queue to the sendin application. The name of thereply5to queue is specified by the sendin application as part of the messa e descriptor. h" ()ent queues WebSphere MQ for iSeries supports instrumentation events! which can be used to monitorqueue mana ers independently of MQ% applications. %nstrumentation events can be eneratedin several ways! for e.ample,

An application attemptin to put a messa e on a queue that is not available or doesnot e.ist. A queue becomin full. A channel bein started. When an instrumentation event occurs! the queue mana er puts an event messa e on anevent queue. This messa e can then be read by a monitorin application! which informs anadministrator or initiate some remedial action if the event indicates a problem. *ote, Tri er events are quite different from instrumentation events in that tri by the same conditions! and do not enerate event messa es. er events arenot caused