| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Communication with multiple CICS |
« View previous topic :: View next topic » |
| Author |
Message
|
| daspot |
 Posted: Tue Mar 07, 2006 3:35 am Post subject: Communication with multiple CICS |
 |
|
Newbie
Joined: 03 Jan 2006
Posts: 8
|
I wish to sollicitate your experience as a user on a problem which seems trivial but that is nevertheless structuring.
In an MVS environment, on one partition- no PLEX, we have recently multiplicate (from 2 to 20) the number of CICSs.
With only two CICS the management of the applications was easy with dedicated queues. But today, while duplicating CICSs we also have duplicate applications.
The outgoing messages are still managed the same way. But (here is the problem), the incoming messages don't recognize which CICSs they have to correspond to because they only know one alias (one manager).
What is the best way to indicate to an outgoing request that it will have to reply in the CICS who has pushed this request ?
We can see few possibilities:
To clone the managers - expensive solution,
To clone the number of queues – a lot of alias and queue,
To deal with the messages ID - probably not very powerful,
... there surely is more possibilities.
This type of structure surely already exists on other sites. I wish to know if it is possible to give me advices on which strategy you have (or would) adopt to answer to this problematic.
Thank you in advance for the information you may provide me. |
|
| Back to top |
|
 |
| wschutz |
| Posted: Tue Mar 07, 2006 3:45 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
If I understand your problem correctly, you have 20 CICS regions that are running the same transactions, and these transaction are generating messages that go somewhere else. That "somewhere else" replies to those messages and you want those replies to be probessed by transactions in the same CICS region that created the original request message. Is that it?
If so, are these transactions waiting for the replies or would it be other transactions that handle the replies?
_________________
-wayne |
|
| Back to top |
|
|
| daspot |
| Posted: Tue Mar 07, 2006 10:44 am Post subject: |
|
|
Newbie
Joined: 03 Jan 2006
Posts: 8
|
hello,
you have fully explained the situation.
to complete my request and answer : The transactions which send the messages are not waiting for the replies.
As you say, other transactions handle the replies.
We work in asynchronous mode. |
|
| Back to top |
|
|
| wschutz |
| Posted: Tue Mar 07, 2006 12:21 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
a common solution would be to define 20 "reply to queues" (normal local q's), and call them something like: REPLY.CICSREGA, where "CICSREGA" is the cics region name.
When an application puts a message to "somewhere else", it puts the name of the replytoQ in the message descriptor. Assuming your "somewhere else" application does the right thing, it will send the answer to the right replytoQ. Then, the application in each region opens the appropiate replytoQ and gets the messages intended for that region. 
_________________
-wayne |
|
| 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
|
|
|
|
