× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



The error is unexpected, with the _given_ source. If however the MFLF source as it really exists does *not* explicitly list the fields for a format, then the error is correct. If any format of the MFLF simply names/refers to the PF format, without naming any fields, then the error is correct where any format has explicitly named fields. Because the error was for ICDETLF2, it would seem most likely that the first format was actually an implicit reference to the format of the physical, rather than the named format ICDETLF1 with its named list of fields.?

Regardless, the easiest resolution is by deleting that MFLF before the ALTER. That action may be the preferred resolution anyhow, because the desirable outcome is _typically_ that the K DTLINE and the field DTLINE in the MFLF should reflect the changed field length [of the physical]. Formats of MFLF which have explicit field lists can never inherit the changed field, because that LF format is not sharing the format of the physical file.

I verified on a new PF and LF, that the error did not occur with the given LF source. However when the LF source was modified such that an inserted [as the first] format was simply a reference to the physical format, then CPF3238 was received for each of format that followed.

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.