Re: RPG redbook

I’m afraid I have no idea who wrote that section and personally would never use EXPORT/IMPORT - to me that can create a cure that is as bad or worse than the disease! I also agree with you about using the PF layouts as sources for the DS - unless of course they are used simply as a communication vehicle and are populated from multiple tables.

So I’m afraid I really can’t give you any answers on that.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Oct 22, 2016, at 2:03 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

I just finished the Externalizing I/O section, and I'm not really sure it helps with the "hack the DB one more time" mentioned at the start.

We're just finishing up what I imagine is a typical DB change issue. We have a table with several columns that need to be lengthened. The table is used in 800-900 programs, some still using I-specs. We of course had no practical choice but to add new columns at the end and orphan the old ones.

The sample app exposes (via EXPORT/IMPORT) data structures defined off PF record formats. How does that help with DB changes? If you change the table and service program, the service program will be exposing a different layout of the DS than calling programs expect which will cause errors.
--
This is the RPG programming on the IBM i (AS/400 and 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.

Please contact support@xxxxxxxxxxxx for any subscription related questions.