IBM Version 4 manual APIs for the Unix Environment, API Parameters

ŸMath functions

ŸMessage services

Ÿ Program or procedure call management and operational descriptor access

ŸStorage management

Related Information

Ÿ	“Integrated	Language	Environment (ILE)	CEE APIs”	on page 8-7
Ÿ	ILE Concepts,	SC41-5606,	for conceptual	information	about ILE

ŸSAA CPI Language Environment Reference, for information about the SAA Language Environment

ŸILE CEE APIs in Systemthe API Reference, SC41-5801

APIs for the UNIX Environment

The interfaces provided by sockets, the integrated file system, and Programming APIs (CPA) Toolkit/400 are part of a continuing emphasis on sup- porting an open environment on the AS/400 system. The socket functions and grated file system should ease the amount of effort required to move applications to the AS/400 system.

The integrated file system is a function of OS/400 that supports strea and storage management similar to personal computer and UNIX operating systems. It also provides an integrating structure over all information s AS/400.

The naming conventions for the UNIX-type APIs are determined by indust ards organizations.

Related Information

Ÿ	“UNIX-Type	APIs”	on page 8-21
Ÿ	Common Programming APIs Toolkit/400 Reference, SC41-4802
Ÿ	Integrated File System Introduction, SC41-5711
Ÿ	Sockets Programming, SC41-5422
Ÿ	UNIX-type	APIs	inSystthem API Reference, SC41-5801

API Parameters

After you have found the API that you want to use, you need to co API and pass to the API the required set of parameters appropriate Parameters can be:

ŸRequired, which means that you must enter all of the parameters in

fied order.

Ÿ

Optional,

which

means

that

you

must

enter all

or none

of

the

paramet

the

optional group. When

you

enter

an optional

group,

you

must

also i

all

preceding

optional

groups.

Ÿ

Omissible,

which means

that the group of parameters

may

have

parame

that can be omitted. When these parameters are omitted, you must

pointer.

For OPM and ILE APIs, the values for all parameters that identify obje system must be in *NAME (basic name) format, left-justified, uppercase, valid special characters. (The *NAME format is a character string that with an alphabetic character (A through Z, $, #, or @) followed by up

2-6System API Programming V4R1