On Mon, 27 Aug 2001 15:22:20 -0700, Newton, Ernie <[log in to unmask]> wrote: >Greetings, > > $no-concur-sess @2.accountname > >We use that command in Vesoft to limit user logons to only one. > >In this example, all users in school district 2 are specified. > >We now have a need to allow concurrent logons for a couple of users. > >Is there a way to allow some users in @2 to have concurrent logons, while >all others are not? > >It doesn't appear as though the minus sign can be used here. yes, "subtracted-out" userset can be used and should work well. THERE IS A TRICK to it, however -- there can NOT be any embedded spaces in a "userset", so if you have: $no-concur-sess @2.acct - mgr2.acct the minus is ignored (actually, it probably generates an error). Instead use: $no-concur-sess @2.acct-mgr2.acct There IS an exception to the "no embedded spaces" rule -- usersets that continue on the next line (by virtue of an ampersand) MAY have leading spaces which are not counted. i.e., you could have the following: $no-concur-sess @2.acct& -mgr2.acct& -user2.acct All of this should be explained in the on-line help and printed manual. Another method of doing this, which may help readability, is to use "defined" usersets: $define-userset everyone @.@ $define-userset me (tom.emerson+tom,@.@+emerson,@.@) then say: $no-concur-sess !everyone-!me which would allow me to use concurrent logons for the specific user "tom.emerson", or any session of "tom" or "emerson" -- EVERYONE else would be excluded. tom * To join/leave the list, search archives, change list settings, * * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *