|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Message reading |
« View previous topic :: View next topic » |
Author |
Message
|
babu_murugesan |
Posted: Wed Nov 22, 2006 8:56 am Post subject: Message reading |
|
|
Novice
Joined: 11 Nov 2006 Posts: 19
|
Assume;
Up to 2000 concurrent users to be supported.
MQ listener program written in COBOL, started by CICS when message arrives in an initiation queue.
Message reading
Our current messaging system via APPC on LU6.2 receives the message in chunks dynamically allocating memory to store it as required.
It looks as if with MQ we read the entire message at once. This means that we will have to statically allocate the maximum possible amount of memory required for a message in our MQ listener program. (The MQ listener is triggered from the initiation queue for every new message).
This means that every CICS transaction will have lots of potentially redundant memory allocated for it, for the duration of the MQ listener transaction.
At what sort of maximum message size would this become a problem ?
One possible way around this would be to have different types of message written to different request queues and inquire on the queue before we read the message to get the maximum message length for that queue. Memory would then be allocated dynamically for that maximum size.
Is this a viable solution ?
Alternatively, if we read a message then discover it is too long for our receiving variable, we could allocate more memory then try and read it again. Is there any guarantee that we can re-read the same message ? Can it be ‘locked’ to prevent another process reading it (without performance implications?)
Thanks,
Babu M |
|
Back to top |
|
 |
Vitor |
Posted: Wed Nov 22, 2006 9:25 am Post subject: Re: Message reading |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
babu_murugesan wrote: |
At what sort of maximum message size would this become a problem ? |
Depends on how much resource you can squeeze into CICS. By the sound of it you're already loading it quite heavily.
babu_murugesan wrote: |
One possible way around this would be to have different types of message written to different request queues and inquire on the queue before we read the message to get the maximum message length for that queue. Memory would then be allocated dynamically for that maximum size.
Is this a viable solution ?
|
If you can afford the CPU cost of multiple reads, along with the RACF checks and everything else you're doing
babu_murugesan wrote: |
Alternatively, if we read a message then discover it is too long for our receiving variable, we could allocate more memory then try and read it again. Is there any guarantee that we can re-read the same message ? Can it be ‘locked’ to prevent another process reading it (without performance implications?)
|
You can do a GET_MSG_UNDER_CURSOR (which may be spelt slightly differently - look it up before use). Cursors in MQ (like in databases) cost a lot of CPU. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|