| Author |
Message
|
| jamesgeorgem |
 Posted: Fri Feb 12, 2010 8:46 am Post subject: Datastorage of MQSeries |
 |
|
Newbie
Joined: 07 Feb 2010
Posts: 7
|
Hi Friends,
I am very new to MQSeries.
and wishes to know one thing
1. If I put a message a in a que manager where is this message stored internally.
is data is stored in the Random Access Memory or to database/text file
Maybe a stupid question?but wishes to know that information.
Hope somebody can help me.
Thanks in advance
JG |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Feb 12, 2010 8:48 am Post subject: Re: Datastorage of MQSeries |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jamesgeorgem wrote: |
| is data is stored in the Random Access Memory or to database/text file |
Depending on message type & platform it could be either RAM or disc or both.
Though the disc storage is neither database nor text but a proprietary format owned by IBM.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Feb 12, 2010 8:52 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
1. If I put a message a in a que manager where is this message stored internally.
is data is stored in the Random Access Memory or to database/text file
Maybe a stupid question?but wishes to know that information. |
Not a stupid question at all.
Briefly, and with much technical detail omitted:
A message put to a queue (not queue manager) is briefly stored in a buffer in RAM, but written to disk subsequently.
Ideally, the application that needs to consume the message is waiting (MQGET with WAIT) to consume the message; and will consume the message directly from the buffer. If the message is not immediately consumed from the buffer, it will be written to disk.
Messages stored on disk are not stored in a database. Rather, they are stored in a proprietary format, down the filesystem (midrange platforms), or in a dataset (z/OS).
_________________
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 |
|
|
| jamesgeorgem |
| Posted: Fri Feb 12, 2010 1:19 pm Post subject: |
|
|
Newbie
Joined: 07 Feb 2010
Posts: 7
|
Hi Bruce/Grand,
Thanks for the clarification. so MQSeries have an entirely different architecture...great..
I appreciate all your inputs....
Thanks and Regards,
JG |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Feb 12, 2010 1:33 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Your original post only asked about message storage, with you pondering if WMQ used a database for this purpose.
To add to your understanding of WMQ: WMQ queue managers log significant events (persistent messages, creation/alteration of objects, transactions and so on); and this logging is accomplished with the same logging infrastructure used for logging in DB2.
_________________
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 |
|
|
| jamesgeorgem |
| Posted: Sat Feb 13, 2010 9:48 am Post subject: |
|
|
Newbie
Joined: 07 Feb 2010
Posts: 7
|
| bruce2359 wrote: |
Your original post only asked about message storage, with you pondering if WMQ used a database for this purpose.
To add to your understanding of WMQ: WMQ queue managers log significant events (persistent messages, creation/alteration of objects, transactions and so on); and this logging is accomplished with the same logging infrastructure used for logging in DB2. |
Thanks Bruce for the additional information. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Sun Feb 14, 2010 4:09 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| bruce2359 wrote: |
| To add to your understanding of WMQ: WMQ queue managers log significant events (persistent messages, creation/alteration of objects, transactions and so on); and this logging is accomplished with the same logging infrastructure used for logging in DB2. |
MQ uses some of the same methodologies for recovery logging as DB2, but not the same code, and DB2 is not a prerequisite for MQ in this regard.
_________________
Glenn |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Feb 14, 2010 5:03 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
OK. Not the same code.
How about this: those with DB2 experience will recognize DB2 utilities and behaviors are remarkably similar to those of WMQ.
On z/OS for example, the bootstrap and other log-related utilities are named alike - with the exception of the first three characters - the module prefix - (see MVS Diagnosis Reference). DSNJU003 (change log inventory) is CSQJU003; DSNJU004 (print log map) is CSQJU004.
Additionally, what WMQ logs is dramatically different from WMQ.
_________________
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 |
|
|
| Vitor |
| Posted: Sun Feb 14, 2010 5:26 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bruce2359 wrote: |
| Additionally, what WMQ logs is dramatically different from WMQ. |
Erm..... 
 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
