|
On Tuesday 26 August 2003 17:55, Graap, Ken wrote: > Can any of you provide reasons why it might be a good idea to restrict > the use of the WRKACTJOB command to Sys Admin and Operator users? > > I'm trying to convince our large team of programmers that WRKUSRJOB is > a better command to use... Hi Ken I was always told that it kept processes running collecting statistics, even when you F3 out of it, until you logged off or ended the command with SysRq 2. Don't know how much truth was in that, but it does appear to keep track of how long it's been since starting the command for the first time in a session. I prefer WRKUSRJOB anyway[1] Regards, Martin [1] WRKSYSACT if I'm on the hunt for very greedy jobs ;) -- martin@xxxxxxxxxx AIM/Gaim: DBG400dotNet http://www.dbg400.net /"\ DBG/400 - DataBase Generation utilities - AS/400 / iSeries Open \ / Source free test environment tools and others (file/spool/misc) X Debian GNU/Linux | ASCII Ribbon Campaign against HTML mail & news / \
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.
midrange.com
