IBM Version 4 manual Ccsid, Compile Program Specific, Include File

Figure 2-5 (Page				2	of	2).		Include Files Shipped with the QSYSINC Library
Operating			Language				File	Name	Member Name	(Header File)
Environment
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:
1 CEE	ILE APIs are			included in this part of the table.
2 The API can be				either bindable when					you	use	the service program name
when		you	use the		API		program name.

For development of client-based applications, the integrated-file-system links to QSYSINC openness includes are provided in the /QIBM/include pa

Include

files for

exit

programs

are

shipped only if the

exit

progr

The member names for these exit programs

start

with

the

letter

E. E

array definitions for APIs that also start

with

E,

any

member

names

QSYSINC library that start with the letter

E

are

include

files

for

Refer

to Systemthe

API Referencefor the actual member

names

for the

exit

grams.

All

source

physical

files

are shipped

with

read

capabilities

only;

c

made to the QSYSINC library. All are built

with

a

CCSID

of

00037.

When

compile

a

program

in

a specific

CCSID,

any

QSYSINC

include

file

is

con

the

program CCSID.

If you are coding in ILE C, the header files in the QSYSINC librar system include files. You should use the < and > symbols on the #inc ment; this affects how the library list is used to search for hea

If you are coding in RPG or COBOL and need to define storage for fields, you should copy the appropriate QSYSINC system include to a library. You can then customize the include file to your specific n customized member when you compile your application.

If you are developing applications on a release n system that will r release n-1 system, you may want to copy each release's include file source libraries. This will minimize the impact of include file change enhanced over time with additional fields.

Chapter 2. Getting Started with2-29APIs