| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ ->IMS via OTMA |
« View previous topic :: View next topic » |
| Author |
Message
|
| vradhik |
 Posted: Wed Apr 01, 2009 12:51 am Post subject: MQ ->IMS via OTMA |
 |
|
Novice
Joined: 08 Nov 2008
Posts: 10
|
We have a mainframes appliation on z/OS 1.10 and IMS v9.1. This application is now going to interface with a web application on AIX to receive some financial data as MQ messages and this will invoke IMS transactions via OTMA on the mainframes end.
We had initially planned to use the IMS Adapter with trigger monitor, which would invoke the IMS transaction to get and process the messages. But due to certain constraints. we would want to opt for the alternate way which is the IMS Bridge mechanism.
The message sizes can vary between 1KB to 10MB with 80% of them lying between 10KB-1MB. Since IMS queues were mentioned to be designed to handle small messages (32K limit) and we will be receiving around 10 messages/sec during peak hours in production.
Is segmentation the only way? Or is there any other way? What do we need to change in our current environment now to handle this?
The requirement is to have a near-realtime response from the mainframe application to the web application. We are sending back status messages using MQ from mainframe application to the web app. thanks! |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Mon Apr 06, 2009 8:17 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| Is segmentation the only way? |
Message segmentation is the supported and documented (WMQ APG, WMQ APR, WMQ System Setup,...) way.
| Quote: |
| ...we will be receiving around 10 messages/sec during peak hours in production |
.
IMS should be able to handle this with ease.
_________________
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 |
|
|
| Sam Uppu |
| Posted: Mon Apr 06, 2009 10:05 am Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
If the QMgr is running on z/OS, MQ segmentation is not supported on z/OS.
Check this link
Thanks. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Apr 06, 2009 12:34 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| If the QMgr is running on z/OS... |
More accurately, if the application is running on z/OS...
Refer to the WMQ APG "How the IMS bridge deals with messages" section, Message segmentation. I've copied a snipped here.
You can define IMS transactions as expecting single- or multi-segment input. The originating WebSphere MQ application must construct the user input following the MQIIH structure as one or more LLZZ-data segments. All segments of an IMS message must be contained in a single WebSphere MQ message sent with a single MQPUT.
_________________
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 |
|
|
| vradhik |
| Posted: Tue Apr 21, 2009 4:56 am Post subject: |
|
|
Novice
Joined: 08 Nov 2008
Posts: 10
|
Thanks for the replies, we decided to go for IMS trigger approach for small messages (<32K) and for batch trigger approach for messages > 32K.  |
|
| 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
|
|
|
|
