Re: CHGPF Issues

[MBarton@xxxxxxxxxx]

>While testing a planned database modification(2 fields were added and 2
>numeric fields had their length increased) we discovered the following
>issues with CHGPF.
>
>We use a field reference file, which was modified with the changes and
>compiled successfully.
>
>1> If the field in the DDS of the modified file is a "referenced" field,
the
>CHGPF command will not change the field lengths in the physical file nor
in
>the associated logical files.  The work around; remove the reference code
>and apply the correct length information to the field definitions.

I use a similar setup & have had no problems other than on one occasion
i got the same field on physical & logical being different lengths but
the circumstances escape me at the moment (on V4R4 at the time).

>2> If a logical file explicitly names fields, neither the fields with the
>changed length nor the added fields were "modified" or "added".  There
does
>not appear to be a work around for this situation.

This is as you would expect it to be. By selecting a subset in the first
place,
how does the command know you want any additional fields (and which ones)
added ?

AFAIK its a manual change to add the field(s) to the logical then
re-compile.

Mike


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---