|
In your post it read "secured by authorization list", I was under the
impression that you might not have access to the autl object.
On Mon, Feb 7, 2011 at 12:38 PM, Charles Wilt <charles.wilt@xxxxxxxxx>wrote:
Jack,--
I don't know why an authorization list would make a different, but in this
case
Object . . . . . . . : QSYS Owner . . . . . . . : QSYS
Library . . . . . : QSYS Primary group . . . : *NONE
Object type . . . . : *LIB ASP device . . . . . : *SYSBAS
Object secured by authorization list . . . . . . . . . . . . : *NONE
Charles
On Mon, Feb 7, 2011 at 11:20 AM, Jack Kingsley <iseriesflorida@xxxxxxxxx>
wrote:
Unless I am missing something, what is the authorization list securing itit
called and what does it look like when you do the dspautl command against
for your profile.list
On Mon, Feb 7, 2011 at 10:41 AM, Charles Wilt <charles.wilt@xxxxxxxxx
wrote:
I don't understand how/why I'm getting the following:
DSPOBJAUT OBJ(QSYS) OBJTYPE(*LIB)
Object . . . . . . . : QSYS
Library . . . . . : QSYS
Object type . . . . : *LIB
Object secured by authorization list
Object
User Group Authority
*PUBLIC *USE
DSPAUT OBJ('/QSYS.LIB')
Not authorized to object. Object is /QSYS.LIB.
I have authority to root
DSPAUT OBJ('/')
Object . . . . . . . . . . . . : /
Type . . . . . . . . . . . . . : DIR
Owner . . . . . . . . . . . . : QSYS
Primary group . . . . . . . . : *NONE
Authorization list . . . . . . : *NONE
Data --Object Authorities--
User Authority Exist Mgt Alter Ref
*PUBLIC *RWX X X X X
And I can DSPAUT on other libraries....
dspaut OBJ('/QSYS.LIB/C1162332.LIB')
Object . . . . . . . . . . . . : /QSYS.LIB/C1162332.LIB
Type . . . . . . . . . . . . . : LIB
Owner . . . . . . . . . . . . : C1162332
Primary group . . . . . . . . : *NONE
Authorization list . . . . . . : *NONE
Data --Object Authorities--
User Authority Exist Mgt Alter Ref
*PUBLIC *RX
C1162332 *RWX X X X X
So why can't I DSPAUT OBJ('/QSYS.LIB')???
Thanks!
Charles
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
listTo 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.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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.
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.
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.