In article <[log in to unmask]>, [log in to unmask] says...
>
>
>
>Greetings to all:
>
>I'm working with a customer developing a fairly large-scale application
>using multiple Turbo databases (like about 15).  We're trying to establish
>a mechanism to enforce locking rules, since we are locking multiple
>data bases over the life of a transaction.  I want to have a "standard"
>which dictates the order every program uses to lock the multiple databases,
>and then have some way to enforce programs to do that.  We are localizing
>all DBLOCK calls into one copylib, so enforcement should be rather easy,
>if I can just figure out some nifty way to do it.
>
>BTW, the customer is not happy with the idea of managing his own
>deadlocks, so a whole lot of intricate coding may be out.
>
>TIA,  Rick Winford   on-site  at [log in to unmask]
>


Make all the database I/O routines callable subprograms. For instance, if you
frequently DBGET a customer master record, write a sub called "GETCUSTMAST"
and have the programs call it when necessary rather than do all the DB work
themselves. Then you guarantee that every program accesses the data via the
same methods. Of course the payoff comes when you have processes more
complicated than just getting a single record: a process by which invoice
transactions are paid off or aged can involve dozens of transactions to
multiple sets. Writing a subroutine to do this that can be called has numerous
benefits, one of which is that you know every program which performs that
process proceeds in exactly the same way every time.
--
Mark Landin
UNIX Sys. Admin
TD Williamson, Inc