|
Buck, Just to expand a bit on source conversion from OPM to ILE.... I typically think of RPGIII when someone says "OPM", so a necessary "first step" is getting the code reformatted as an RPGIV member. The goal on the initial conversion is maximum compatibility with the OPM program. Once the source has been reliably migrated to the new format, then ILE can be incorporated into the programs as needed. A couple of gotchas that the newcomer should be aware of. I don't expect this list is complete, just some of the most common. These are from my personal experience, so feel free to chime in if I missed something important. Thanks...... 1) Numeric truncation - Like it or not, some programmers have come to depend on the old truncation rules. Those date conversion algorithms (MULT 10000.0001) and the like would not function correctly without the old rules, and RPGIV issues an error (by default) when it happens. For maximum compatibility, use control spec TRUNCNBR(*YES) to restore the old rules for the initial conversion. Note that this will NOT affect truncation rules for expressions. 2) Numeric calcs to expressions - Some conversion tools will try to convert numeric algorithms to expressions. Looks pretty, but differences in the way expressions and "fixed format" operators behave makes this a risky modification. NOTE: IBM does not add this feature in its CVTRPGSRC utility. 3) IGNDECERR - This compile option for RPGIII is not available for RPGIV. However, RPGIV has FIXNBR(*{NO}ZONED *{NO}INPUTPACKED) which is probably similar enough 4) Use Control specs to define the environment - Programs converted from RPGIII to RPGIV should include control specs to better define the environment and compiler options. Use DFTACTGRP(*YES) for all newly converted members. Once the program begins to use ILE features, the control specs change. Eric DeLong Sally Beauty Company MIS-Sr. Programmer/Analyst 940-898-7863 or ext. 1863 -----Original Message----- From: Buck Calabro [mailto:Buck.Calabro@commsoft.net] Sent: Tuesday, March 05, 2002 4:58 PM To: rpg400-l@midrange.com Subject: RE: Activation groups for beginners >What I was getting at is that if you put all >of your programs in QILE, and then scope >the overrides to the default *ACTGRPDFN, >the override will affect any other programs >running in the QILE actgrp. > >This is different than DFTACTGRP(*YES) because >in that situation it goes by call-level, and >when that call level ends, so does the override. > >This is why I think *NEW/*CALLER is easier for >new people to understand. I can't outright disagree; I just picked a scenario that I see a lot of and figured I'd work off of that. In a mixed OPM/ILE environment where I'm converting one program at a time, I can't guarantee that the program calling my new ILE *CALLER code isn't OPM. --buck _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l or email: RPG400-L-request@midrange.com 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 mailing list archive is Copyright 1997-2025 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.