Re: Securing JobQs

["Greg Day" <gregday@xxxxxxxxxxxxxxx>]

What I did was secure the CHGJOB command (*PUBLIC EXCLUDE) so that users
couldn't move jobs around, and 'cause them to run out of sequence. The
AS400 Operators belong to a group call GRPOPS. I added GRPOPS to have *USE
authority to the CHGJOB command.

Hope this helps.




"Goodbar, Loyd (AFS-Water Valley)" <LGoodbar@afs.bwauto.com> on 02/07/99
03:32:30

Please respond to MIDRANGE-L@midrange.com

To:   "'midrange-l@midrange.com'" <midrange-l@midrange.com>
cc:    (bcc: Greg Day/SC/StarCity)
Subject:  Securing JobQs




We have several jobqs on the system. Generally, most departments use
QBATCH.
Payroll uses PAYROLL, and there are a few special purpose queues.

The problem is that payroll gets impatient, and they move jobs from PAYROLL
to QBATCH. So... I want to restrict payroll personnel to the PAYROLL jobq.

Are using authorization lists the best way of handling this? (IE, put an
auth list on QBATCH for all users EXCEPT payroll, then PUBLIC *EXCLUDE the
jobq) Obviously, I'd also restrict the PAYROLL jobq to payroll people, etc
etc.

Will this wreak havoc on IBM-supplied profiles?

Thanks!

--
Loyd Goodbar
Programmer/Analyst
Borg-Warner Automotive, AFS, Water Valley

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---






+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---