On Mar 8, 2012, at 1:44 PM, midrange-l-request@xxxxxxxxxxxx wrote:

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.

That's interesting Chuck. I had never tried to do it, I was just going from screen shots on a client system where my startup code (which is attempting to replace the User LIBL) errors out because QTEMP is already in the system portion of the LIBL. From what I can see, while the system defends against things like CHGSBSD from using QTEMP in this way, sadly it does not prevent it from being added to the QSYSLIBL system value list.



Jon Paris

www.partner400.com
www.SystemiDeveloper.com





This thread ...


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

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