RE: Various file lock states

>Please note that the reason for the *SHRNUP is to ensure that usage of
>*FIRST, *LAST, and Specific_Member_Name does not change or fail from one
>invocation to the next.

I really think that if there isn't a lot of ADDPFM and RMVM activity you
don't have much to worry about.  And really, if you run your queries in
separate RUNQRY steps outside of WRKQRY you'll probably eliminate the risk
entirely.  It seems like the *SHRNUP lock is just there to prevent member
changes that could impact your member name selection or the established
*FIRST or *LAST between file/mbr selection time and execution time.

I applied this change in a multi-member environment and haven't had an issue
yet.

-Jim