HP3000-L Archives

December 1995, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Michael T. Kapsak" <[log in to unmask]>
Reply To:
Michael T. Kapsak
Date:
Tue, 5 Dec 1995 17:29:49 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
--
MCOM-HTTP-Cookie-file-1
mcom.com        TRUE    /       FALSE   946713599       NETSCAPE_VERIFY
c65ff91e,c6491ed9
We have been using the LOGOFF program for a number of years, and the
majority of our Manufacturing and Financial applications run VIEW
screens. The logoff job wakes up every 30 minutes or so to see who has
been idle for 30 minutes. It then attempts to log these users off. We do
have several user id's and programs that are excluded from the logoff
program because (1) the programs are not recognized by logoff as being
active when in fact they actually are. An example would be the IQ program
from Cognos along with several from our Financial and Manuf.
applications. At 4:00pm every day we perform a logoff of all labor
sign-ons who have logged on for the first shift. They usually leave about
3:00pm daily. We do have an occasional user who does not get aborted, why
we can't figure out right now. (testing continues).
 
Then at 11:30pm daily we run the job again to attempt to abort all
sessions except for operator and one or two more id's which will not
affect our prod. backup job.
 
It is not a foolproof program, I suspect mainly because how the HP looks
at certain processes and determines they are too critical to abort. (ie..
may cause data corruption).
 
There are several files in the DATA group which can be configured for
different sets of users, programs, time of day exclusions, etc. If you
need any more info feel free to call me (802)877-4355 or e-mail. Hope
this helps you out somewhat.

ATOM RSS1 RSS2