> -----Original Message-----
> From: Brian Donaldson [mailto:[log in to unmask]]
> 
> What is really needed to solve this problem once and for all 
> is Vesoft's Security/3000.
> 
> Add this line to the SECURCON.DATA.VESOFT file:
> 
> $FORBID "JSCOUNT(HPJOBNAME+',@.@&ONLINE')>1"
>    "Only one session allowed per session name!" @.@&ONLINE
[...]

Actually, "single logons" are such a common requirement that there is an explicit configuration keyword: $no-concurr-sess (though the above method allows you to configure the error message to your liking)

However, this method alone won't stop someone from multiple logons -- you would need to be using session-level security [i.e., passwords at the session level] otherwise someone could use tom,mgr.acct; tom1,mgr.acct; tom2,mgr.acct; and so on because tom <> tom1 <> tom2...

> Of course, if your shop does not have VESOFT on your box then 
> you would have to write a program or command file to do this.

To keep this post/thread from becoming a <plug>fest, I believe that practically all of the other add-on security products have a similar capability -- of course, "all of the other..." products amounts to HP's own security monitor and SAF/3000 [are there any others?]  Of course, this thread has shown that "writing your own" is certainly very doable :) :) :)
 
> However, what real HP3000 shop doesn't have VESOFT on its box? :-)

Ahhhh, music to Vlad's ears, no doubt ;)

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