The other day I happened to do a LISTUSER on one of my development
     logons and was a bit surprised to see a LOGON CNT of -87.  After
     logging off the counter was correctly decremented to the not so
     correct value -88.  A subsequent logon incremented the LOGON CNT back
     to -87.  Since I don't make much use of the LOGON CNT I thought
     'That's strange' and went on to other things until I tried to do a
     :PURGEUSER and received the message
     'In use.  Can't be purged. (CIERR 916)'
     presumably because the LOGON CNT was not 0.
 
     After a little bit of experimentation, I was able to reproduce a
     negative LOGON CNT with:
 
     :mpex
     MPEX/3000  25N50210  (c) VESOFT Inc, 1980  5.0  05:00246
     %listuser sam
     ... LOGON CNT : 1
     %chlogon mgr.test
     Error: You are not configured in the user database.
     Error: CHLOGON failed.
     %listuser sam
     ... LOGON CNT : 2
     %god.pub.vesoft
     %listuser sam
     ... LOGON CNT : 0
     %mortal.pub.vesoft
     %listuser sam
     ... LOGON CNT : -2
     %exit
     END OF PROGRAM
     :listuser sam
     ... LOGON CNT : -3
 
     We are also using VESOFT's Security/3000 with LOGON, HELLO & LOGOFF
     enabled under MPE/iX 5.0.  Further experimentation has also shown that
     there are other conditions in which %chlogon incorrectly modifies the
     LOGON CNT.
 
     Any thoughts on :PURGEUSER under these conditions?