We have changed our QTP Udc to include a "Use" file when Qtp is invoked.
 This use file contains 2 statements:  Set Lock File Update
           Set Process Limit 5000000
 
We are a large shop (800 users), and have noticed better performance with
this method of locking for QTP.  We are very cautious about Impedes on our
system.
 
David Jennings
Mgr of Software Integrity and Performance
Micro Warehouse
 
"The above opinions are only my own, and I take no responsibility in their
content.  No statements may be reproduced in any format without my consent"
 ----------
From: owner-hp3000-l
To: Multiple recipients of list HP3000-L
Subject: Re: QTP problem in batch
Date: Thursday, May 02, 1996 11:48AM
 
Thanks for the responses to our QTP Problem.  We detemined that the
process was performing a SET LOCK FILE REQUEST which was locking the
sets for the duration of the request.  We reviewed the options and
the only one that seems more reasonable is SET LOCK FILE UPDATE.  We
contacted Cognos and basically got no assistance as to the
implications of doing this.  In the manual it indicates that if the
checksum determines the record has been changed that transaction is
bit bucketed and the process stops.  Are there any other
implications of the set lock file update that would warrent against
using it?
 
We are also assuming that the above potential of changed records
will be minimal since QTP will re-read and update in one logical
transaction...correct assumption???
 
Thanks Bob