|
This did not work. I made the change and than asked one of the other developers to try to get in and he did. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Turnidge, Dave Sent: Friday, August 25, 2006 7:30 AM To: Midrange Systems Technical Discussion Subject: RE: lock Job Schedule Entries Don't mess with QSYS. Change *PUBLIC to *EXCLUDE. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dwayne Allison Sent: Friday, August 25, 2006 7:29 AM To: Midrange Systems Technical Discussion Subject: RE: lock Job Schedule Entries So, do we change the QSYS & *PUBLIC? If so what do we change it to? Object User Group Authority QSYS *ALL SMITHC *ALL WILSONC *ALL WILLIAMC *ALL *PUBLIC *USE -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ketzes, Larry Sent: Friday, August 25, 2006 7:06 AM To: Midrange Systems Technical Discussion Subject: RE: lock Job Schedule Entries You could always lock down the: Wrkjobscde Addjobscde Chgjobscde Commands to *public *exclude, and then grant access to whomever. Larry ====================== Larry Ketzes iSeries Senior System Administrator American Life Insurance Company One ALICO Plaza 600 King Street Wilmington, DE 19801 Phone: 302-594-2146 Mobile: 302-559-1631 Fax: 302-830-4524 Email: larry.ketzes@xxxxxxx -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dwayne Allison Sent: Friday, August 25, 2006 8:02 AM To: Midrange Systems Technical Discussion Subject: lock Job Schedule Entries Good Morning, We are in the middle of an audit and the auditors are requesting that the Job Schedule Entries only allow noted users. Is this possible and if so how? -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.