Re: Legacy code -Reply

["Walden Leverich" <walden@xxxxxxxxxxxxxxx>]

<snip>
>2.  You must specify, using a K extender, which files in your RPG are to be
>affected by commitment control (ehhh, we HAD no ILE back then, anyone with
>ideas on CC under ILE?).
<snip>
Under ILE/RPG there is a COMMIT(*YES) and COMMIT(*NO) option on the file.
Even better, you don't need to decide on commitment control at compile time.
There is a COMMIT(pgmvar) option and if pgmvar is '1' when the file is
opened it will be opened for commitment control, otherwise ('0') it will
not. You will need to use a user open to change this variable before the
file is opened, but this option sure helps when writing trigger programs.

<snip>
>4.  Establish a "commitment block" prior to writing to or updating any
files.
> Place a COMIT statment up front, and another after, all writes/updates are
>successful.
<snip>
Although this process of establishing a "commitment block" is not
technically necessary I agree with its use. HOWEVER, I would use a rollback,
not a commit, to start the block. Under commitment control I am committing a
block of updates that must all occur as a group, if there are some stragling
updates hanging about when I start this "block" I want them toasted, not
commited. If the process that caused these straglers completed successfully
it should have commited the upates itself.

-Walden


+---
| 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
+---