Sybase OpenClient Middleware configuration

general discussion
1

I am hoping someone may be able to give me some guidance/advice about
configuring and upgrading our OpenClient Middleware.

We are shortly going to be gradually upgrading our users from
BusinessObjects 3.1 to 4.1. Under BusObj 3.1, we have to use the Sybase
OpenClient 10.0.4 (16-bit version) to communicate with the server.

Our server has recently been upgraded to Sybase Adaptive Server Enterprise
v. 11.5.1, and ideally, we should use Sybase OpenClient v. 11.1 with it.

However, when I tried installing OpenClient 11.1, it only has a 32-bit
version, and its installation appears to disable OpenClient 10.0.4 16-bit
version.

As we roll the conversion out to our user groups (who are attached to
various file servers, beyond our “reach”), we would like to give them a
chance to gradually rewrite their 3.1 queries to 4.1. In order to do that,
both 3.1 (and OpenClient 10.0.4) needs to coexist with the 4.1 installation.

So, it seems that we cannot upgrade to OpenClient 11.1 for the 4.1
installation. Our DBAs have not been able to help us resolve how to handle
this situation.

Has anyone out there had to deal with a similar situation? Any advice on
how to proceed?

And, if we have to stick with OpenClient 10.0.4, do you have any advice on
how to eventually upgrade to OpenClient 11.1 later? (Since the middleware
is built into the Connection information.)

Thanks for any words of wisdom,

Anita Craig
Stanford University

Listserv Archives (BOB member since 2002-06-25)

2

Hi, Debbie. I’d appreciate if you can search your archives, and see if
there were any special techniques you used to make OC10 16-bit and OC11
32-bit coexist.

I did as you suggested, and installed OC11 in a new directory. I’m on
WinNT4 workstation, and after the OC11 install, the following environment
variables were updated (i.e., all but the SYBASE environment variable had
the OC10 path, then a semicolon, then the OC11 path. The SYBASE
environment variable was changed to just the OC11 path):
Include = c:\syb10\INCLUDE;c:\syb11\INCLUDE
Lib = c:\syb10\LIB;c:\syb11\LIB
Path = …;c:\syb10\BIN;c:\syb10\DLL;c:\syb11\BIN;c:\syb11\DLL;…
But the SYBASE env var was: SYBASE=c:\syb11

With that configuration, BusObj3.1 gave me the error UNI-0010: Connection
Attempt Failed when I tried to run a query.

    a.) c:\syb10;c:\syb11
    b.) c:\syb11;c:\syb10

but only a change to c:\syb10 worked. We won’t be able to have our
users toggling environment variables - and many of them are under
Windows95, so they’d have to keep editing their AUTOEXEC.BAT, which would
not be safe for them to do.

Do you have any other suggestions for configuring Open Client for both
versions? Also, do you remember whether there were some machines that you
could NOT get to work, and what the differences in machines were?

Thanks for your help and suggestions.

Anita Craig

At 10:17 PM 3/19/99 +0000, you wrote:

Anita wrote:

… when I tried installing OpenClient 11.1, it only has a 32-bit
version, and its installation appears to disable OpenClient 10.0.4 16-bit
version.

Anita,

We also had a tough time getting OpenClient 10 and 11 to coexist on the
same client. It seemed to work on some machines and not on others. You
might try reinstalling OpenClient 10 first, then rename that directory to
something else, then install 11, and make sure that the renamed directory
for 10 is in the path before 11. Good luck.

Debbie

Pls report bounces in response to postings to BUSOB-L-Request@listserv.aol.com
Web archives (24 hrs. a day now!): listserv.aol.com/archives/busob-l.html
OR search: Mail to listserv@listserv.aol.com, ‘search a_phrase in BUSOB-L’
Unsubscribe: Mail to listserv@listserv.aol.com, ‘unsubscribe BUSOB-L’
====================================

Listserv Archives (BOB member since 2002-06-25)