Re: Protection for spool files?

[Jeff Carey <jeffreycarey@xxxxxxx>]

John Earl wrote:
> 
> Spool file authority is fairly non-intuitive, and certainly doesn't use the
> same rules as other OS/400 objects.
> 

That's because spool files are not objects at all, but made up of
records in physical files in library QSPL.  If you think of it that way,
then it makes a little more sense - you can't grant authority to one
record and not another.  

While this may seem cumbersome, think of how much better the AS/400
handles spooled output than other systems.  Try reprinting a report
starting at page 153 in Unix (is there a product that can do this?  I
know a few years ago my former company couldn't find one - and it
certainly isn't part of the OS!)  

Spooled "files" are considered "output," like text sent to a screen.  As
such, the spooling capability of OS/400 gives a lot of control over
something that's basically assumed to be printed and kept as hard copy. 
In fact it's probably because of the AS/400's superior spooling that
people keep those spool files out there so long anyway!
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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
+---