RE: IFS object ownership

Sorry, Chris, but would you mind expounding on this:

The user profile owned the object
even though it was set for group ownership.

Specifically what does it mean to have a file set for group ownership? And
how did you set this? I suspect a misconception and I'd like to help.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"It is a paradox that every dictator has climbed to power on the ladder of
free speech. Immediately on attaining power each dictator has suppressed
all free speech except his own."
-- Herbert Hoover

This is a big depends! I have been struggling with the same issues
here. Depending on how the IFS objects are created the owner is set.
And at V5R3, have not checked at V5R4, Group Profile Ownership was
ignored in the IFS. Again when created with tools from the iSeries
such
as copying a DB to a stream file. The user profile owned the object
even though it was set for group ownership.

Wish you luck.

--
Chris Bipes
Director of Information Services
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H.
Lampert
Sent: Tuesday, October 12, 2010 1:56 PM
To: Midrange Systems Technical Discussion
Subject: IFS object ownership

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.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.