problem with QSYSARB holding a lock on a library object

["Mark S. Waterbury" <mark.s.waterbury@xxxxxxx>]

Hello, all:

With V5R3M0 and above, we have the system value QLIBLCKLVL that can be 
set to 0 to inhibit the *SHRRD lock on *LIB objects that are added to 
each job's library list.  This is convenient when we need to be able to 
rename a library (for example, on a test system).

Last week, I was working with a customer running V6R1, and they changed 
QLIBLCKLVL from 1 to 0, but the next day, there were still a large 
number of system jobs (spool jobs, etc.) that held a *SHRRD lock on the 
library in question, presumably because those jobs started before they 
changed QLIBLCKLVL. 

They decided to wait for the next scheduled IPL of the system over the 
week-end.  Now, I see the QSYSARB job holds a *SHRRD lock on several 
libraries, including the one we want to rename.

Does anyone know what is going on here?

Under what conditions does QSYSARB hold a *SHRRD lock on a library, and 
why does it appear not to honor the QLIBLCKLVL system value?

Thanks,

Mark S. Waterbury