Our queues are named after what it is - we describe the contents of the
queue... because a queue does not "do" anything.
John Scott
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
.CO.UK> cc:
Sent by: MQSeries Subject: Transaction Names
List
<[EMAIL PROTECTED]
N.AC.AT>
06/22/2004 01:29
AM
Please respond to
MQSeries List
I have already posted this question on mqseries.net, but I wondered if I
would get some more responses on the list server...
I am not looking for ideas on general MQSeries naming standards, I already
have those and there are enough examples in the archives to keep anybody
happy.
Our queue naming standard is basically APP_NAME.TRANSACTION_NAME.
Where APP_NAME is the name of the application that is allowed access to the
queue. We use alias/remote queue definitions to wire up
MYAPP.TRANSACTION_NAME -> YOURAPP.TRANSACTION_NAME
I am now looking in detail at the TRANSACTION_NAME. When I look at the
queues we have I see a mixture of TRANSACTION_NAME styles - some of them
are
named after what the message content is (i.e. ORDER_AMENDMENT) and others
are named after what the applications (typically the receiving application)
does with the data (i.e. UPDATE_ORDER).
Thus we would have a queue called:
MYAPP.ORDER_AMENDMENT
or
MYAPP.UPDATE_ORDER
I wanted to canvas whether people preferred the "what it is" over "what it
does" or vica-versa.
Which style do you use and why?
Regards
John Scott
IBM Certified Specialist - MQSeries
Argos Ltd.
**************************************************************
Click here to visit the Argos home page http://www.argos.co.uk
The information contained in this message or any of its attachments may be
privileged and/or confidential, and is intended exclusively for the
addressee. Unauthorised disclosure, copying or distribution of the contents
is strictly prohibited.
The views expressed may not be official policy, but the personal views of
the originator.
If you have received this message in error, please advise the sender by
using the reply facility in your e-mail software.
All messages sent and received by Argos Ltd are monitored for viruses,
high-risk file extensions, and inappropriate content.
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
