|
Scott,
> The "DataOffset" is a variable that I receive from the API itself.
> There's no guarantee that the first entry will immediately follow the
> header. (In fact, it frequently doesn't, since there's an "Input Parm"
> section, and some other sections)
Sorry. I had to search through my code library to locate an example, and the
first one I happened to pull up was for a fixed length header that doesn't
have an offset value stored within it.
> Your idea of keeping track of the total offset from the start in an
> integer field, rather than keeping track of the next pointer position as I
> do, is interesting, though. I'll have to think about that some more.
Here's a version more appropriate for the list API:
c eval EntryOffset = DataOffset
c for EntryNo = 1 to NumEntries
c eval p_ListEntry = p_ListHeader + EntryOffset
c*** ... at this point, the JOBL0100 data structure contains
c*** ... one of the entries of the list.
c eval EntryOffset = EntryOffset + EntrySize
c endfor
Regards,
John Taylor
As an Amazon Associate we earn from qualifying purchases.
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.