|
David, The QUSAPIBD *BNDDIR is intended to contain all ILE APIs that are documented in the System API Reference. From a historical point of view, functions such as perror() were viewed as part of C runtime (and are documented in the C language reference manuals rather than the OS/400 manuals). Since language runtime is in fact part of OS/400 perhaps this should be re-examined. No promises, but I will see if we can (in a safe manner) add the various C runtime *SRVPGMS to QUSAPIBD. One problem I can see is that the C header files should probably then move to QSYSINC also, and that is definitely opening up a can of worms..., oh and what about the API documentation??? Thanks (I think), Bruce > >Bruce, > >Why do you have to specify a service program on the create? >I see that QC2IO is not in QUSAPIDB, is this API an exception? >The manual says "Service programs that contain OS/400 ILE APIs are >in the QUSAPIBD binding directory. This binding directory is >implicitly used by ILE compilers to resolve the OS/400 ILE API >references; therefore, it is not necessary to explicitly name >the service program or the API binding directory when creating >programs that use OS/400 ILE APIs." > >Thanks, > >David Morris > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@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 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.