Object (IBM i)

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Object" IBM i – news · newspapers · books · scholar · JSTOR (December 2009) (Learn how and when to remove this message)

On many computing platforms everything is a file, but in contrast in IBM i everything is an object.^[1]

IBM i objects share similarities with objects in object-oriented programming, but there are differences as well. There are similarities in that when storage is allocated for something, that something is of a specific type, and only a specific set of programs are allowed to act upon that object. There are differences in that IBM i objects cannot be inherited, and the set of object types is fixed, and only IBM has the ability to create new ones.

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 Control Language for more information.
• *MENU: Menu (accessed with the GO command).
• *FILE: File (IBM i 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).

A library (*LIB) on IBM i is an object that is used as a system directory to keep track of other objects. Objects are not stored inside libraries, but rather libraries are used as namespaces for objects. Libraries are a "system" object, and therefore only one instance of any given Library "name" is possible. They're made to appear as if they're stored in the QSYS library.

Generally speaking all libraries created by IBM for use by the operating system begin with the letter 'Q'.

IBM Standard Libraries:

• QSYS - System Parent Library
• QSYS2 - System Library for CPI's(Characters Per Inch)
• QHLPSYS - Online Documentation Library for Users
• QTCP - TCP Connectivity Utilities
• QAFP - Advanced Function Printing
• QGPL - General Purpose Library
• QTEMP - Job specific temporary Library (deleted when the job ends)

A library list (*LIBL) is an object which specifies a default set of locations to look for an object (similar to the PATH mechanism of other operating systems). This object doesn't exist on its own and is always associated with another object like a job or a job description (*JOBD). Some job descriptions specify the special value *SYSVAL which means that the library list can be found in the system value QUSRLIBL. As of OS/400 V5R1, the user portion of the Library List can contain up to 250 library names. Prior to that it could only have 25 libraries.

A job's library list consists of four sections:

• System portion: Always at the top and contains system libraries like QSYS, QHLPSYS, QUSRSYS, etc. The system portion can hold up to 15 library names. The default contents of the system portion are specified in the QSYSLIBL system value. The contents of the system portion can be changed for the current job to differ from QSYSLIBL by using the CHGSYSLIBL command.
• Product portion: When a CL command is executed that specifies a production library, that library will be added to the product portion of the library list for the duration of the command. It follows the system portion and the O/S will maintain up to two libraries in it.
• Current library: Is a special library associated with a user profile and there can only be one in the list at a time. This library is useful for programmers to have their personal library at the top of the list regardless of what the user portion is changed to. It can be changed locally using the CHGCURLIB command. To change it for the user on all future jobs use the CHGUSRPRF command.
• User portion: The last part of the library list that contains all of the application libraries. The list is normally assigned to the job from the job description but for batch jobs this can be overridden using the SBMJOB command's INLLIBL parameter. A job's library list can be changed locally with the EDTLIBL(Edit Library List), CHGLIBL(Change Library List), ADDLIBLE(Add Library List Entry), and RMVLIBLE(Remove Library List Entry) command.

• AS/400 Objects