Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Queue naming conventions? (Newbie)

Status
Not open for further replies.

saifnawaz

Programmer
Apr 1, 2004
8
Hi,
I am a newbie to mqseries.
I was reading through various documentaions of mqseries and have come across the Define Qlocal command.
My question is : what is the use of the Dot(.) operator while naming queues? Does it show some sort of hierarchy reference
e.g. jupiter.system.queue
Thanks
 
Yes, it sort of does. But this is not a feature of MQ as such. Naming convention is something that is designed and followed by the end-users. But in case you are following a format as above, then yes, it does signify a hierarchy. But a logical one.

Here's something for you from the manuals.

"One way of ensuring uniqueness is to prefix each queue manager name with its own unique node name. For example, if a node is called ACCOUNTS, you can name your queue manager ACCOUNTS.SATURN.QUEUE.MANAGER, where SATURN identifies a particular queue manager and QUEUE.MANAGER is an extension you can give to all queue managers. Alternatively, you can omit this, but note that ACCOUNTS.SATURN and ACCOUNTS.SATURN.QUEUE.MANAGER are different queue manager names."

Systems admin guide, Chapter 3.



Cheers
KK
 
If you have to reference the queue names and queue manager names a lot, you might want to consider keeping them descriptive but brief. This also helps avoid typoes.

SERVRNM.MAINGRP.QMGRNAM.QNAM

You can also have a description for the Queue Managers and queues if you use the Windows GUI for some of your management.

BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!
 
Just my opinion but.....

Personally I would absolutely avoid putting the Queue manager or any server name in the queue name. The reason for this is that application becomes much easier to 'transport' if you need to.

We have naming conventions that are of the format

Application.queue usage.

The only changes that need to be made then is to the connecting queue manager. This makes migration from test/development through to production much easier.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top