Re: CRTPF question?

[Vern Hamberg <hambergv@xxxxxxxxxxxxxx>]

At 06:31 AM 8/9/97 -0400, you wrote:
>Tim,
>
>In a message dated 97-08-04 21:07:25 EDT, you write:
>
>> Why isn't there a keyword on the CRTPF CL command that will give you an
>>  option to reserve the files existing data and then *ADD the data back
>>  using the FMTOPT(*NOCHK) for you?  Is this a stupid question?  But the
>>  OS400 developers seemed to have thought of everything so I am suprised
>>  that you have to go thru several steps when changing a physical file
>>  (Change the DDS, CRTDUPOBJ the current file, then CRTPF the new blank
>>  file, then CPYF the old data into it) Is there a good reason for these
>>  methodical steps? 
>
>Not a stupid question at all.  Take heart, you COULD be using the AS/Set CASE
>tool which performs this function as long as it "feels like it".  Sometimes,
>AS/Set drops the data for no reason.  Compiling files is one of the single
>hardest paradigms for people going straight from the S/36 to the AS/400 to
>comprehend.  Although I personally would prefer FMTOPT(*MAP *DROP) as the
>default, I really do not know why IBM chose to blow away the data
>altogether...
>
>I Hear 'Ya
>
>Dean Asmussen
>Enterprise Systems Consulting, Inc.
>Fuquay-Varina, NC  USA
>E-Mail:  DAsmussen@AOL.COM
>

Use CHGPF instead of CRTPF. At least in v3r2/v3r7, the CHGPF command has a
source file parameter that applies changes while preserving the data. About
time, I'd say!

Cheers

Vernon Hamberg
System Software Programmer
Old Republic National Title Insurance Company
400 Second Avenue South
Minneapolis, MN 55401
(612) 371-1111 x480
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *