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



As a minor point, starting with V4R3 section 1.2.2.3 there is the
additional line "a length of 10 in order to allocate a 4-byte integer
field".  You are correct that previous editions did not mention the
usage of Integer fields.

You are also correct about the majority of the QRPGLESRC includes using
binary definitions rather than integer.  The hope is to be able to
introduce a new source file in the future which provides integer
definitions (along with longer names, function prototypes, based
structures, and other features of ILE RPG).  For compatibility reasons
the existing QRPGLESRC includes would, of course, also be available.

Bruce

>
>Take from the System API Reference 1.2.2.3
>
> "For API BINARY(4) fields, RPG developers should use
>either positional notation or a length of 5 to 9 in order to allocate
>a 4-byte binary field"
>
>It makes no mention of 4 byte integer fields, does this mean all my 9B 0
>definitions have a potential error
>Even some of the API data structures in QSYSINC use 9B 0.
>


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.