Re: Securing Spool Files

[email@xxxxxxxxxxxxxxxxxxx (James W Kilgore)]

Gerald,

In reading John's learned response, I recalled a seminar where the
speaker started out by stating that people generally will not accept a
simple solution, so he hoped he could make his topic sufficiently
complex that it would be received well.

I'll give it a try:

Don't spool checks. End of problem.

Too short? <g>

John Earl wrote:
> 
> Gerald,
> 
> 
> More than likely it's Special Authorities that are giving your operator the
> rights to see the payroll spool files.   If your operator has *SPLCTL special
> authority, they will always be able to see every spool file on the system.
> *SPLCTL is is to spool files as *ALLOBJ is to objects.   If the operator has
> *SPLCTL, you will have to remove it in order to secure your payroll outq's.
> 
> If the Operator has *JOBCTL special authority, you can secure the spool files 
>by
> putting them in an OUTQ created with the OPRCTL(*NO) and specifying regular
> OS/400 authority (*PUBLIC *EXCLUDE) for the OUTQ object.
> 
> Depending on how the output queue is used, you may want to also specify the
> DSPDTA(*NO) and AUTCHK(*OWNER) parameters as well.  Press the F1 key to see 
>what
> those parameters will do for your security.
> 
> hth,
> 
> jte
>
+---
| 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
+---