For Objects

When naming OS/400 objects, the components are as follows:

Application identifier (S AMMMMOX): S Identifies the user system.Only one letter is used since there will be relatively few application systems, and the objects that compose the systems are in any case likely to be separated into different libraries. For example:
I = Inventory management system
Application Functional group (S A MMMMOX): A identifies the functional subsystem of the application.This letter is used to group all objects belonging to a significant functional group within an application. It is possible that there is only one functional group if it is a small application. For example:
T - Transaction entry subsystemO - Order entry subsystemA - Accounts subsystem
Mnemonic (SA MMMM OX): MMMM is a mnemonic, normally made up of two elements (MM + MM), chosen according to the rules described below. For example:
SLBT = Select batch.CUDA = Customer dataDSCU = Display customers
Type (SAMMMM O X): O, a single letter indicating both the OS/400 object type and the attribute. It can be any one of the following:

Object Type	Attribute
A	Data area or physical file defining a data area
B	BASIC program or display file used by BASIC program
C	CLP program or display file used by CL program
J	C program or display file used by C program
D	DFU program or display file used by DFU program
H	Panel group
$	Printer file used in common
K	COBOL program or display file used by COBOL program
I	PL/1 Program or display file used by PL/1 program
L	Logical file
M	DDM file
P	Physical file
Q	Query program
R	RPG III program or display file used by RPG program
T	Tape file

Subtype (SAMMMMO X): X is an optional suffix, whose nature depends upon the object type.

As program suffixes, the following have special meanings:

As file suffices, the following have special meanings:

For example, Display Customers display file: LUDSCUR#; Display Customers command processing program: LUDSCUC@.