| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Single MQSeries accessing CICS on multiple LPAR's? |
« View previous topic :: View next topic » |
| Author |
Message
|
| jdveencamp |
 Posted: Mon Mar 29, 2010 8:33 am Post subject: Single MQSeries accessing CICS on multiple LPAR's? |
 |
|
Newbie
Joined: 29 Mar 2010
Posts: 2
|
MQ Experts,
We are new to MQSeries, and have our queue manager currently running on a mainframe LPAR that has some CICS's also running on that LPAR. What we are wondering, is we have some other CICS's running on a different mainframe LPAR. Do we also have to have a queue manager running on that other LPAR? Or can one queue manager communicate to CICS regions running on multiple LPAR's?
The reason for my question is licensing costs. We currently have our queue manager on a low utilization LPAR, and the WLM licensing costs for MQSeries are lower because of that. But the other LPAR with these other CICS regions is much higher CPU so would raise our MQ licensing costs dramatically.
Thanks for any info!
Jon |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Mar 29, 2010 8:43 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
AFAIK CICS can only connect to a queue manager on the same LPAR
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Domnu |
| Posted: Mon Mar 29, 2010 11:16 am Post subject: |
|
|
Newbie
Joined: 30 Nov 2009
Posts: 4
Location: Iowa, USA
|
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Mar 30, 2010 6:08 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| CICS requires that a Queue Manager be local to the instance of CICS running. |
The IBM-supplied MQ-CICS adapter thingie that runs in the CICS region does an MQCONNect to the named queue manager. MQCONNects are to local (same LPAR) queue managers.
_________________
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 |
|
|
| bruce2359 |
| Posted: Sun Apr 04, 2010 6:08 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
A possible solution for CICS instances not in the same LPAR as MQ is to do the CICS MRO thing.
Take a look at http://publib.boulder.ibm.com/infocenter/cicsts/v2r3/index.jsp?topic=/com.ibm.cics.ts23.doc/dfha1/dfha12t.htm
Select a CICS in the same LPAR as MQ that will serve as a gateway for all other CICSs that are not in the same LPAR with MQ.
Configure the cluster (not an MQ term here) of CICSs to enable messages arriving at the MQ in the same LPAR as gateway CICS to start apps (function ship) to the external CICSs (vis XCF, for example).
Get your CICS sysprog involved in this.
_________________
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 |
|
|
| jdveencamp |
| Posted: Sun Apr 04, 2010 12:31 pm Post subject: |
|
|
Newbie
Joined: 29 Mar 2010
Posts: 2
|
| Appreciate the responses guys. Thanks! |
|
| 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
|
|
|
|
