MKS Implementer 2006 Administration Guide

Chapter 3: Implementer Administration
130
Field Description
Object Code Field Descriptions
Activity flag Specify the status of the object code. You cannot check out or create a
request for a member/object using an inactive object code. You can use
an inactive object code for inquiry purposes.
1=Active: Object code is active. This is the default value for most object
codes.
0=Inactive: Object code is inactive. Some infrequently used object
codes are delivered inactive with Implementer.
Object type Specify the type of object associated with this object code.
When this field blank, the object code is referred to as non object based.
This occurs, for example, when you use Implementer to check out non
OS/400 objects such as printed user manuals or source-based items that
only have a source member, such as OCL36 source members.
Object attribute Specify the system attribute of the object associated with this object
code.
Source member type For object codes related to source members or source-based objects,
specify the system source member type. When this field is blank, the
object code is referred to as non source-based.
Match the source member type code of the actual object to what is
defined in Implementer. For example, the source member type for a
reference file defaults to PF (like a standard physical file). To compile the
reference file before the physical file, change this type to PFREF and
specify a lower sequence number.
Default source file For object codes related to source-based objects, specify the name of the
source file. You can override the source file name in Work with
Environments when you define object codes for an environment, or in
Work with User Profiles by specifying the development source files of the
developer.
Creation sequence Specify the sequence to compile members and objects. The value must
be a unique number between 1–ZZZZ. Certain object types require
compiling before others. In general, the logical order is as follows: field
reference files, physical files, logical files, device files (such as display
and printer files), commands, and programs. The object codes delivered
with Implementer use this order.
When automatically assigning object codes in check out or promotion,
Implementer assigns sequence 8000 to IFS directory object codes, and
sequence 8010 to IFS files.
Special characteristics Specify any special characteristics for the object code, such as copy data
only rather than a file, merge messages in message files, or any CASE
related characteristics. Implementer considers these characteristics when
processing the object code.
For IFS files, specify PCFILE. For IFS directories, specify PCDIR.