× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: How to maintain security when a file is deleted?
  • From: Bob Crothers <bob@xxxxxxxxxxxxxx>
  • Date: Thu, 17 Jun 1999 14:11:32 -0000
  • Organization: Cornerstone Communications, LLC

Check out the "REFOBJ" parm of GrtObjAut  --- allows you to give 
authority to an object based on another object.

Bob

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.