Evan,

One way to do this is to write a program in the language of your choice that
does a DBOPEN followed by a DBLOCK of each database (this will require MR
capability.) Then the program goes into an infinite loop calling the pause
intrinsic. Any program that tries to update the database will fail to
achieve a lock, rendering the databases read-only. Programs that call
conditional locks will come back immediately with a failed lock.
Unconditional locks will hang.

This has been a very successful solution I have used on systems where a
duplicate copy of the databases is kept for reporting and/or shadowing using
Image log files.

Doug.

Doug Werth                             Beechglen Development Inc.
[log in to unmask]                               Cincinnati, Ohio

The opinions expressed do not  necessarily represent the views or
opinions of Beechglen Development. They might but not necessarily.
They represent solely the opinions of the author.


----- Original Message -----
From: Rudderow, Evan <[log in to unmask]>
To: <[log in to unmask]>
Sent: Thursday, September 09, 1999 1:40 PM
Subject: Converting applications to read-only


> Hi all,
>
> We're converting from our HP3000 "legacy" applications to an ERP real
> soon now; management has decreed that the HP3K apps must still be
> available for lookups but that nobody should be able to enter new, or
> modify existing, data.  I figure the simplest thing to do is change all
> of the databases so that the write class list is empty.
>
> Anyone else got any ideas?
>
> Thanks
>
> Evan