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.