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



Hey all,

I have a physical file with several multiple format logicals built
over it (don't ask, I wouldn't have done it this way). The
multi-formats are used to sub-select certain records from the same
physical.

a simplified look at how the logicals are created:

R ICDETLF1 PFILE(ICDETLP)
DTLVL1
DTWHSI
DTLINE
<snip lots of fields>
K DTWHSI
K DTLINE
O DTLVL1 CMP(EQ '1')

R ICDETLF2 PFILE(ICDETLP)
DTLVL1
DTWHSI
DTLINE
<snip lots of fields>
K DTWHSI
K DTLINE
O DTLVL1 CMP(EQ '2')

R ICDETLF3 PFILE(ICDETLP)
DTLVL1
DTWHSI
DTLINE
<snip lots of fields>
K DTWHSI
K DTLINE
O DTLVL1 CMP(EQ '3')


I'm changing DTLINE from 4A to 6A (the physical uses a reference file
to define the field).

when I start the CHGPF process, it halts with the following message:

CPF3238
Message . . . . : Key field DTLINE not same as previous formats.
Cause . . . . . : A logical file was being created by your job. However,
the key field DTLINE in record format ICDETLF2 has a different type and/or
length than the key fields in the same position in previous formats.
<snip>

so, it converted the initial format (ICDETLF1) but halted on the
second, I assume because it can't match up DTLINE in format ICDETLF2
in the new definition from the temporary new PF.

has anyone else run into this? any ideas on how I can get CHGPF to
work for these logicals, or should I quit wasting my time and just
delete before and rebuild them afterwards?

Thanks,

Rick

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.