As nobody has replied I guess everybody has got this working fine. We are trying to get DB2 connect wroking now with Bo version 5.1.6 in preparation for the move to Version 6 /Xi 2. I’ll let you know our experiences.
George - just in case you get back to this …
I’m curious as to what kind of DB2 Connect you are using. We have been using what was called Enterprise Edition because Personal (or Runtime) Edition did not work with DB2 OS/390 ( which I guess is the z series now). Our latest version number is version 5 fixpak 8
Our reason for moving is the dropping of support for NEON Shadow by BO after 5.1.7. My next question may seem rather odd but is their a way of defining a new Repository Connection that points at an existing repository? I didn’t really want to have to set up a new Security domain etc. But the Supervisor tool seems to be forcing me that way. :?
so you can’t do a safe recovery? I forget the details right now but wouldn’t that allow you to define a new connection to the same old repo?
too bad about NEON - I have used that before when IBM got antsy about our quasi-legal license. Thankfully the regional data center stepped up with a site license but getting the right versions (DB2 Connect) installed has always been troublesome.
Hey Chris - What is this please? Is this something similar to DB2 Connect? I get so confused with all the product names over the last 8 years
The organisation I work for needs to upgrade to Db2 V8 because of other issues, and the Businessobjects problem is just a side issue
The situation is that our development Mainframe has already been migrated to V8 compatibility mode. the good news is that we can still use BO version 5.1.6 with NEON SHAdow 3.5 and 3.6 DLLs and version 5 of the mainframe end. The bad news is tht we can no longer create or update our secured connections (modifying the DSN) (and probably shared and personal as well but we don’t use those) the connectdata table in the repository will not accept the inserts from supervisor or designer. The Shadow logging reports that the data passed is too big for a varchar(254) column…
Our next step is to create a repository with DB2/Connect and see iif that works, if not tyhen we may be looking at moving our repository to SQL server a little earlier than planned.
It still leaves us with the problem of defining Data connections using Connect or NEON, but we will face that when we come to it…
We’re using BO 5.1.4, our repository is still on Oracle but we built a few universes on z/OS DB2 v8 This seemed to be working fine but now we can no longer modify the universes to add columns. BO can’t access the catalog to get column definitions. Queries still run OK.
This is the error. Our Tech person opened a PMR with IBM but I was just wondering if anyone has seen this.
IBM][CLI Driver][DB2] SQL0443N Routine “SQLCOLUMNS” (specific name “SQLCOLUMNS”) has returned an error SQLSTATE with diagnostic text “SQLCODE=-805 DQ01.DSNASPCC.DSNACOL8.176B27D21992”. SQLSTATE=38112
I totally agree with having some kind of BO - DB2 forum. We are actually implementing Crystal Enterprise v10 and then will merge that with our existing BO environment in XI r2. I’ve mapped out an upgrade strategy which also includes moving the data from Oracle to DB2 and the converting our ETL code to Ascential.
The creation/updating of connections in the repository was a bug in either DB2 or Shadow, which got fixed along the way.
We have BO 4.1.4 and BO 5.1.6 running against db2 for Z-os Version 8 compatibility mode, since Monday 11 July No problems with BO yet. but not 8) or yet
I would be interested in hearing your experience going forward. Please let me know if you run in to any problems. Feel free to use my email if you want to contact me directly.
Nope It’s 4.1.4… Don’t ask but we have not been able to deploy 5.1.6 because of insufficient server power for a full client infoview deployment and are now in the process of building new servers to deploy 6.5.2 when it eventually crawls out of the development labs with support for Db2 for Z-os version 8
Oh yes and we are running it on windows XP desktops as well.
Yes the repository is on db2 V8 it has got there through version 6 and 7 of db2 for the BO 4 repository.
We have had a V5 repository working on the development mainframe for at least 3 months but only in compatibility mode, again via version 7 pf DB2.
we will be going to SQL server for the V6 repository, because Xi won’t be supporting db2 (Z/os) as a repository host but there again there’s no BCA either. Just the Crystal equivalents, and hopefully a lot friendlier…
Now where is 6.5.2 and my proof of db2 connect, oh yes and the server farm to run it on…
[quote:a165cbb214=“G.E.Davies”]The bad news is tht we can no longer create or update our secured connections (modifying the DSN) (and probably shared and personal as well but we don’t use those) the connectdata table in the repository will not accept the inserts from supervisor or designer. The Shadow logging reports that the data passed is too big for a varchar(254) column…
[/quote]
We had this resolved, unfortunately I don’t know which product fix pack fixed this issue, but now we can edit our secured connections through shadow and db2 v8 compatibility mode.
OK. So now we have 6.5.2 and a BO consultant coming to install and configure our servers. We have DB2 connect enterprise edition V8.2 running on the V5 server. 8)
However we are having problems getting the client connection, for 5.1.6, working via DB2 connect.
Our DBAs are trying to use the LITE client to connect to the server and on to Db2 but it doesn’t seem to work.
Scott can you confirm?
You have to put the full DB2 connect enterprise edition product on the client desktops to make it work:?:
Oh and one further comment on this. We have 4.1.4 and 5.1.6 running successfully “live” on db2 V8 COMPATIBILITY MODE, and Neon SHADOW, with no real problems, apart from having to have a different “plan”, because we also have db2 V7 running on the same mainframe (different partitions).
W’ve succesfully tested 5.1.3 met z/OS DB2 V8 Compat Mode, but can’t find any documentation if this 5.1.3. version is also working in the last phase of V8 and this is NewFunction Mode.
Did you in meantime already some testing with BusObj in a NewFunctionMode DB2 V8 subsystem?