Re: RPG Cycle

[fkolmann@xxxxxxxxxxxxx]

Orphaned records (like people) are caused by the unexpected death of parents.
Program crashes/bugs etc need to be identified and the causes fixed to prevent
further orphans.

The 'bad/orphaned' records I strip from the live files and transfer to 'error
files' as
the normal purge processes cannot cope with them. This keeps a record of what
happened for auditing purposes.  I dont know how to use the referential 
integrity,

I dont understand how it works particularly  when records are being 'created',
until all the records
are in place there cannot be intergrity so that implies that Journalling with
Commit/RollBack
needs to be used.  The canned software we use has not got Commit hence my
deficiency.

"James W. Kilgore" wrote:

> Hi,
> I've got to ask.  Once the system shows you the orphans, what do you do about
> them?
> If the referential integrity checker doesn't allow them, how do you get rid of
> them?
>
> TIA
>
> fkolmann@revlon.com.au wrote:
>
> > I need to learn what and how to do 'Referential Constraints'.
> > I will check the DataBase Guide.
> >
> > "Nelson C. Smith" wrote:
> >
> > > Try adding Referential Constraints to those files and the system will show
> > > you the orphans real quick.  No programming required.
> >


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---