| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQCHLLIB |
« View previous topic :: View next topic » |
| Author |
Message
|
| starfish77 |
 Posted: Mon Dec 15, 2003 3:32 pm Post subject: MQCHLLIB |
 |
|
Apprentice
Joined: 07 Nov 2003
Posts: 31
Location: USA
|
1) What is the advantage of using MQCHLLIB over MQSERVER? (As per the doc, MQGET does not work if the message size is more than 4MB)Can some one please explain this.
2) Should we NOT use MQSERVER if the message size is larger than queue MAXMSGL and MQSeries segmentation is going to be used?
3) If I am using programatic segmentation where I can control the size of each segment, can I use MQSERVER variable to connect?
Thanks in advace.. |
|
| Back to top |
|
 |
| JasonE |
| Posted: Tue Dec 16, 2003 2:04 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
| Quote: |
| 1) What is the advantage of using MQCHLLIB over MQSERVER? (As per the doc, MQGET does not work if the message size is more than 4MB)Can some one please explain this. |
When you specify the channel you can change channel attributes (eg max message length!), add exits, have basic failover support (look at the *QM option on the MQCONN), do SSL etc. There is not much difference between a MQCONNX supplying the channel defn and the channel table though as you can do the same with both. MNQSERVER is a very small subset.
| Quote: |
| 2) Should we NOT use MQSERVER if the message size is larger than queue MAXMSGL and MQSeries segmentation is going to be used? |
| Quote: |
| 3) If I am using programatic segmentation where I can control the size of each segment, can I use MQSERVER variable to connect? |
As per above, MQSERVER uses a default client conn channel, and if it doesnt match your requirements, find a different way of doing things. |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Tue Dec 16, 2003 3:45 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
| Quote: |
| 1) What is the advantage of using MQCHLLIB over MQSERVER? |
The main advantage is flexibility:
Different client applications on the same machine (with the same environment variables) can connect to different server queue managers.
You can use groups to provide basic failover - i.e. use Q1 on QMGRB if QMGRA is down for some reason.
If you were to use MQSERVER by setting it programmatically then you might require to recompile code if an MQ admin makes a change on a server e.g. changes the port/name/ip address of the qmgr. Using a channel table, there would just need to be a definition change outwith the code.
You could still have multiple channel tables too - e.g. to isolate different users on the same machine.
Cheers,
Vicky |
|
| 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
|
|
|
|
