All that is required is setting the SYBASE variable and appending to the PATH
statement the location of the DLLs. The path to the BIN is helpful for running
Open Client utilities from the Command prompt, but it is not required. In our
implementation we actually opted to put the DLLs in the BIN directory and
append the BIN directory (instead of the DLL directory) to the PATH statement.
The environment setting for the LIB and INCLUDE directories are required for
Open Client development. There are a couple of important things to remember
before implementing this option. First, its not supported by Sybase. Second,
you have to make sure all Open Client files are removed from all the PCs in
question (I wrote a utility that removed all Open Client files, registry
setting, and environment variables from all PCs via the Novell container
script.) Third, you have to write the login script to first take a snapshot of
the PC environment (PATH, INCLUDE, LIB, SYBASE) and save them as other
variables (OLDPATH, OLDINC, etc.) You will need these setting for when a user
logs out and back in. If you don't reset the environment variables to their
old values in the beginning of the script, then you will keep appending on top
of the variables with the Sybase setting over and over again.
Other things to note about this deployment:
1) Works with NT, Win95, and even Win31/DOS
2) Our script is written to allow user to switch between environments
(versions) by using a login variable.
3) We run our scripts from the system container one up from the user
container. This allows us an easy way to manage the number of users running
off a given file server. At our main offices we have ~800 users each running
against 3 servers. If it wasn't for politics, we could probably run all 2400
users on one or two servers.
4) Including regional offices, we have 11 separate servers housing the same
Open Client setup. DBA has a utility that generates the SQL.INI file from a
list of Sybase servers and pushes it to each Open Client server (including each
version.) Currently we are running 207 Sybase servers that are all tracked by
this setup with no issues.
I probably can't provide you with the complete script (intellectual property
rights and other garbage like that), but I'm open to any questions you may
Daniel J. Mock
> > We have a Powerbuild application using Sybase as the backend. Instead of
> > installing it on each individual PC, we installed OpenClient on the
> > server (Netware). The user's login script sets up the variables required
> > and points to the network directory. This make it easy when we switched
> > IP address. I only needed to change once and everyone was fixed.
> Can you tell us what was required in the Netware login script?
> What about the registry entries?