RE: Programmer DFU access

John Earl wrote:

>I put together something similar once, and discovered a big problem with
it.  The
>spool file can always be manipulated/changed/deleted by the person who
reated it
>(even if it's in an outq they have *EXCLUDE authority to :(  ).

>Our solution was to have an automatic SNDNETSPLF ship the spool file to
another
>system, into an outq that was *PUBLIC *EXCLUDE.  The new spool file ended
up
>being owned by  the owner of the SNDNETSPLF job, so it was slightly more
secure.



You can also attach a data queue to the output queue. Any time a spool file
is added to the output queue an entry is added to the data queue. You then
have a program running in the background which processes the spool file,
adding it to a log file or whatever.

Albert York


+---
| 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
+---