1. Home
  2. Manager Controls
  3. Manager Controls: System Monitor

Manager Controls: System Monitor

System Monitor

System Monitor

This window shows current user and document status and in real time identifies user activity in creating documents, transactions and when they log on or off. It is designed for system manager administration.

You can set the Refresh Rate and, if needs be view the logged-in users passwords. Because of this, only trusted users should have access to this window.

Note NOTE: Data will only be refreshed when this window is in front of all others.

Note NOTE: V5.10 changed the way the user-limit was recognised and the operation of this window changed significantly.

Button

Action

View Passwords

Click to redraw the list showing passwords. This will only last until the next refresh. This is only enabled if your user id is listed in the optMonitorShowPassUsers system option.

File Path Status

This button opens the File Path Status window which looks and all active and potential folder and file connections for the program.

View User Session Log

This opens the User Logon Sessions window so a system manager can see User Logn and Logoff information.

Sound

If checked, the system bell will sound after each refresh.

No Token Refresh

Normally your user token is refreshed with it’s expiry extended each time the window refresh takes place, ensuring that you stay active indefinitely. If you check this checkbox, your token is not refreshed and it will ultimately go into an idle state. This can be useful for testing.

Test For Only One User

Check to perform a server test each refresh to check whether you are the only workstation attached to the datafile.

Note NOTE: This is not the same as seeing a single user listed in the user list. The current user list is the contents of the User Token table. A token is awarded to a user when they logon to the database, removed when they logoff and regularly updated as the user works in the program. It has an expiry of initially 15 minutes. If the expiry is passed the user is considered idle. This test views the tokens on the server to establish if you are the only active (non-idle) user. If this test gets a positive result, it is normally the case that a single-user operation can be performed.

Current User List

The Current User List shown at the bottom right will contain all current user tokens that have been granted and their status. Users are identified by their User ID and a unique number. The latter is needed in case two users logon using the same User ID, which, while not recommended, is permitted. When a user logon is performed, that session is granted a token. When the user logoff is performed (when there is a clean exit) the token is removed.

However, the token has a lease-life typically of 15 minutes. During normal user activity in the program this is regularly refreshed with the lease-life extended automatically. However, if a user becomes inactive and the lease-life is passed, the token and user are considered idle.

An idle user becoming active again can re-activate that token, unless in doing so would exceed the licensed user limit, or a single-user session is waiting or in progress.

If, on a user logon, the user finds ALL tokens are idle then all tokens are deleted, before the logon user is granted a new token. In this way rogue user entries, where no clean logoff was performed, can be cleaned out of the system. (Note: When this happens a comment is placed on the User Session Log.)

For an extreme example, say you were running with 12 users on a 12-user license and the entire factory power fails for a minute or so with all user computers affected. Immediately you will not be able to logon as you would be the 13th user. If you waif for over 15 minutes before logging on however, all the rogue tokens will be removed. For a deeper explanation of the multi-user control mechanism see the IntroSQL Introduction to Client-Server SQL help.

There are a number of options that effect this system:

Name

Privileges

Description

optSessionIdleMaxMins

Sy

Maximum session idle time in minutes before forcing a logoff. Minimum orf 5, maximum 720, default 240.

optSessionLogMaxDays

Sy

The maximum age in days of USLFILE table rows are automatically deleted. Minimum 10, maximum 365, default 90.

optSingleUserDelaySecs

S, Sy, U

Single-user other user delay logout in seconds. Minimum 60, maximum 600, default 180.

See also: –

Compiled in Program Version 5.10. Help data last modified 19 Jun 2016 08:26:00.00. Class wMonitor last modified 10 Oct 2017 11:48:24.

Updated on May 27, 2020

Was this article helpful?

Related Articles

Leave a Comment