• Subject: Re: Legacy code -Reply
  • From: DAsmussen@xxxxxxx
  • Date: Sat, 27 Sep 1997 03:41:53 -0400 (EDT)

Walden,

(Welcome, BTW.  Your input has already improved the list)

In a message dated 97-09-22 10:35:51 EDT, you write:

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

MAN could we have used THIS on the last project!  We had "display only"
features that utilized the same program as the "update" version, it would
have been nice not to have the journaling switched to *BOTH just to look at
the record...

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

Well, TRY telling a pharmaceutical user that it's not necessary ;-)!  We had
to write our code to such a standard that a ROLBK start would be considered
unnecessary (although I agree with YOUR position!).  This is why I mentioned
the *PSSR subroutine (to eliminate any of your mentioned "stragglers").

Thanks for the ILE update!

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@AOL.COM (for now)

"Where there is an open mind, there will always be a frontier." -- Charles F.
Kettering
+---
| 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
+---


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].