×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




You could use prefix() on one of the files to change the name of the fields.

From the manual ...

D outrecDs e ds extname(outfile) prefix(O_)


-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of tgarvey@xxxxxxxxxx
Sent: Tuesday, September 24, 2024 1:10 PM
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Subject: Two files, two fields, different lengths

Hi,



I have two files which have a field with the same name, but which have
different lengths.
I'm trying to overlay them so I can access their contents with arrays. But
the compiler fails with *RNF7408 30 1 The length of the input field
does not match the definition of the field; specification is ignored.

Here's how they're defined.



D Old1 E DS extname(OpenQryf1:*INPUT)

D qualified

D ValidInd overlay(ADVALN)

D like(*InLR)

D dim(%size(ADVALN))



D Old2 E DS extname(OpenQryf2:*INPUT)

D qualified

D ValidInd overlay(ADVALN)

D like(*InLR)

D dim(%size(ADVALN))



The ADVALN in the first file is defined as 225 characters while the ADVALN
in the second file is defined as 226 characters.

How do I tell the compiler that the ADVALN for the second file is not the
same as that in the first?
I never refer to ADVALN in any other part of the source code.

I've tried referring to ADVALN as Old1.ADVALN (e.g. overlay(Old1.ADVALN))
but the compiler doesn't like that either.



What am I not seeing? Any ideas?



Kind Regards,



Thomas Garvey


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