Re: ILE RPG field name weirdness -- RPG400-L

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

Denis Robitaille wrote:

If the second OFFSET is defined in the prototype, that would explain why
there is no compile error. . . .

No.

There is an F-spec pulling in a file containing a packed(5,0) field called OFFSET.

There is a D-spec block defining FIRSTRECIPIENT as

DFIRSTRECIPIENT DS D OFFSET 1 4B 0
D ADDRLEN 5 8B 0
D FORMAT 9 16 D DTYPE 17 20B 0
D RESERVED 21 24B 0
D RECADDRESS 25 275

and there's another D-spec block prototyping QtmmSendMail as

D QtmmSendMail PR ExtProc('QtmmSendMail')
D FileName 255A const options(*varsize)
D FileNameLen 10I 0 const D MsgFrom 256A const options(*varsize)
D MsgFromLen 10I 0 const D RecipBuf like(FIRSTRECIPIENT) D dim(32767) D options(*varsize) D NumRecips 10I 0 const D ErrorCode 8000A options(*varsize)

FIRSTRECIPIENT is used later in calls to QtmmSendMail. And the file in question gets read.

In the compilation listing, OFFSET shows up in the above DS definition, and in the generated I-specs block for the file, and in this cross-reference line:

*RNF7031 OFFSET B(5,0) 215D 2762D

with the RNF7031 indicating that it never gets referenced.

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