Connx and RMS file locking

[Chris Sharman]

>We are running PH 710.G1  on a VAX/ALPHA and are using CONNX as an ODBC
>connection to our files.
>It seems that CONNX is not recognizing PH record locking.  PH "DOES" recognize
>the locks
>issued by CONNX.
>
>Has anyone experienced these problems?  Any feedback is appreciated

Oh, yes, I've experienced PH locking problems.
Powerhouse's default behaviour is not to lock, but to re-read & checksum on
update: if there is a conflict, you get the "record has changed since you found
it" message. I presume this is what's happening ?

If you use PH file locks, they're GROUP level locks, and DON'T provide any sync
between users in different VMS groups.

If you use Quick "LOCK RECORD", then it uses real RMS locks (hurrah), which
then cooperates (at the RMS level) with all other well-behaved applications
(sounds like CONNX is one such).

I've dispensed with PH file locks as cumbersome & ineffective, and am
dispensing with the DALOCK.OBJ module in my cooperating 3GL code, in favour
of PH LOCK RECORD.

The only fly in the ointment is QTP, where to get it to use record locking you
need to avoid using an intermediate file: often difficult. You're left with
PH file locks (as discussed), exclusive or protected file opens, or "record
has changed since you found it".

How is CONNX, by the way ?

Chris
_______________________________________________________________________
Chris.Sharman@CCAgroup.co.uk		http://www.ccastat.demon.co.uk/
CCA Stationery Ltd, Eastway, Fulwood, Preston, Lancashire, PR2 9WS.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.