Re: How to maintain security when a file is deleted?

Try using the CHGPF command with the SRCFILE keyword.  This will recreate
the file using the new DDS and keep ALL the original attributes including
Authority, Journaling etc.

Jeff Young
Dynax Resources, Inc


At 12:34 PM 6/17/99 -0400, you wrote:
>When we distribute file objects out to customers, we restore the tape to an
>install library, copy the production data to an archive library with CPYF
>CRTFILE(*YES), delete the production file, CRTDUPOBJ from the install
>library to the production library and finally, CPYF the data from the
>archive back into production.
>
>If the customer has private authority assigned to the production file, it
>gets lost when we delete the file.  How can we preserve the private
>authority to these changed objects?  I looked quickly at authority holders,
>but they're for S/36 files.  Then I thought about using the QSYLUSRA API to
>retrieve the current authority before we delete the file and then GRTOBJAUT
>to re-apply the authority to the new one.
>
>Is there a better way?  How do others distribute software upgrades that
>maintain the customer's authority scheme?  How do you tell them about new
>objects that may need authority to be addressed?
>
>Buck Calabro
>Billing Concepts Albany, NY
>+---
>| 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
+---