RE: User cleanup

["Julio Domingo" <jdomingo@xxxxxxxxxxx>]

That should be relatively simple.  The program that sets up their job could
be modified to check their having an active record in the control file it
uses then the AS400 job can be checked for its existence and activity.  If
no activity delete the control record.  If there is activity, perform the
same operations as their having multiple jobs.  You may want to change the
inactivity level the AS/400 system values to end jobs after a period of
inactivity.

Kind  Regards,
Julio R. Domingo
429 Clydebank Drive
Madison, Alabama  35758
Phone:  256-340-5084
Cell:      256-289-4544
E-mail:   jdomingo@knology.net

 -----Original Message-----
From:   midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com]
On Behalf Of Dave Snyder
Sent:   Wednesday, January 09, 2002 10:00 AM
To:     midrange-l@midrange.com
Subject:        User cleanup

That sWe have a situation where users are using client access to connect to
the AS400. Nothing new.
Sometimes the users close their client access by clicking the 'X' button
instead of logging off properly. Users are users.
Sometimes the user's p/c locks up and they must reboot before exiting the
AS400. Nothing new again.
One of the applications that we have keeps track of users signed on, and
unless they sign off properly, it causes problems for the next time they log
in - someone has to manually "reset" them within the application.
The question we are looking at is...is there a way, via an exit point
program or however, to call a program that will perform this "resetting" of
the user when the above two situations occur?
Thanks for any thoughts.
Dave

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.