In a message dated 10/24/99 4:10:23 PM Pacific Daylight Time, email@example.com writes: << If you have OWNER(*GRPPRF), you will not know who really created the object. Who created the object and who owns the object are two seperate things. If you use DSPOBJD you can see who created it, even if its owned by the group profile. Instead, use GRPAUT(*ALL), which means when somebody creates an object, it will still be owned by them, but everybody in the group will have full authority to it. >> I disagree. Individuals should not own objects. Only the group profile should. If individuals own an object, it makes it difficult to restore to other machines. Also, it the individual leaves, it's more of a pain to delete his profile when he owns objects. IMHO Ron Hawkins +--- | 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: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.