For development of client-based applications, the integrated-file-system symbolic
links to QSYSINC openness includes are provided in the /QIBM/include path.
Include files for exit programs are shipped only if the exit program has a structure.
The member names for these exit programs start with the letter E. Except for RPG
array definitions for APIs that also start with E, any member names in the
QSYSINC library that start with the letter E are include files for exit programs.
Refer to the
System API Reference
for the actual member names for the exit pro-
grams.
All source physical files are shipped with read capabilities only; changes cannot be
made to the QSYSINC library. All are built with a CCSID of 00037. When you
compile a program in a specific CCSID, any QSYSINC include file is converted to
the program CCSID.
If you are coding in ILE C, the header files in the QSYSINC library are considered
system include files. You should use the < and > symbols on the #include state-
ment; this affects how the library list is used to search for header files.
If you are coding in RPG or COBOL and need to define storage for variable length
fields, you should copy the appropriate QSYSINC system include to a user source
library. You can then customize the include file to your specific needs and use the
customized member when you compile your application.
If you are developing applications on a release n system that will run on a
release n-1 system, you may want to copy each release's include files to user
source libraries. This will minimize the impact of include file changes as APIs are
enhanced over time with additional fields.
Figure 2-5 (Page 2 of 2). Include Files Shipped with the QSYSINCLibrary
Operating
Environment Language File Name Member Name (Header File)
ILE APIs ILE C H Service program name or API
program name2
ILE RPG QRPGLESRC Service program name or API
program name2
ILE COBOL QCBLLESRC Service program name or API
program name2
UNIX type ILE C ARPA Industry defined
ILE C H Industry defined
ILE C NET Industry defined
ILE C NETINET Industry defined
ILE C SYS Industry defined
Notes:
1CEE ILE APIs are included in this part of the table.
2The API can be either bindable when you use the service program name or callable
when you use the API program name.
Chapter 2. Getting Started with APIs 2-29