| Author |
Message
|
| zpat |
 Posted: Fri Feb 03, 2006 1:52 am Post subject: J2EE and CICS |
 |
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I am not a Java expert, but have been asked whether Websphere MQ provides support for connecting PCs to z/OS CICS applications using J2EE?
I can't offhand think of any CICS J2EE connector which uses MQ - anyone got any ideas? |
|
| Back to top |
|
 |
| mvic |
| Posted: Fri Feb 03, 2006 2:28 am Post subject: Re: J2EE and CICS |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| zpat wrote: |
| connecting PCs to z/OS CICS applications using J2EE? |
What does this mean, exactly? How does one connect a PC to a CICS application - either with or without J2EE ? Sorry for my ignorance - I do MQ, not CICS. |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Feb 03, 2006 2:47 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
CICS transaction gateway for example.
The CKTI IBM MQ/CICS bridge
These I know about - this question requires MQ and CICS knowledge to answer (otherwise I wouldn't need to ask!).
Last edited by zpat on Fri Feb 03, 2006 3:11 am; edited 1 time in total |
|
| Back to top |
|
|
| wschutz |
| Posted: Fri Feb 03, 2006 3:00 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
So, does using JMS to send messages to the CICS bridge count?
_________________
-wayne |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Feb 03, 2006 3:11 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| Possibly, if JMS can supply the MQCICS headers. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Feb 03, 2006 3:32 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| zpat wrote: |
| Possibly, if JMS can supply the MQCICS headers. |
We talk to CICS without the bridge using JMS.
Our mainframe setup is to have the queues triggered and an initq and trigger monitor is running in CICS for each CICS region. We set the property targetClient=1 (JMSC.TargetClient_NONJMS_MQ from memory) either on the queue (cast to MQQueue) or in JNDI.
We use only TextMessages so no hex or packed numbers allowed. Works like a charm.
Sometimes we set the CCSID property on the JNDI entry for the queue.
(500) means we don't have to translate on the channel and the message gets to the MF in EBCDIC.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
