× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi,

1. Commitment control will also work for RPGIII programs, you do not have to
convert them to RPGIV.
2. You have to create a Journal and Journal receivers and register your
physical files in this journal.
3. If you want to use Commitment control in your RPG-Programs, you have to
add the keyword COMMIT (COMIT)
   for you update and output files in the F-Specs.
4. You do not need to specify COMMIT for Input-Files.
5. You have to decide where to set COMMIT and ROLBK in your programs.
   A record remains locked until the next COMMIT or ROLBK.
   UNLOCK or Extender (N) will not free the record.
6. Because Journaling requires additional actions, performance may go down a
little
   and you'll need some additional disk space.
7. You have to start commitment control for your job STRCMTCTL.
   Be careful the default value for Commitment Scope is activation group.
   As long as you do not have a true ILE environment, commitment scope
should be set to *JOB.

I hope that helps, for more information look at the online library.
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/rzakj
/rzakjcommitkickoff.htm


Birgitta

-----Ursprüngliche Nachricht-----
Von: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]Im Auftrag von Forbes, Vincent
Gesendet: Freitag, 4. November 2005 17:24
An: RPG programming on the AS400 / iSeries
Betreff: Conversion to RPGLE & commitment control


In our application, we have a series of 9 RPG programs that creates all
transactions.  The problem is that there is little or no error checking for
such things as record lock.  We have nightly audit reports that verify
balances & every few months or so it finds a problem where not all of the
files were updated.

I am trying to make a case to put commitment control on this process.

Some of the issues are:
-       The RPG programs need to be converted to RPGLE so commit can span
all the programs.  Will a simple IBM conversion {no commit} change how the
program works?  Does IBM guarantee there is no difference?
-       Will the performance with commit suffer?
-       What is needed to add in commit to this process?
-       Some programs don't do any updates.  They just return info.  Do they
need to be converted to RPGLE?
-       Any others?


Since I work for a bank, the paranoia level is high.  The general feeling is
"If it ain't broke...don't fix it" and "Do you realize how much testing we
will have to do for this change?"


Vincent Forbes
CIBC
Toronto, Ontario

Nothing is impossible...if you don't have to do it yourself.
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.