MKS Implementer 2006 Administration Guide

Glossary
promote \dir2, all files and directories listed in subdirectory 2 are included. On reports
and audits only the directory name (dir2) is listed.
*.*
You can check out or promote the contents of an environment’s directory (including
files, subdirectories, and contents) by specifying *.* for the object name, and a
backward slash (\) for the object code. For example, if you check out or promote
IFS\dir using *.*, all IFS files and directories in IFS\dir are included. Reports and
audits show member/object *.* to indicate that all contents were affected.
implementation object An implementation object is the resulting OS/400 source and objects
created from the generation of an AllFusion 2E model object. For example, a function usually
creates source and objects for a program, display file, and help text. The source and objects
generated for these objects are referred to as the implementation objects.
Implementer Receiver The Implementer Receiver is a component of Implementer that
resides on a remote system. Software can be distributed to the Implementer Receiver.
import An import is the process of restoring LANSA objects from a device or save file
created in an export activity into a different partition.
JDE JDE is the abbreviation for J.D. Edwards (now PeopleSoft World).
keyword restriction A keyword restriction is a facility that restricts access to object code
command keywords. It is used to restrict sensitive keywords, such as the User Profile
(USRPRF) keyword that controls adopted authorities.
LANSA function A LANSA function is an OS/400 executable program created by LANSA
and user-defined.
LANSA objects LANSA objects are objects created in LANSA, such as files, fields, processes,
and functions. They are not necessarily OS/400 objects.
lock A lock is applied to a member/object when it is checked out. The lock is automatically
released when the member object is promoted to a production (*PRD) environment.
A Standard lock is the user action that created the lock through a standard check out.
An Emergency lock is the user action that created the lock through an emergency check
out.
member/object A member/object is a member and/or object under Implementer control.
It can be an object or source stored in a library, an element managed by a CASE tool (such as
AllFusion 2E), or an IFS file. For example, it refers to an object for a data area, but for an RPG
program it refers to the member and object.
model object A model object is an AllFusion 2E object you can check out. AllFusion 2E has
eight object types you can check out: access paths (ACP), applications (APP), arrays (ARR),
conditions (CND), field (FLD), files (FIL), functions (FUN), and messages (MSG).
463