Filter
Top Products
The CD-ROM premastering APIs could be used if you currently produce distributed
systems license option (DSLO) distribution tapes at a central site. If you would now
like to distribute on CD-ROM rather than tape, you would use the CD-ROM pre-
mastering APIs.
You would use the Handle CD-ROM Premastering State (QlpHandleCdState or
QLPCDRST) API to place your job into a CD-ROM premastering state. While in
this state, any save operations performed will have information about the tape file
sizes stored away for future use in generating the QDSETMAP file. In the case of
a SAVSYS or option 40 (Create Distribution Tape) on the Work with Licensed Pro-
grams menu, special files are saved to tape so that the CD-ROM volumes
produced can be used for installation.
When the save operations have been performed, you would then use the Generate
CD-ROM Premastering Information (QlpGenerateCdPremasteringInfo or
QLPCDINF) API. This API is used to analyze the tape file size information stored
away during the previous API and produce a byte-stream file that contains informa-
tion about which CD-ROM volumes these files will reside on. Information is also
returned into a user space that is useful in producing a mastering control file that
may be necessary when having the CD-ROMs mastered.
UNIX-Type APIs
The UNIX-type APIs are intended for experienced UNIX programmers who want to
do either of the following:
Create new application programs that run on the AS/400
Create an AS/400 version of existing application programs that run on other
UNIX-based systems
The UNIX-type APIs consist of the following groups.
Environment Variable APIs
Environment variables are character strings of the form name=value that are
stored in an environment space outside of the program. The strings are stored in a
temporary space associated with the job.
Environment variables can be set using the putenv() or Qp0zPutEnv() function.
They can be retrieved using the getenv() or Qp0zGetEnv() function. The putenv()
and getenv() functions are designed to meet the X/Open** single UNIX specifica-
tion (formerly Spec 1170). The Qp0zPutEnv() and Qp0zGetEnv() functions are
AS/400 extensions to the industry-standard APIs. They provide the additional
capability to store or retrieve a coded character set identifier (CCSID) associated
with the string.
After environment variables are set, they exist for the duration of the job. There is
no way to remove an environment variable. However, the value can be set to
NULL by using a subsequent call to putenv() or Qp0zPutEnv() and specifying a
value of NULL.
The OS/400 support for environment variables does differ from the usual behavior
of environment variables on UNIX systems:
There is no default set of environment variables provided when a job starts.
On the AS/400, the environ array, which points to the environment variable
Chapter 8. Use of OS/400 APIs 8-21