FILE LOCKING IN QTP (long)

[WITKOPP@IDT.COM]

> Hello,
> 
> I've been reading the QTP (vms) reference manual trying to figure out file
> locking without much success.  A number of terms are either not defined or
> ambiguously defined.
[snip]
> What i would like to happen is to have everything shareable or at least
> semi-exclusive so that QTPs and QUICK can access the same files at the same
> time.  QTP should lock files during update, but only for the duration of
> the update.

It depends on how you're doing the update. Are you creating
a temporary file? If so, it's going to do the input phase-output
phase thing where it doesn't begin updates until the input phase
is complete. You might check into whether you can do your
updates in multiple requests, avoiding the creation of a temporary
file. You can then set updates to lock just the record (probably
the cluster actually) when it needs to update. You still need
a strategy to handle conflicts when they occur, but they'll be
much less frequent.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
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.