| Author |
Message
|
| oli.gendebien |
 Posted: Tue Sep 03, 2013 7:44 am Post subject: MQSeries processes names |
 |
|
Newbie
Joined: 03 Sep 2013
Posts: 3
|
Hi all,
First of all, greetings to everybody, this is my first post here.
I'm absolutely new to MQSeries and I'm trying to understand the architecture and make sense of the different processes that make up MQ. Although some of the processes names make sense, there are others that are not mnemonic at all. I was wondering if anybody knew where do the names come from.
For instance
Channel Initiator
runmqchi, run + mq + ch + i = makes sense
Logger:
amqhasmx, amq + hasmx = doesn't make sense
Thanks a lot,
Oli |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Sep 03, 2013 7:50 am Post subject: Re: MQSeries processes names |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| oli.gendebien wrote: |
| I was wondering if anybody knew where do the names come from. |
They come from a place in Hursley in the UK, where WMQ is developed.
Seriously.
If they ever had any meaning, it was probably only to IBM's internal source code repository. In your example, hasmx was probably the next available module name when the code was checked in. Two minutes later & it would have been called hasmy.
The only distinction which has any value is that anything starting "run" you can use from a command line, anything starting "amq" should be left well alone & be managed internally unless a) you're talking to IBM with a PMR open or b) you're using the emergency queue manager shut down procedure & are singing a hymm of your choice. I use "Abide With Me" every time I have to do that.
If anyone knows a hymm along the lines of "Abide With The Guy Who Set Up The Backup Strategy And Checks It's Working Periodically", please share.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| oli.gendebien |
| Posted: Tue Sep 03, 2013 7:56 am Post subject: |
|
|
Newbie
Joined: 03 Sep 2013
Posts: 3
|
@Vitor, Thanks very much
... I suspected that much but I thought I might as well ask.
Cheers,
Oli |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Sep 03, 2013 7:59 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| oli.gendebien wrote: |
| I suspected that much but I thought I might as well ask. |
Never hurts to ask.
Well sometimes round here it can lead to being spammed with links to training courses.
But even that seems to have been cheerfully resolved. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Sep 03, 2013 8:09 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
"HA" "SMX"
They usually do have meaning, somewhere.
But at a certain point, if you strip out enough letters, it stops being a unique acronym, and loses general meaning. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Sep 03, 2013 9:30 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
amqhasmx is the WMQ V7 logger process. It is the same code that used to be called amqzmuc0 in V6. amqharmx is the companion log formatter (only used if linear logging is active). The WMQ System Adminstration Guide V7.0, Chapter 11. Stopping and removing queue managers manually, has lists of process names and descriptions for Windows and Unix flavors. All log reading and writing requests go through amqhasmx. Communication with other mq processes is achieved through a set of shared memory buffers. This means that semaphores are used to control singleton access to these buffers and one of the reasons that you need to be careful which user Ids are used as MQ service Ids so that semaphore ownership does not get jumbled. Particularly important is the Primary Group membership of mqm. It's not enough on some Unix variants to simply be a member of (secondary) group mqm. mqm must be the Primary group.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Sep 03, 2013 9:48 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
IBM assigns a three-character ID to a product set. amq as the first three letters identifies WMQ for distributed platforms, CSQ identifies WMQ for z/OS.
The project team creates names of internals - sometimes whimsically, and documents functionality when it is appropriate that end-users like us have a need to know.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| oli.gendebien |
| Posted: Tue Sep 03, 2013 10:04 am Post subject: |
|
|
Newbie
Joined: 03 Sep 2013
Posts: 3
|
@bruce2359, @mqjeff Thank you for the input
@lancelotlinc Also thank you for the technical background.
Cheers,
Oli |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Sep 03, 2013 10:21 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| The WMQ System Adminstration Guide V7.0, Chapter 11. Stopping and removing queue managers manually, has lists of process names and descriptions for Windows and Unix flavors. |
And should include the words to "Abide With Me" or "Lead, Kindly Sys Admin" 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Andyh |
| Posted: Tue Sep 03, 2013 11:57 am Post subject: |
|
|
Master
Joined: 29 Jul 2010
Posts: 239
|
amqhasmx is the MQ V5 logger, and as such I'm a little surprised to see it still referenced. From MQ V6 onwards the log writer thread (formerly amqhasmx) and the log formater thread (formerly amqharmx and only needed when linear logging is configured) normally run as threads in the amqzmuc0 process, rather than as processes in themselves.
As stated earlier, amq is the three character module prefix assigned in IBM for distributed MQ. The fourth character of the name typically signifies the MQ sub component (internal). H is the sub-component identifier for the logger sub-component and hence amqh is the prefix for source files and programs in the logger sub-component.
The last character is often used to identify the platform, for example 'x' signifies a UNIX specific name, 'n' a Windows specific name, '4' and iSeries specific name.
In summary the format of distributed MQ internal names is typically
amq<sub-component><XXX><platform>, where <XXX> is typically chosen by the developer of that sub-component and usually reflects the internal function in some manner. |
|
| Back to top |
|
|
|
|
