5 replies to this topic

[Lewis Mccabe]

FYI: You cannot use UMSG to notify users of a timeout if you also set the timeout during the display of the UMSG - Client hangs.

Here is the setup:
We set the timeout (@TIMEOUT) and had @TFUNCT function display a message to the user that their screen had timed out. We kept @TIMEOUT set so if the user never dismissed the UMSG we would log them out so they weren't taking up a PRO-IV seat. When the system tried to log off after timing out from the UMSG, the PRO-IV client would hang. Changing the user notification from UMSG to a global message function works - the session is logged out cleanly.

Lew

[Mike Schoen]

Lewis,

Have you by any chance found a way to automaticly time-out the users without requiring a key-press from the client session?
We've had this requested of us in the past, but have not found a way to do it.


Mike

[Lewis Mccabe]

Mike,

We do this via a check of @PFUNCT.

We set @TFUNCT to RTIMEOUT. The first time through we pop a global message window to notify user that screen has timed out. To automatically log out: We keep the same @TFUNCT. If user times out from the 1st iteration of RTIMEOUT the logic is this:
IF @PFUNCT = @FUNCT THEN
// We have already timed out. This is the second call of this timeout function.
// Exit application
@TIMEOUT = 0
@TFUNCT = ''
@LFUNCT = 'RLOGOFF'
FNEXIT
ENDIF

RLOGOFF is simply a housekeeping function which ultimately sets @LFUNCT=OFF.

HTH

Lew

[Joseph Bove]

Mike,

Have you by any chance found a way to automaticly time-out the users without requiring a key-press from the client session?

I know there was a persistent issue on several of the 4.6 and early 5.5 kernel (especially on Linux) where this was an issue. You would actually time out until you pressed a key. (Which really made timing out for license control useless.)

If this is your issue, an upgrade of your kernel may solve you.

hth,

Joseph

[Mike Schoen]

Thanks Joseph, I will have to give that a try.

We've mostly had this requested from users who got tired of staff locking a record, then going for a wander somewhere, leaving a record lock behind.

[Neil Hunter]

We're using timeout on 5.5r411, no messages or anything, but it does not require any user interference.

Another possible route is a timer control running on the client machines ...