Filter
Top Products
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 the
System API Reference
, SC41-5801
APIs for the UNIX Environment
The interfaces provided by sockets, the integrated file system, and the Common
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 inte-
grated file system should ease the amount of effort required to move UNIX**
applications to the AS/400 system.
The integrated file system is a function of OS/400 that supports stream input/output
and storage management similar to personal computer and UNIX operating
systems. It also provides an integrating structure over all information stored in
AS/400.
The naming conventions for the UNIX-type APIs are determined by industry stand-
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 in the
System API Reference
, SC41-5801
API Parameters
After you have found the API that you want to use, you need to code a call to an
API and pass to the API the required set of parameters appropriate for that API.
Parameters can be:
Required, which means that you must enter all of the parameters in the speci-
fied order.
Optional, which means that you must enter all or none of the parameters within
the optional group. When you enter an optional group, you must also include
all preceding optional groups.
Omissible, which means that the group of parameters may have parameters
that can be omitted. When these parameters are omitted, you must pass a null
pointer.
For OPM and ILE APIs, the values for all parameters that identify objects on the
system must be in *NAME (basic name) format, left-justified, uppercase, and with
valid special characters. (The *NAME format is a character string that must begin
with an alphabetic character (A through Z, $, #, or @) followed by up to 9 charac-
2-6 System API Programming V4R1