> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of Mark Bixby
> Sent: Tuesday, July 06, 1999 1:06 PM
> To: [log in to unmask]
> Subject: Re: user license
>
>
> John Zoltak writes:
> >
> > Mark Bixby writes:
> > > The HPRC was probably hinting at using a batch job to spawn a
> > > server process for
> > > each additional user, and fork() or CREATEPROCESS() would be
> > > a way to do that.
> > > The server process would open the user's terminal LDEV
> > > directly instead of
> > > the user doing :HELLO.
> > >
> > > Once upon a time, our student registration system worked this
> > > way.  I'm
> > > simplifying greatly here, but we had a batch job listener
> > > process.  The end
> > > users would :HELLO over DTC serial lines and run a logon UDC
> > > that would notify
> > > the batch listener and then log the user off.
> > >
> > > The batch listener would then spawn a new terminal handler
> > > process and would
> > > open the user's terminal LDEV directly.
> > >
> > > The user would now be "logged on", but without any colon
> > > prompt, and without
> > > counting against the user license.
> >
> > Mark,
> >
> > This is not true. When you open a terminal LDEV for input/output, this
> > will count against the user license. This is by design and documented
> > somewhere. The only way that I know of to get around the user license
> > issue it to use a PC client and sockets to do the communication.
>
> <BLUSH>
>
> I stand corrected; I did warn everybody that I have an unlimited license
> machine, so I've never had to be too concerned about this problem.  :-)
>
> The architectural point is still valid, and as John points out, could
> be implemented via sockets (as simple as telnetting to a specific
> port, or as
> complicated as full-blown client-server).  A POSIX socket
> listener could just
> fork() new server processes in response to incoming TCP connections.
> --
> Mark Bixby                      E-mail: [log in to unmask]
> Coast Community College Dist.   Web: http://www.cccd.edu/~markb/
> District Information Services   1370 Adams Ave, Costa Mesa, CA,
> USA 92626-5429
> Technical Support               Voice: +1 714 438-4647
> "So long and thanks for all the fish!"

Using sockets is doable, however, let's not forget security.  If
you don't care about security, you can do a quick and dirty implemetation
that has each terminal emulator nailed to a preassisgned tcp port
with a dedicated listner sitting there serving as the menu program
for your application.  However, the simple solution requires no
user authentication.

Let's say that the program that lets you in, handles the socket
communication,
on the HP 3000 runs in PM. This just might open the old pandora's box to the
system.  If the computer is even indirectly exposed to the Internet lookout.

It is still possible to do the login's without cost, however, someone
concerned about security should use a master program that authenticates
the users and then with some control, assigns tcp ports.

Charles Finley
Transformix Computer Corporation
(310) 630-1773
(310) 630-1770