Hi,
you can use 
Logoff The LOGOFF utility can be used to logoff another process. Root privileges are required to logoff another process logged on with a different user id.

LOGOFF {port | startport-endport}

Roland,

This isn't exactly what you're asking for, but if this is UniVerse, you can add AUTOLOGOUT nn (where nn is minutes) to your UV.LOGIN paragraph.  Then if that number of minutes passes without a keystroke being passed to UniVerse, the user is logged out.

You've probably already looked at that, but just in case ...

On Universe we have Auto.Logoff (or is it Auto.Logout?) 
At any rate you can add a time of inactivity long enough that no one should be idle for say 6 hours or whatever
You can add that to the login voc so it applies to all users

HI Roland,
Does you system have the AUTOLOGOUT command. you can set that in your login process, then the system will monitor and log out any user that is idle for the number of minutes you set AUTOLOGOUT at.

Would setting the autologout in your login procedure help?

AUTOLOGOUT {number of minutes}

I think a mass logout would require some coding.

Karl

We use AUTOLOGOUT to auto logoff users after x minutes of inactivity.
We put this in the LOGIN VOC
you need to make sure you bypass any special logins. this is part of our LOGIN VOC
IF @TTY = 'phantom' THEN GO ENDLOGIN
AUTOLOGOUT 150
MAIN
ENDLOGIN:

The auto logout seems the best otion.
For end of day precedures, you can have a different login which bypasses it.

The other option is to have the following (in pseudo code) : 
request account to log all users off (may be hard coded)
get current port number (so you don't log off yourself)
get other ports not to log off   (exempt list. probably not required if part of end of day procedure)
get max port number  (be careful not to log off the spooler. may be hard coded)
start loop incrementing ports from 0 or 1
  if logged in
    if required account
       if not current port or in exempt list then logoff port
  end multiple if
end loop & get next port

Regards,
Warwick

LOGOFF {port | startport-endport}

you can also MASTER OFF a user session as an Administrator.

We run through a series of steps to try and prevent corruption of the databases...

1.  Use TANDEM to take control of the session, then log the user off (as if it was them logging off...)
2.  Use MASTER OFF to try try and get the user off

3.  We are running on a Unix platform, so the last option is to kill the PID as an administrator
     first, ps -ef | grep pidno
this shows details of anythng related to the PID
then try kill -signal PID
we try multiple times with differing signal codes trying elimate sessions the "nicest" way possible...
signal code sequence..:
15, 13, 1, 3, 5, 7, 9
with the ps -ef check after each kill command to see if the session has gone

If you have been granted access with a privileged credential, why don't you use the OS tools. It's usually simple to script and schedule these for automation.

eg to logout all fred's uv/linux sessions from sh: sudo pkill -term -u fred uvsh 
For Windows Powershell, look at Stop-Process

You could set up a scheduled job (win scheduler or *nix cron) to call a logout script before the backup (or whatever the use-case is).

Hi Roland,

While all the suggestions put forward are great, do not use any of them. Your system is running on ULTRACS and user must log out via the application, if not your security and user files will get clogged up and will need to be manually cleaned, or logging a Support Call. I believe ULTRACS provides a timeout setting, review the Admin Manual.

HTH.

Does the application provide access to the logging-out function? At that point, you could incorporate that functionality in the ON.ABORT paragraph. Presumably, logging out would only fire the ON.EXIT paragraph if it exists. 

If the security and user files pose a problem for abort exits, perhaps it would be useful for reducing support calls that address this issue.