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

One way would be to write a utility that would grant the object
authority back to the new object from the object in the archive library.
This would be done via the REFOBJ parm on the GRTOBJAUT command.  

Say you call your archive library ARCHIVELIB and the library containing
your new objects PRODLIB.  A rough outline of this utility might look
like this:
-       DSPOBJD all objects in PRODLIB to an output file.
-       Read through the file, issuing a GRTOBJAUT
OBJ(PRODLIB/<objname>) REFOBJ(ARCHIVELIB/<objname>)
-       In the case of a new object not in the archive lib, you may want
to specify a template reference object or a default authority (like
*PUBLIC *USE).

Hope this helps.

Terry Richardson
The Orvis Company, Inc.

        

        -----Original Message-----
        From:   Buck Calabro [SMTP:mcalabro@commsoft.net]
        Sent:   Thursday, June 17, 1999 12:34 PM
        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
+---