Re: Trigger programs.

>>   Does anyone else have any input on this? I have been given to
  understand that the problem with using a trigger program and/or R/I
  over a file is that RPGs will crash and burn if they attempt a
  database function which is porhibited by the constraints. <<

You are correct about both methods. That is, however, precisely the
behavior that is required. If a program is doing something that
compromises database integrity, it deserves to crash. You need to track
down the culprits (at least the critical ones) beforehand and make sure
that they follow the rules. Each program that updates or inserts records
into the physical file should be identified and examined, especially the
ones that run in jobs which may not be easily recovered if an unexpected
error message is received. Suspect code can be modified either to force
compliance, or allow a graceful recovery. In a large system, this may
not be a trivial job, but a system that generates invalid data has
little value.

JMHO
Pete


--
 - Pete Hall peteh@earth.inwave.com
http://www.inwave.com/~peteh/

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *