|
Thanks for the input, Rob.
The core problem is creating millions of objects in the IFS, and we're
going to resolve that here by using database files to store the CLOB
data. AUTLs are a great tool, but I still have a problem with IFS
objects: the owner. Let's say I create a folder authorized by an AUTL.
If I then create a file in that folder, not only is the object assigned
that AUTL, but the system also makes an entry of my user profile with
*EXCLUDE, so you see this:
Object . . . . . . . . . . . . : /autltest/TestMe.txt
Type . . . . . . . . . . . . . : STMF
Owner . . . . . . . . . . . . : TAUTL1
Primary group . . . . . . . . : *NONE
Authorization list . . . . . . : AUTLTEST
Type options, press Enter.
1=Add user 2=Change user authority 4=Remove user
Data --Object Authorities--
Opt User Authority Exist Mgt Alter Ref
*PUBLIC *RWX X X X X
TAUTL1 *EXCLUDE
Does the *EXCLUDE add an entry to the TAUTL1 user profile? I don't know
but my guess would be yes. And I think the ownership does. So once
again the moral of the story is that millions of IFS files is just bad.
And thus my focus on moving IFS files to CLOB columns except when
impractical.
Joe
+1 on the PRTPRFINT, did you just miss the very recent thread on whyhave
someone's SAVSECDTA was running so long?
+1 on recommending authorization lists.
Here's an example I know you can grasp. Let's say you have a test Infor
library for company 1. You have all the objects owned by SSA01. You
another for company 2 with all objects owned by SSA02 and so on. So,
instead of adding an authorization list to both of these in which you can
add the users to the databases you want to have access to various data
sets you decide, "hey, I just assign the users who need access to this
data a supplemental group profile of SSA01, SSA02 or whatever data set
they need access to". We tried that. SAVSYS went from 4 minutes to 44
minutes and PRTPRFINT pointed directly to our use of supplemental groups.
Rob Berendt
--
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.
As an Amazon Associate we earn from qualifying purchases.
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.