As you customize your i5/OS™ PASE
programs to use i5/OS functions,
you need to consider the ways in which your program will interact with them.
Communications i5/OS PASE is
generally compatible with AIX® and Linux® in sockets communications.
Database i5/OS PASE supports
the DB2® UDB
for iSeries™ Call
Level Interface (CLI). DB2® CLI on AIX® and i5/OS are
not proper subsets of each other, so there are minor differences in a few
interfaces, and some APIs in one implementation might not exist in another.
Data encoding
Most operating systems, such as AIX® and Linux®, use ASCII character encoding. Most i5/OS functions use EBCDIC character
encoding. You can specify a coded character set identifier (CCSID) value for
some i5/OS object types
to identify a specific encoding for character data in the object.
File systems i5/OS PASE programs
can access any file or resource that is accessible through the integrated
file system, including objects in the QSYS.LIB and QOPT file systems.
Globalization
Because the i5/OS PASE
run time is based on the AIX® run time, i5/OS PASE
programs can use the same rich set of programming interfaces for locales,
character string manipulation, date and time services, message catalogs, and
character encoding conversions supported on AIX®.
Message services i5/OS PASE signals
and ILE signals are independent, so it is not possible to directly call a
handler for one signal type by raising the other type of signal.
Pseudo-terminal i5/OS PASE supports
both AT&T and Berkeley Software Distributions (BSD) style devices. From
a programming perspective, these devices work in i5/OS PASE
in the same way that they work on AIX®.
Security
From a security point of view, i5/OS PASE
programs are subject to the same security restrictions as any other program
on i5/OS.
Work management i5/OS handles i5/OS PASE programs in the same
way it handles any other job on the system.