| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| ESQL access to mainframe DB2 from MQSIv2.0.1 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Outdesign |
 Posted: Wed Oct 31, 2001 2:49 am Post subject: |
 |
|
Apprentice
Joined: 16 Sep 2001
Posts: 38
Location: Hampshire, UK
|
Excellent news 
|
|
| Back to top |
|
 |
| NickB |
| Posted: Thu Nov 08, 2001 6:27 am Post subject: |
|
|
Centurion
Joined: 20 May 2001
Posts: 107
Location: Zurich Financial Services
|
OK, now for the bad news.
After successfully getting my message flow to query mainframe DB2 I now see intermittent problems with the connectivity. In fact, after running 2 messages through my msg flow the broker fails to talk to DB2 and I get CL0125E (HY010) sequence errors. it must be something to do with the way the broker uses ODBC as my connectivity from a db2 session on the AIX node itself works consistently all the time.
My configuration is:
BROKER = 2.0.1 on AIX using UDB 7.1
MAINFRAME = UDB 6.1
I've tried putting fixpack 4 onto UDB 7 on the broker node but this has made matters worse.
Do my problems disappear by moving to MQSI 2.0.2?
Can anybody help? |
|
| Back to top |
|
|
| NickB |
| Posted: Mon Nov 19, 2001 6:14 am Post subject: |
|
|
Centurion
Joined: 20 May 2001
Posts: 107
Location: Zurich Financial Services
|
....and the answer to the problem is as follows:
(1) Install fixpack 2a for UDB 7.1 on AIX
(2) Follow the instructions documented in:
http://www-1.ibm.com/servlet/support/manager?rs=71&rt=0&org=SW&doc=1042663
It appears that the fix applied in UDB 2a has not been carried forward to FP3 and FP4. Also, currently IBM do not officially support the ODBC driver referenced in step 2 above!
Given the vast number of viewings of this thread, it would appear that MQSI connectivity to mainframe DB2 is of significant interest to MQSI developers out there. Apparently IBM have set up a specialist group to look in to the whole issue of DB2 connectivity, ODBC drivers, etc.
|
|
| Back to top |
|
|
| spring |
| Posted: Thu Jan 17, 2002 12:42 am Post subject: |
|
|
Newbie
Joined: 16 Jan 2002
Posts: 2
|
We could connect from Solaris MQSI v2.0.1 hub (UDB 6.1) to DB2 on OS/390 mainframe.
We had to use the db2 client connection from Solaris box.
User id with the same name as the one used while creating broker had to be defined on the mainframe and granted sufficient previliges.
We did ran into "HY010" problem couple of times. But somehow it started working afterwards..
My gut feeling is HY010 is occuring when the message fails in some other part of the message flow and tries to rollback etc.
But once we stabilize the message flow from errors, we didnt get HY010 errors.
Could there be any other reason for getting HY010 error?
Do we have to apply any patches to our existing configuration so as to make sure in future we dont get such errors?
-- Any help is appreciated..!
|
|
| Back to top |
|
|
| GYR |
| Posted: Tue Feb 19, 2002 5:31 am Post subject: |
|
|
Acolyte
Joined: 23 Jan 2002
Posts: 72
|
| Message to Doggy, would appreciate if you could relay how you got the JDE link to work for AS400. I have to do sometrhing similar and although have got so far can not seem to get the correct link. Thanks in advance. Please use the following email address if it makes it easier to post there. a6r6s6e@yahoo.co.uk |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
