Displaying/Change the attributes of a Queue Manager

Displaying the attributes of a Queue Manager

To display the attributes of a Queue Manager (say QMA), use the DIS QMGR MQSC command:

$ runmqsc QMA

And you will see:

: dis qmgr
            1 : dis qmgr
AMQ8408: Display Queue Manager details.
  QMNAME(QMA)                                                 ACCTCONO(DISABLED)
  ACCTINT(1800)                                    ACCTMQI(OFF)
  ACCTQ(OFF)                                        ACTIVREC(MSG)
  ALTDATE(2007-06-19)                          ALTTIME(20.34.04)

MQ queue naming standards

The naming of the WebSphere MQ queues is an important part of Q replication setup. It may be that your site already has a naming standard for MQ queues, but if it does not, then here are some thoughts on the subject.

Queues are related to Q Capture and Q Apply programs, so it would be useful to have that fact reflected in the name of the queues.

Issuing commands to a Queue Manager (runmqsc)

Once we have created a Queue Manager, we will want to perform administrative tasks, such as creating queues, among others. To enable us to communicate with our Queue Manager, we use the RUNMQSC MQ command, which opens the MQSC (MQ Script Center) environment.

After entering the MQSC environment, we can issue one of the following MQSC commands: ALTER, CLEAR, DEFINE, DELETE, DISPLAY, END, PING, REFRESH, RESET, RESOLVE, RESUME, START, STOP, or SUSPEND. Each of these commands has it's own options, which are shown in the following table:

Read/Write/Load Message with MQ : Part-3

Previous posts on "WebSphere MQ"  you can find HERE.

Write Message in the Queue with MQ Stage

Read/Write/Load Message with MQ : Part-2

Post Linked :

What is MQ Stage ???

Read/Write/Load Message with MQ : Part-1

A) PUT

Read/Write/Load Message with MQ : Part-1

 Previous Post :            What is MQ Stage ???

Stage MQ: The 3 parameters are: Queue manager, User and Password.

What is MQ Stage ???

 

The WebSphere MQ stage is a passive stage that offers a message based solution to customers where messaging represents another form of source and target data. The WebSphere MQ stage lets WebSphere DataStage read from and write to WebSphere MQ message queues. You can use this stage as:

• An intermediary between applications, transforming messages as they are sent between programs
• A conduit for the transmission of legacy data to a message queue
• A message queue reader for transmission to a non-messaging target

Start/Stop/Delete a Queue Manager

Starting a Queue Manager

Before we can use a Queue Manager, we need to start it, using the STRMQM command. The command to start a Queue Manager called QMA is:

$ strmqm QMA

You should see output similar to the following on your screen:

WebSphere MQ queue manager 'QMA' starting.

2108 log records accessed on queue manager 'QMA' during the log replay phase.

Log replay for queue manager 'QMA' complete.

Transaction manager state recovered for queue manager 'QMA'.

WebSphere MQ queue manager 'QMA' started.

Create/start/stop a Queue Manager

To create a Queue Manager, our userID needs to be part of the mqm group. If we do not have the appropriate authority, then we need to ask our MQ administrator to issue this command.

The command to create a Queue Manager is CRTMQM and there are various parameters available with this command:

crtmqm [-z] [-q] [-c Text] [-d DefXmitQ] [-h MaxHandles]

[-g ApplicationGroup] [-t TrigInt]

[-u DeadQ] [-x MaxUMsgs] [-lp LogPri] [-ls LogSec]

[-lc | -ll] [-lf LogFileSize] [-ld LogPath] QMgrName

WebSphere MQ commands

In this section, we look at the WebSphere MQ commands we need to set up and administer the MQ environment. The following table lists the V6 WebSphere MQ commands:

amqccert	Check certificate chains		mqftrcvc	Receive file on client
amqmdain	WebSphere MQ services control		mqftsnd	Send file from server
amqtcert	Transfer certificates		mqftsndc	Send file from client
crtmqm	Create Queue Manager		rcdmqimg	Record media image

An introduction to MQ - Part2

Let's look at the Remote Queue defnition for CAPA.TO.APPB.SENDQ.REMOTE, shown next. On the left-hand side are the defnitions on QMA, which comprise the Remote Queue, the Transmission Queue, and the Channel defnition. The defnitions on QMB are on the right-hand side and comprise the Local Queue and the Receiver Channel.

An introduction to MQ - Part1

In a nutshell, WebSphere MQ is an assured delivery mechanism, which consists of queues managed by Queue Managers. We can put messages onto, and retrieve messages from queues, and the movement of messages between queues is facilitated by components called Channels and Transmission Queues.

There are a number of fundamental points that we need to know about WebSphere MQ:

• All objects in WebSphere MQ are case sensitive
• We cannot read messages from a Remote Queue (only from a Local Queue)
• We can only put a message onto a Local Queue (not a Remote Queue)