HP3000-L Archives

January 1995, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Dan Yates <[log in to unmask]>
Reply To:
Dan Yates <[log in to unmask]>
Date:
Tue, 3 Jan 1995 21:55:41 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (18 lines)
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.
 
thanks
 
 
Dan

ATOM RSS1 RSS2