|
> What do you do if you have some jobs that are active, but the user has > either gone away from their terminal or is just not keying anything? It > seems that your routine to test last I/O would kill them also.. You must have missed the thread: to summarize, the application in question is a public application, run from a totally hamstrung *USRPRF, running on a series of *DEVDs that are set up to reject all other users, that is already set up (in the application and the display file) to terminate after 5 minutes of inactivity. -- JHHL
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.