RE: WRKQRY is using *SHRNUP lock

Yes, there is, according to this message I saved long ago.

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@xxxxxxxxxxxxxxxxx>

Donald R. Fisher, III
Project Manager
Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@xxxxxxxxxxxxx

<clip>
Is there a way to change WRKQRY to use *SHRRD like SQL?
<clip>