I hope this question makes sense because I am not a UNIX server person (that person is on vacation). I called IBI and they suggested I put the question out on the forum to ensure we're ok. We are currently on webfocus 5.3.3 and UNIX is our reporting server. Our data resides on the mainframe. The mainframe upgraded to DB2connect version 9 last night (in test .. this is not a production problem yet) so we are getting the following error:

(FOC1400) SQLCODE IS -1434 (HEX: FFFFFA66)
: [S1000] [IBM][CLI Driver] SQL1434N A CONNECT or ATTACH statement failed
: because of a client/server incompatibility between 32 bit and 64 bit pl
: atforms.

We believe we just need to upgrade our db2 connect on the UNIX box to version 8 (which is compatible with version 9 on the mainframe).

One thing IBI said was we need to be running in 32 bit mode in 533 ... well the error above indicates we need to be 64 bit processing. Does anyone have 533 using db2 connect version 8 in 64 bit processing? Does it work fine? Is there anything else beside upgrading the db2 connect version that we need to do?

One more note ... we have one application still on version 5.2.1 ... does anyone have db2 connect version 8 and 5.2.1 working?

Thanks.

I don't know if it will help at all, but this chart summarizes compatibility for WF 5.3.4. (charts for other versions are available as well):
Supported Systems and Adapters Information

It looks like DB2 7.2 and DB2 8.1 are compatible with WF 5.3.*

We are running DB2 8.1 on an AIX box. We use it to talk to both mid-tier and mainframe DB2 connections.

We are running 5.3.3 in production (till Oct. 27) and 7.6.2 in dev.

Our WebFOCUS software is the 32 bit on 64 bit version for AIX. I don't know about Solaris in this case.

What I would suggest is that you talk to your DBAs and/or your sys admins and show them the error you are getting. One of the first things that you want to do is have one of them do a successful connection from your WF reporting server platform using only DB2 tools. If that fails, your problem in not in WebFOCUS.

If that test is successful, you might want to do a passthru request through edastart -t with traceon. I think the syntax is

edastart -t -traceon

You must be logged onto the Unix box to do this. If you running WF with security on, you should have an id on that box. If not, does your WF Unix server sys admin have a backup? You need that person to go to your /dirname/ibi/srv53/wfs/bin directory where dirname is whereever the root directory of the installation is. You can also do this from the server admin id if you can log in as that.

Do you have access to the WebFOCUS console as an admin? You can also go to Procedures and do a passthru request from there.

These are starting points. Let me know what you find out from these steps. You must check standalone access to DB2 before you get WebFOCUS involved.

Thanks for all the info. Standalone is definitely working. I can pull any data from the mainframe using advanced query tool or my desktop. That was my first check this morning. Webfocus running on our windows platforn (desktops) in db2 connect version 8 is also working. We have definitely narrowed it down to our Unix server and we know that is not on db2 version 8. Since the mainframe converted last night to version 9, it has been stated that we need to be on db2 connect version 8 or newer. Db2 7 is not 64 bit.

As for doing anything on the UNIX console ... our person that knows how to do that stuff is on vacation. Never fails

We don't think our problem is necessarily webfocus, it's the db2 connect version on the UNIX server. I was checking on compatability with the versions in my post and the fact that we now need to be 64 bit processing according to the mainframe support area.

Francis, thanks for that document. We look good for 533, but 521 is not looking good (I found that document based on your document ... I now knew what to look for).

Time for a WebFocus upgrade?

you won't see much advantage over ODBC by using the db2 connect.

our IBI representative said "well, db2 connect is a call-level interface, so it has advantages over the ODBC driver. we don't support the ODBC driver." So I called IBM and they told me to send him this.

http://www-03.ibm.com/servers/eserver/iseries/db2/clifaq.htm#header_2

I printed it and posted it on the wall of my office so our IBM rep can't keep trying to sell us the DB2 enterprise edition for $100,000.

Jason K.

I heard DB2 Connect is only something like 70$ per server.
Is enterprise edition really 100K$ ???

Because if it is, we will reconsider our plans.

Thanks