QSPRWTRI not in QC2LE ???

[bvining@xxxxxxxxxxxx]

If the procedure is an API found in the System API Reference then you
do not need to worry about the binding directory.  It happens to be
QUSAPIBD, but as that *BNDDIR is implicitly used by the system you do
not have to specify it.  Most of the *SRVPGM based system APIs do
document the *SRVPGM name, but that is because the various language
include file members are named the same as the *SRVPGM (except for the
cross platform APIs (Unix-type, CEE, etc.) where the include file member
name is often dictated by industry convention).

If, on the other hand, the API is found in one of the ILE C manuals
(C/C++ Run-Time Library Reference or ILE C/C++ MI Library Reference
for example) then specifying QC2LE is probably a wise move.

And if the API is actually part of a separately ordered product, then
the product documentation should tell you what *BNDDIR or *SRVPGM
to specify when creating your application.

Bruce Vining

>
>What do you do when you find that it's a procedure? Which binding directory
>is it in? Most seem to be in QC2LE, but there are a few others, and tracking
>down a particular procedure can be quite time consuming. Is there a better
>way? Shouldn't the documentation tell us where to find it?
>


+---
| 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
+---