We are SOFT users, but use our own procedure.  BackPack or Roadrunner
customers can use XLOGOFF.  I experimented with it a bit, and it works as
advertised.
 
Our routine is called KILL
 
LQ ALL
SERVER HPAUTOCONT TRUE
SETVAR LOCKON CHR(27) + "l"
SETVAR LOCKOFF CHR(27) + "m"
SETVAR HOMEUP  CHR(27) + "H" + CHR(27) + "J"
SETVAR HOMEUP  CHR(27) + "H" + CHR(27) + "J"
ECHO **************************************************
ECHO *** THIS COMMAND FILE WILL KILL ALL SESSIONS   ***
ECHO ***   EXCEPT FOR LOGONS TO "OPERATOR",         ***
ECHO ***   "VESOFT" AND "SYS"                       ***
ECHO **************************************************
ECHO !LOCKON
IF FINFO ("KILLFILE.PUB.OPERATOR","EXISTS") THEN
   PURGE KILLFILE.PUB.OPERATOR
ENDIF
IF FINFO ("KILLCMD.PUB.OPERATOR","EXISTS") THEN
   PURGE KILLCMD.PUB.OPERATOR
ENDIF
BUILD KILLFILE.PUB.OPERATOR;REC=-80,1,F,ASCII
FILE KILLFILE=KILLFILE.PUB.OPERATOR,OLD
SHOWJOB JOB=@S;*KILLFILE
RUN QEDIT.PUB.ROBELLE;INFO="USE KILLUSE.PUB.OPERATOR";PARM=4
ECHO !HOMEUP
ECHO !LOCKOFF
PRINT KILLCMD.PUB.OPERATOR;PAGE=0
INPUT YESNO; PROMPT="***  ABORT THESE SESSIONS (Y/N)? "
IF UPS(YESNO)="Y" THEN
    XEQ KILLCMD.PUB.OPERATOR
    ECHO
    ECHO SESSIONS BEING ABORTED.  PLEASE WAIT A MINUTE FOR A REPORT
    ECHO
    PAUSE 60
    COMMENT
    COMMENT Added 07/12/90 to show users logged on after the
    COMMENT ABORTJOB has completed to alert operators to ghost
    COMMENT sessions.
    COMMENT
    FILE NEWPASS=$NEWPASS
    SHOWJOB [log in to unmask];*NEWPASS
    IF FINFO ("$OLDPASS","EOF") > 3 THEN
        ECHO  THERE ARE STILL SOME USERS LOGGED ONTO LIST20
    ELSE
        ECHO LIST20 ACCOUNT IS CLEAR
    ENDIF
    SHOWJOB [log in to unmask];*NEWPASS
    IF FINFO ("$OLDPASS","EOF") > 3 THEN
        ECHO  THERE ARE STILL SOME USERS LOGGED ONTO LISTQA
    ELSE
        ECHO LISTQA ACCOUNT IS CLEAR
    ENDIF
    SHOWJOB [log in to unmask];*NEWPASS
    IF FINFO ("$OLDPASS","EOF") > 3 THEN
        ECHO  THERE ARE STILL SOME USERS LOGGED ONTO LISTTEST
    ELSE
        ECHO LISTTEST ACCOUNT IS CLEAR
    ENDIF
    SHOWJOB [log in to unmask];*NEWPASS
    IF FINFO ("$OLDPASS","EOF") > 3 THEN
        ECHO  THERE ARE STILL SOME USERS LOGGED ONTO PROGDEV
    ELSE
        ECHO PROGDEV ACCOUNT IS CLEAR
    ENDIF
    SHOWJOB [log in to unmask];*NEWPASS
    IF FINFO ("$OLDPASS","EOF") > 3 THEN
        ECHO  THERE ARE STILL SOME USERS LOGGED ONTO TELMARK
    ELSE
        ECHO TELMARK ACCOUNT IS CLEAR
    ENDIF
ELSE
    ECHO ***  SESSIONS NOT ABORTED
ENDIF
DELETEVAR LOCKON
DELETEVAR LOCKOFF
DELETEVAR HOMEUP
DELETEVAR YESNO
PURGE KILLFILE.PUB.OPERATOR
PURGE KILLCMD.PUB.OPERATOR
SETVAR HPAUTOCONT FALSE
 ----------
>From: owner-hp3000-l%UTCVM.UTC.EDU
>To: Multiple recipients of list HP3000-L
>Subject: Re: VESOFT software
>Date: Monday, December 04, 1995 3:16PM
>
>---------------------- Information from the mail header
>-----------------------
>Sender:       HP-3000 Systems Discussion <[log in to unmask]>
>Poster:       Charles Leader <[log in to unmask]>
>Organization: NETCOM On-line Communication Services (408 261-4700 guest)
>Subject:      Re: VESOFT software
>---------------------------------------------------------------------------
 ----
>-
>
>Cynthia Bridges-Fowler ([log in to unmask]) wrote:
>:  In [log in to unmask]>  writes:
>
>: I sent the following message to another list I'm on but have had little
>: response from that group of users. I suspect the users on that list are
>: not familiar with the many features of VESOFT other than basic security
>: and maybe the menus. The majority of my users never see the colon
>: prompt (unless a job blows up!) because we use VESOFT menus heavily.
>: I'm posting my earlier message here to solicit your sage advice and
>: input! TIA!
>
>: > We have used the LOGOFF function of VESOFT's software numerous times in
>: > the past when we are preparing to do maintenance. We generally do this
>: > maintenance at the end of the day on a Friday (after 5pm) and use
>: > LOGOFF to abort sessions on machines that have been left idle for 10+
>: > minutes. Once all users are logged off, we then proceed to make the
>: > system unavailable to users for the duration of the maintenance,
whether
>: > for installation of software, system upgrades, or whatever.
>: >
>
>For this part, I'd recommend using the ABORTJOB command inside of MPEX.
>You can say something along the lines of:
>%ABORTJOB ONLINE-LDEV=20 This will take everyone off the system except
>for the console. ONLINE does not touch batch jobs, or you can say:
>%ABORTJOB @-LDEV=20
>
>Anyway, have a look at the help for the command, you will probably find
>this a lot easier than configuring LOGOFF to achieve the same thing.
>
>Charles Leader
>Former VESOFT System Manager and Technical Support
>[log in to unmask]
>