RE: massive document storage in the IFS - how to handle Mimix

Sorry. There's a link about halfway down the page to another page that talks about unix-like file systems not having those properties.
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rzamv/rzamvifsrootfiles.htm

I see what you see in wrklnk, but I think those properties are inherited from the udfs definition or from the mounted-over link. Did you try changing them?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark S Waterbury
Sent: Monday, May 20, 2013 4:40 PM
To: Midrange Systems Technical Discussion
Subject: Re: massive document storage in the IFS - how to handle Mimix

Hi, Dan:

Where did you get the idea that QOpenSys and UDSFS "doesn't have *OBJMGT, *OBJEXIST, *OBJALTER and *OBJREF"? =-O

I just looked at the link you provided, and I don't see anything there that says THAT! :-\

Also, just issue WRKLNK '/*' and issue a "9" against any files or directories, and you can plainly see the "Exist Mgt Alter and Ref"
columns displayed, with an "X" under them,. for those users with that authority. (You might need to do this from a profile with *ALLOBJ or you might not be authorized to see that.)

Just sayin' ...

Mark

On 5/20/2013 5:12 PM, Dan Kimmel wrote:
Has anyone tried a user defined subsystem to manage the problem Joe
had with ownership? UDFS, like QOpenSys, doesn't have *OBJMGT,
*OBJEXIST, *OBJALTER, and *OBJREF, while root does. Here:
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rzamv/rzam
vplanifssec.htm

I wonder if this difference also keeps the object ownership from being added to the user profile. If so, it might also make UDFS a good place to keep millions and millions of little document files.

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