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

CHGPF *does* work for removing fields or changing size.  If you are not
using the field being removed in a logical file, you get a warning message
and the field is dropped.

Jeff Young
Dynax Resources, Inc

At 12:16 PM 6/17/99 -0700, you wrote:
>We use CHGPF naming the source to add or change any fields in a file.  Does
>not work for removing fields though or making fields smaller, but we never
>do that.  CHGPF if fast and all object authorities are maintained.  File
>level ID is updated so you still have to compile.  But the file level ID
>should be the same on the customers system as on your system so you will not
>have to re-compile on the customers system if you have the recompiled
>objects in your install lib.  Have Fun.
>
>Christopher K. Bipes           mailto:ChrisB@Cross-Check.com
>Sr. Programmer/Analyst         mailto:Chris_Bipes@Yahoo.com
>CrossCheck, Inc.                       http:\\www.cross-check.com
>6119 State Farm Drive          Phone: 707 586-0551 x 1102
>Rohnert Park  CA  94928                Fax: 707 586-1884
>
>
>
>-----Original Message-----
>From: Buck Calabro [mailto:mcalabro@commsoft.net]
>Sent: Thursday, June 17, 1999 9:34 AM
>To: 'midrange-l@midrange.com'
>Subject: How to maintain security when a file is deleted?
>
>
>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
+---