John Dunlop wrote:
> I know there has been some discussion about this before but I have been
> unable to find answers in the Archives.
>
> Maybe someone can help.  We have a system with a user limit of 100 users
> configured. We have a problem that many users who used to have one
> session on a terminal, now have a PC and use multiple sessions (quite
> legitimately). However, we sometimes reach the limit where at 96
> sessions shown, it doesn't allow any more sessions to log on.
>
> What I would like to know :
>
>  1. I know there is a reason that only 96 instead of 100 sessions can be
> logged on but I forget why.

Do a showdev and look for DTC ldevs that are 'hot' printers or other data
capture devices that are FOPENED by a job or session. IMHO this is a bug but
no one seems to care.

>  2. How can I tell which users haven't used their terminals for , say 8
> hours, although they have left them on?
>
>  3. Is there anything in the Contributed Library etc that anyone can
> recommend?

Many sites use Bouncer to logoff idle sessions.

>  5. How can you tell which users have been logged on for over a week?
>
One would have to examine the system log files to find the prior logon in
the console log record or the job initiation record for that session number.
This can best be done with CONSLOG or CLUE3000. CLUE3000 is available at
Beechglen.Com in the freeware section.

Cordially,

Mike Hornsby
Co-founder/Chief Technical Officer
Beechglen Development Inc. (Beechglen.Com)
513-922-0509
[log in to unmask]