MKS Implementer 2006 Administration Guide

Appendix D: Glossary
464
model object list Model object list is an AllFusion 2E feature that allows grouping some of
the objects in a model into a named list. For change control purposes, model objects are
checked out to lists to indicate changes were made or are planned. The model object lists are
attached to the AllFusion 2E model and can be selected for AllFusion 2E promotions. Once
you use a model object list for check out, it becomes a change list.
model object name Model object name is the 25-character name given to an AllFusion 2E
model object.
move request Move request is an Implementer task that moves all object/source from the
environments or libraries to the target environments. It performs any request instructions
that impact production data, for example, MRGMSGF. In addition, it moves previous
versions of source and objects to the archive libraries before the move, if specified.
My Workbench My Workbench is a panel that allows developers to perform all necessary
development work. The panel contains the items to be worked on and provides access to all
tools needed to complete the development of the items and move them off the Workbench.
The tools allow you to select and add items to the Workbench, access standard development
tools to edit, compile and test items, and access user-defined tools through user-defined
options. From the Workbench, you can access promotion functions to move completed items
back into production, and book time against projects.
non sequential development Non sequential development is the term used when the lock
for a member/object does not follow the defined, standard development path. Any deviation
from the defined workflow for a specific member is non sequential development. See also,
sequential development and concurrent development.
object code An object code defines a type of object and/or member to be promoted. The
object code in Implementer combines information from the OS/400 object type and source
type. Many object codes are shipped with Implementer and others can be user-defined.
SQL-based objects use specific SQL object codes. For IFS files, the object code is the file
extension.
owning model object The owning model object is the name of a model object that owns
another model object. For example, an access path (ACP) model object is always owned by a
file (FIL) object. Not all model objects have an owning model object.
partition A partition is a division of a LANSA system that has its own field reference files
and processes. Each partition in LANSA is completely independent and no cross-referencing
is allowed across partitions. A partition in LANSA is comparable to an environment in
Implementer.
path A path represents the location of a directory or subdirectory. It is the complete list of
all directories and subdirectories between the root directory and the directory being
identified. The subdirectories in the path are separated by a backward slash (\). For
example, to identify the path of the SYSTEM directory nested in the WINDOWS directory that
stems from the root directory, the notation is \WINDOWS\SYSTEM. See also qualified name
and application path.