Item Subject: Message text
> I have just installed HP's odbc allbase/sql and image/sql drivers to
> access our ALLBASE/SQL database that resides on a HP3000 957 from a
> process running on a PC. Everything seems to work as expected.  When a
> process uses ODBC to connect to the database the 3000 spawns a job for
> each process that requires access.  If I have 64 users then there must
> be 64 jobs running.  Is there a process or some way to configure the
> system so that only 1 job can satisfy needs of all users.
>
> I understand that each of these jobs replaces a session but to have the
> job limit set at 64 seems a bit much.  Is there anyone who knows how
> this process works that can explain it in more detail.
> It would be much appreciated.
 
Dan,
 
With Allbase G0 you will only have the one job, and that will spawn processes
underneath it for each connection.
 
BTW, make sure you get the latest release which address the process decay
problem.
 
/isaac