FILE LOCKING IN QTP

EDISR@detroitedison.com EDISR@detroitedison.com
23 Jun 98 13:17:00 -0400


Pablo 
 
The most effective way to share the data files is to increase the COMMIT 
frequency in the QTPs.  E.g. COMMIT AT UPDATE or COMMIT AT 50 TRANSACTIONS. 
The default is COMMIT AT RUN and this will lock the primary file/table/index 
for the duration of the QTP run. 
 
The risk you take is if a QUICK screen reads a record for update just before 
the QTP gets to it and the user doesn't commit that record for a while, the 
QTP may terminate abnormally when it tries to open it for update read. 
  
 
Robert Edis (Blue) 
Technical Consultant 
Michigan, USA 
(VAX/VMS, ORACLE Rdb, PowerHouse 4GL)
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.