Object Types

The number of object types is huge and a small subset of them are available to users. The human
readable form of the object type is always a three to six character mnemonic preceded by an
asterisk. What follows is a short list of the more commonly used objects and their mnemonics:

*LIB: Library (where everything below, except directories and stream files, is stored;
libraries cannot exist within other libraries)

*PGM: Program (for compiled languages: CL, RPG-IV, C, C++, COBOL, etc. and there
are no interface restrictions between the languages).

*MODULE: Module (linkable into a program from a compiled language above and here
too there are no restrictions on linkability between languages).

*SRVPGM: Service program (dynamic set of one or more modules, akin to a DLL file in
Microsoft Windows).

*BNDDIR: Binding directory (holds a list of modules and service programs and is used
when creating programs).

*CMD: Command (an object used for calling programs that allows users to prompt for
their parameters; can be created with the Command Definition language). See AS/400
Control Language for more information.

*MENU: Menu (accessed with the GO command).

*FILE: File (AS/400 files can be used for data, input/output devices, and source code,
depending on sub type).

*DTAARA: Data area (small bits of storage used to store tiny items of data for fast
access).

*DIR: Directory (part of the Integrated File System that is equivalent to Unix and
Microsoft Windows hierarchical file systems).

*STMF: Stream file (traditional file that would be familiar to most Unix and Microsoft
Windows users and only stored in directories)

*JRN & *JRNRCV: Journal and journal receiver (used to journal changes to files, data
areas, and stream files).

*USRPRF: User profile (allows users to sign-on to the system).

 *JOBD: Job description (used when submitting/starting jobs).

*SBSD: Subsystem description (used when starting subsystems; this is the place where
user jobs run).

*JOBQ: Job queue (used to queue up batch jobs to run in a subsystem).

*LIND: Line description (communications line: Ethernet, token ring, etc.).

*CTLD: Controller description (communications controller for lines, workstations, etc.).

*DEVD: Device description (communications device for lines, workstations, printers

tape drives, etc.)

*DTAQ: Data queue (used to queue up data entries for fast retrieval by other jobs).

*MSGQ: Message queue (used to send message to users, can also be used like a data
queue).

*OUTQ: Output queue (used to queue up output to a printer).

*USRSPC: User space a generic data-containing object of arbitrary size (up to 16T).

Library

A library (*LIB) on the AS/400 is an object that is used as a system directory to keep track of
other objects. AS/400 objects are not actually stored in libraries. Theyre really nothing more
than namespaces, but its easier to refer to an object as being in or stored in a library.

Certain types of the AS/400 object (database file, storage areas and executable program objects)
can be compiled, copied, and stored into/from many different libraries concurrently, with the
Library List hierarchy determining which instance of the object to use during execution of any
application that utilizes that object name. There are AS/400 commands to help move objects
around, and objects may be qualified at compile time to point to specific other objects statically
at runtime, in order to circumvent the Library List.

Libraries cannot contain other libraries

The AS/400 uses a library in much the same way that personal computers use directories.
Libraries and directories are holding areas for related material. For example, one library might be
dedicated to payroll programs, another to inventory control. Libraries generally contain many
other objects. Unlike directories, however, libraries cannot contain other libraries (with one
exception library QSYS, discussed below). AS/400 is structured as a list, the opposite of
Windows which has a tree-like structure. To find an AS/400 object requires the name of the
library and the name of the object. The AS/400 identifies objects by their qualified name, which
takes the form LIBRARY/OBJECT. For example, to reference the EMPMASTER file in the
PAYROLL library, youd usually refer to PAYROLL/EMPMASTER.

System Library

Other types of objects, designated as system objects cannot be replicated. Libraries are a
system object, and therefore only one instance of any given Library name is possible.
Theyre made to appear as if theyre stored in the QSYS library. Other system objects include
user profiles (*USRPRF), configuration objects (*LIND, *CTLD, *DEVD), etc..

IBM Standard Libraries:

QSYS system library for the AS/400. It contains the programs and other objects that
make up the operating system. QSYS must exist on an AS/400 for the system to work.
Other libraries on the AS/400 exist within the context of the QSYS library; it is the only
library that can contain other libraries. A few special objects, such as user profiles and I/O
configurations, can exist only within QSYS. You should never modify or delete any
object within the QSYS library.

QSYS2 System Library for CPIs.

QHLPSYS Contains on-line help information that is displayed when the Help key or
the extended help function keys are pressed.

QTCP TCP Connectivity Utilities.

QSPL holds the spooled, printed output pages that have not yet been printed.

QAFP Advanced Function Printing.

QGPL General Purpose Library that contains IBM-provided objects. The system places
newly created objects that are not specifically placed in a distinct library in QGPL.

QTEMP Job specific temporary Library (deleted when the job ends), Each time a user
signs on, the system creates a QTEMP library for this interactive job. If the user submits
a job to the batch queue, another QTEMP library is created for the batch job.