Re: 30000 locks after v4r4

["Evan Harris" <spanner@xxxxxxxxxx>]

Deb

I have seen this message many, many times. The way I read it, the save locks
items as it prepares them to be put on tape; I guess this is some kind of
synchronization thing. If it can get a lock, then the objects isn't locked
and it can be saved. Therefore, if it has to get a large number of locks
before commencing a save of the  library, the message gets issued. (Someone
may issue a more technical explanation of this)

Anyway, I had a few libraries that had extremely excessive numbers of
members in multi member files and I used to get this message all the time -
back to at least 3.7

It made me examine the way my objects were grouped and stored as I figured
that while it was doing all that there was some potetnial for it to slow the
save. Cant confirm or deny this, but it certainly made me look at things and
re-ogranise them


HTH
Evan Harris

>  After my first daily backup since upgrading to V4R4 I received the
>following message. IBM seems to suggest this message has been here since
>v3r2 and is just info only. I have never seen this message before!
>Everything did save fine except a few objects in qusrsys, so I realize it
is
>not critical.  Just an inquiring mind that's all !  Anyone have any insight
>as to what this message is telling me other than the obvious?



+---
| 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
+---