Here's my 2 cents worth on the subject.

        Wouldn't it be easier to assign each user their own user logon name?

        (user0001.acct
         user0002.acct
         user0003.acct
         etc.)

        By doing this you eliminate the need to check for ip addresses and
the jobcnt function will control
        how many times a user can log on.

        If you want some users to have multiple logons and other to have
just 1 then a table could be created
        to control this.
        Yes, creating a table with several hundred entries could cause a
slowdown for logging on.

        Maybe a bytestream file would work better?  I haven't played with
this kind of file so I'm guessing
        here.

                bytestream file could look like this:
"user0001##user0002##user0003##user0004##...."
                the user name would occupy 8 bytes and could contain spaces
if the name was shorter than 8 bytes.
                the ## would be their session limitation value.

                Again a script could be written to maintain this file to
remove/add users as needed.

                To maintain this level of security you could create a
command script that would add/remove users as they join/leave your place of
business.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *