Journaling Constraints

Can journaling be enforced at the DB level?

I am building an application that is using journaling to track history of
changes, and allow user inquiry (so they will stop saying it was my pgm, and
they didn't change anything <grin>).

Because the primary key of the file (account number) can change, the inquiry
program _NEEDS_ journaling to be on, at all times. If journaling is off, and
an account number changes, bad things will happen, and their history will be
'orphaned'. The easy answer is to write all update/add applications to check
for journaling to be on, before updating or adding anything. But who knows
who will be writing these update programs.

What I am hoping is that there is a way to set up something similar to a PF
constraint, that will not allow WRITEs/UPDATEs/DELETEs to a particular file
unless journaling is on.

--
"Enter any 11-digit prime number to continue..."
"In Hebrew SQL, how do you use right() and left()?..." - Random Thought
"If all you have is a hammer, all your problems begin to look like nails"