RE: RPGII to RPG IV

Set-up the multiply formats to respective data structures.
Old internally defined files have 1 field, just like a flat file.
 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of M. Lazarus
Sent: Monday, December 13, 2004 3:01 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: RPGII to RPG IV

Bob,

  Multi-format LF's work quite well for this purpose.  For input only,
you can create the fields with SST().  But the beast for the long term
is probably to separate out each format into its own PF and use the MFLF
as the glue to bring them all together.  The MFLF would have the same
name as the original PF.

  -mark

At 12/13/04 03:46 PM, you wrote:
>Has anyone moved an old RPGII program to RPGIII and then RPGIV in 
>recent months?
>I'm specifically wondering about approaches to move the 
>program-described database files to externally describd.
>Most of that is obvious, but what about multi-format files? Do people 
>simply do a rewrite of the app in that situation or is there some 
>simpler method to handle them?
>
>-Bob
>
>--
>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.

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




NOTICE: This electronic mail message and any files transmitted with it are 
intended exclusively for the individual or entity to which it is addressed. The 
message, together with any attachment, may contain confidential and/or 
privileged information. Any unauthorized review, use, printing, saving, 
copying, disclosure or distribution is strictly prohibited. If you have 
received this message in error, please immediately advise the sender by reply 
email and delete all copies.