I asked:
[snip]
> >  1. I know there is a reason that only 96 instead of 100 sessions can be
> > logged on but I forget why.

Mike Hornsby replied:

> 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.

I did that but no "hot" devices showed up.

I asked:

> >  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?

Mike replied:

> Many sites use Bouncer to logoff idle sessions.

I was thinking that there might be a way to actually determine when the
last IO occurred for a session.

I asked :

> >  5. How can you tell which users have been logged on for over a week?

Mike replied :

> 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.

That is one way but Ed Stouder gave me more what I was after.

Thanks  for your help , Mike.


--
Cheers,

John Dunlop

** Please note the new e-mail address **

E-mail : [log in to unmask]       "If at first you don't succeed...
Web : http://www.hp3000links.com       Don't take up sky-diving !"
"All your HP3000 resources on the Net"