CPI1466: Job holds large number of locks

[Matthias Oertli <oertlim@xxxxxxxxxxxxxxxx>]

Recently my *allusr backup has started sending CPI1466 to
the 
*SYSOPR queue, indicating that the job holds in excess of
30000
locks. As the message suggests, I ran a WRKJOB
OPTION(*JOBLCK)
which took 80 minutes to produce a 1151 page spool file.
It looks like SAVLIB has locks on multiple libraries, on
every
object within them and on every member within every object. 
Not really understanding the process I was wondering if this
is
normal behaviour. I was under the impression SAVLIB
SAVACT(*NO)
works on a library by library basis. Anyone?
Regards,
Matthias

btw: v4r3, cum 9054

--------------------------------------------------
Matthias Oertli   oertlim@s054.aone.net.au
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---