|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Thank you Jim. This was quite timely information. And yes, these Queries are doing multiple member files (yuck). I will discuss this with the individuals involved. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin Jim Damato <jdamato@dollargeneral.com> Sent by: midrange-l-admin@midrange.com 07/24/2002 04:11 PM Please respond to midrange-l To: "'midrange-l@midrange.com'" <midrange-l@midrange.com> cc: Fax to: Subject: RE: Various file lock states > Rob: >I was analyzing a difficulty with ADDPFM. I was noticing that >RUNQRY, UPDDTA, WRKDBF, etc all lock a file with *SHRRD. While >WRKQRY locks afile with *SHRNUP. Frankly I don't think there is >any need for this high of a lock on the file. It is not like the >query was outputting to an outfile, just screen. > >Any comments? Stolen from iSeries Network tips forum: ---------- The following command can be used to enable support to have Query/400 default to use *SHRRD locks on the input database files: qsys/crtdtaara dtaara(qusrsys/qqulcklvl) type(*char) + len(4) value('LSRD') aut(*use) Query/400 will examine the contents of the data area named QQULCKLVL in library QUSRSYS to determine the lock level to be applied to the input files for the query definition during definition time activity. The two supported values: LSRD Causes a *SHRRD lock to be put on the files LSRO Causes a *SHRNUP lock to be put on the files If the data area is not retrievable for any reason then the default is to perform *SHRNUP on the *FILE object during 'definition-time' activity. 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. Usage of this data area for *SHRRD will no longer enforce a same-member assumption; and as such could effect future run requests to access an incorrect/unexpected member, or failure to find a/the member -- whereas with *SHRNUP, these 'failing' scenarios can not occur. Caveat emptor. HTH. --------------------- James P. Damato Manager - Technical Administration Dollar General Corporation <mailto:jdamato@dollargeneral.com> _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.