Re: IFS object ownership -- MIDRANGE-L

× 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.

Hi, James:

In computer science, "More sins are committed in the name of compatibility..."

The IFS has always worked this way. Remember, the code for the "integrated file system" was ported directly from AIX. OS/400 concepts like OWNER(*GRPPRF) have no bearing on the IFS in the "root", QOpenSys or user-defined file systems.

You could also read the AIX documentation in the AIX InfoCenter, here:

http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp

All the best,

Mark S. Waterbury

> On 10/12/2010 4:56 PM, James H. H. Lampert wrote:

We have a problem with disappearing IFS objects on customer systems.
We've had it for some time, and I'm convinced that the biggest single
cause of it is that owning user profiles are being deleted with
OWNOBJOPT(*DLT), by system administrators who don't know any better.

Short of changing every user profile enrolled in the application to
OWNER(*GRPPRF), is there a simple way to arrange things so that the IFS
objects are created under (for example) QUSER? Or failing that, to
programmatically change their owners on creation?

I don't see anything like this in the "UNIX-type APIs" manual, but I
might be looking in the wrong place.

--
JHHL

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.