Path: utzoo!attcan!uunet!husc6!mailrus!tut.cis.ohio-state.edu!osu-cis!att!ttrdc!levy
From: levy@ttrdc.UUCP (Daniel R. Levy)
Newsgroups: comp.os.vms
Subject: Re: Multi-terminal service and license key
Message-ID: <2665@ttrdc.UUCP>
Date: 16 May 88 22:58:02 GMT
References: <880512061915.20807ca9@LBL.Gov>
Organization: AT&T, Skokie, IL
Lines: 55

In article <880512061915.20807ca9@LBL.Gov>, nagy%warner.hepnet@LBL.GOV (Frank J. Nagy, VAX Wizard & Guru) writes:
# >      1) Will the six slave terminals be counted as a single user
# >         if under the control of the master program?
# 
# The slave terminals do NOT count as separate users.  They are just
# I/O devices in use by a program.  If the program is running from
# a batch job or is a detached process, then even that program does
# not count as an interactive user.
#      
# The N-user license only counts against "interactive users".  An
# interactive user is one who has LOGGED IN via:
# 
# 	- SET HOST
# 
# 	- a terminal multiplexor line
# 
# 	- a LAT connection
# 
# 	- (only on a VAXStation) the main display screen
# 
# Network jobs (like file accesses), batch jobs, subprocesses and
# detached processes are NOT counted against the license limit.
# = Frank J. Nagy   "VAX Guru & Wizard"

But what about:

	- a batch process which does a $SPAWN /IN=terminal: /OUT=terminal:

		???

We use a variation on that here to implement a quick-and-dirty callback 
facility (a batch job on the VAX allocates the terminal, calls the user [on
an outward-dial-only line], then SPAWNs DCL to the terminal).  Of course we
have a full VMS license; we aren't trying to cheat nor do we suggest that
anyone else should (cheat).  An F$MODE() invoked from that session returns
"INTERACTIVE" (no surprise?!).  So I presume that it might be impossible
anyhow to cheat on the interactive limit using that method, as the system
seems to believe the session to be interactive, though it doesn't show up
on a SHOW USERS.

If there is any PD or shareware callback software out there I'd like to hear
about it, incidentally.  SPAWN is crufty, slow, and doesn't offer password
protection.  Though the user who submitted the callback job, of course, had
to first log in the usual way, he supplied the phone number, and the line
used to call out can't be dialed in on.  So I am presuming the HACKER risk to
be small short of someone tampering with the phone or terminal lines, or
an authorized user giving a wrong number that calls a waiting HACKER.  (Any
HACKERs or WIZARDs out there who can think of anything I've forgotten please
reply, preferably NOT by deleting all my files... :-).
VMS mail if you bust in... :-).
-- 
|------------Dan Levy------------|  Path: ihnp4,<most AT&T machines>!ttrdc!levy
|              AT&T              |  Weinberg's Principle:  An expert is a
|       Data Systems Group       |  person who avoids the small errors while
|--------Skokie, Illinois--------|  sweeping on to the grand fallacy.