× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. July 2002

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

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.