RE: Pros & Cons

Krys:
>I wouldn't say that no one does.  I know several shops that have to monitor 
>before and after images for user controls.

(Nina:)
>they were done that way to print changes before and after.  but now
>no one even prints out the change edits anymore...

Change Edits and the like are best done from Journal Images.  A company in
Melbourne (I'll remember the name eventually) sells a utility to print
journal images nicely ... I wrote my own, too, but it has fewer features
and is a little flaky for use other than programmer testing.

Please don't tell me about the performance impact of journalling. It ain't
so, unless you're doing things the S/36 way (copying files all over the
place).

With regard to field naming, a common practice is the "2+4" field name, in
which the first two characters of the name identify the format the field
comes from.  So  field name XYCUST and AACUST are the CUST field on two
different database formats, and #1CUST is CUST on display-file format 1.
If you follow this standard, it is dead easy (that is, I have done it) to
write a command to generate RPG source to do the moves from one format to
another, and append that as a subroutine to your program.

In RPG IV, it's even easier, I believe.

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