|
Depends on your need. I can't see how a user (or anybody) can live without WRKUSRJOB (or WRKSBMJOB) and WRKSPLF (all with USER(*CURRENT) as primary selection). WRKACTJOB is for something different use - it might help the advanced user understand why his job isn't running. Henrik > date: Tue, 26 Aug 2003 09:55:55 -0700 > from: "Graap, Ken" <keg@xxxxxxxxxxxxx> > subject: WRKACTJOB > > 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... > > Kenneth
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.