Filter
Top Products
The registration facility APIs provide the capability to:
Register and deregister exit points with the registration facility
Add and remove exit programs to and from the repository
Retrieve exit point and exit program information from the repository
Designate the order in which exit programs should be called
An exit point can call one program, a fixed number of programs, or all programs
associated with an exit point. The exit program number associated with each exit
program should be used to determine the sequence in which the exit programs are
run.
An exit point can be registered multiple times with the same exit point name;
however, the combination of the exit point name and the exit point format name
must be unique. Each exit program will be associated with a specific exit point and
exit point format. The exit point format name can be used to indicate that a change
occurred to the interface of the exit point. For example, this unique name (exit
point and format) could be the result of a parameter change, version change, exit
program data definition, and so forth. This unique name will facilitate having dif-
ferent exit programs run from different versions of a product for the same exit point
name.
Security APIs
The OS/400 security APIs allow you to:
Perform many of the security functions through a program interface. You can
use APIs instead of CL commands.
Combine many individual jobs into a single server or overhead job without com-
promising system security.
Network Security APIs
The OS/400 network security APIs provide a means that automatically logs you on
to a server when you request a NetWare** function (for example, file or print). You
can create authentication entries for each NetWare Directory Services** (NDS**)
tree or NetWare 3.x server to which you are authorized. The entry identifies the
tree or server, your name on that server, and (optionally) your password. When
you request a NetWare function, the system attempts to start a connection to the
server by using this data.
Note: To use these APIs, you need the Enhanced NetWare Integration for OS/400
feature.
Software Product APIs
The software products APIs were created to provide the user with the ability to
package and manage their product in a manner similar to the way IBM licensed
programs are managed. OS/400 commands along with these APIs allow you to
work with and create program temporary fixes (PTFs), to package and distribute
products, and to manage software licenses.
For more details on managing a product, see the
System Manager Use
book,
SC41-5321. The System Manager for AS/400 licensed program can be used to
facilitate managing your products.
8-20 System API Programming V4R1