IBM Version 4 manual Started, Locating the API to, Socket Network Functions This, Unix

Chapter 2. Getting	Started		with	APIs
You	may	find	the information in this chapter helpful as you start						t
for	example,		locating	the	API	that	you	want to use. It also tells	y
tion	that	you	will need		when	using	the	APIs. Other topics covered	a

Ÿ Language selection considerations

ŸAPI environments

ŸAPI parameters

ŸInternal identifiers

Ÿ User spaces and receiver variables

ŸContinuation handles

Ÿ System and user domain concepts

ŸExit programs

ŸQSYSINC library

ŸQUSRTOOL library

Ÿ	User	index considerations (recovering data)
Ÿ	APIs	and internal system objects

ŸPerformance considerations

Locating the API to	Use
If	you	are usingSystemtheAPI Reference, you can use the following methods to
find	an	API:

ŸYou can use the table of contents where the APIs are grouped

Within each chapter, the APIs are listed in alphabetical order.

ŸYou can use the index where the APIs are listed in alphabetica

application programming interface (API) topic.

ŸYou can also use the index where the APIs are listed under te following:

–Job API

–List API

–

Spooled file

API

–

Socket

network

functions

(in

this

case,functionsthe meansterm the

same

as

APIs)

Except for APIs that are defined

by

formal

standards organizations

UNIX

type or Systems Application Architecture (SAA)), OS/400

APIs

start

letter

Q

and

are

followed

by

two

to three

letters

that

make

up

an

nent

identifier. The last part of the API name identifies the actio

API.

Generally,

the

information after

the

component

ID

is

an

abbrevia

verb

that

describes

the function

of

the API. Figure 2-1

on

page 2-2

the

verbs

that are

either

part

of

an

API

name

or

are

implied

ver

an API

name.

 Copyright IBM Corp. 1997 2-1