I thought that I had seen it there (system portion). Perhaps from the
System Value QSYSLIBL? I ain't brave enough to run a test.

Jerry C. Adams
IBM i Programmer/Analyst
I really didn't say everything I said. - Yogi Berra
--
A&K Wholesale
Murfreesboro, TN
615-867-5070


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Thursday, March 08, 2012 12:45 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: QTEMP in LIBL

On 08-Mar-2012 10:18 , Jon Paris wrote:

<<SNIP>> Funny thing is the problem came to light in a scenario where
a utility is QTEMP adding QTEMP to the LIBL, but it fails because it
is already there in the _System_ portion!

Now that's security.


Since the OS intends to prevent QTEMP from ever being in the SYS portion
of the library list, e.g. by error cpd0009 "Parameter SYSLIBLE value cannot
be QTEMP." for CHGSBSD SYSLIBLE(QTEMP), and I believe similarly for the LIB
parameter of the command CHGSYSLIBL, there is already something suspect
about the /security/ on any system where that error could have transpired as
described.

Regards, Chuck
--
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 thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].