APIs and pointers (was: QSYSINC not in V3R7M0 what to do?)

[bvining@xxxxxxxxxxxx]

In the case of *PGM based APIs the returning of actual pointers is
discouraged due to the lack of pointer support in some of the OPM
languages.  For *SRVPGM based APIs there are, however, APIs that work with
pointers.  This is permitted as ILE RPG, ILE COBOL, and ILE C all have
at least some minimal level of pointer support.

Examples would include the Dynamic Screen Manager QsnRtvEnvDta API
which returns a space pointer (PTR(SPP)) as its second parameter,
the QsnCrtEnv API which accepts two procedure pointers (PTR(PP)) for
its third parameter, and the program activation QleActBndPgm API
which accepts a system pointer (PTR(SYP)) as its first parameter.

In all these cases the pointer is defined as PTR(x) and not, as you are
already aware, a CHAR(*).  The CHAR(*) is used to indicate a variable
length field or structure of multiple fields.

I will point out that I am refering specifically to AS/400 unique system
APIs.  The Unix-type APIs have their own documentation style and conventions.

Bruce

>
>I don't think any of the APIs return actual pointers...
>


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