Re: Legacy code -Reply

[Scott Cornell <CORNELLS@xxxxxxxxxxxxxxx>]

In a message dated 97-09-16 22:38:35 EDT,
Dean writes:

<<No, it's not apparent.  But that's how
_I_ learned embedded SQL -- someone
else started writing in it.  Commitment
control can be reduced to a list of
less than 10 rules that someone starting
out needs to know, with emphasis on
how to handle it in an ABEND situation>>

              ----------

At least you had some sample code to learn
embedded SQL from ;)  

However, for my own information, I'd be
very interested in seeing Dean's "Top Ten
rules for commitment control."  I know
pretty much what commitment control is for
(ensuring that nothing is "1/2 updated"
should an error occur, right?), but since
we don't develop new code here (only
enhance & maintain another vendor's code
that does *NOT* use SQL, VA-RPG, commitment
control, or any other goodies of the 90's
:(), my experience has been limited to
dabbling w/embedded SQL in in-house
conversions, file translations, and fix
pgms.  Most of them were one time deals, so
"commitment control" consisted of restoring
the files & rerunning the conversion if
something went wrong!
+---
| 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
+---