02.05.2013 Views

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Glossary<br />

DLO Document Library Object (DLO) refers to a file or folder that exists in the QDLS file<br />

system on an iSeries. These objects, referred to in <strong>Implementer</strong> as IFS objects, are supported<br />

for change management. See also IFS object, IFS file, and IFS directory.<br />

document A document is a special type of file created by OfficeVision/400 and stored in the<br />

QDLS space. A document is a file, but a file is not necessarily a document. It is the OS/400<br />

term for any object residing within an IFS folder on the iSeries. Within <strong>Implementer</strong>, the term<br />

IFS object is used.<br />

environment An environment identifies a collection of libraries, object owners, authorized<br />

users, and rules about how the libraries are controlled by <strong>Implementer</strong>. See also related<br />

environment.<br />

environment ID An environment ID is a sequential number assigned to each target<br />

environment on a promotion request. The number, which starts at one and increments by<br />

one, is used for naming some libraries, save files, and other objects used as part of the<br />

promotion request.<br />

environment library list Environment library list is a list of up to 250 libraries used for<br />

compilation in the environment. Of these, 248 entries are available for your use. The last two<br />

entries are reserved for QTEMP and the <strong>Implementer</strong> work library on the promotion request.<br />

The environment library list is used also when processing special commands for a request.<br />

environment type An environment type defines whether an environment is for production<br />

(*PRD), quality assurance (*QAC), or development (*TST). It enforces check out an<br />

promotion restrictions and ensures the developers do not attempt to copy members/objects<br />

from one production environment to another.<br />

export An export is the process of saving LANSA objects into a device or save file to move<br />

them from one LANSA partition to another, on the same or different system.<br />

export list An export list is a named list of LANSA objects to be exported from one LANSA<br />

partition to another. There are two types of lists provided by LANSA: One is visible to<br />

LANSA users and maintainable within the LANSA menu. The other is not visible to you but<br />

provided for object management vendors. <strong>Implementer</strong> creates an export list whenever it<br />

copies LANSA objects from one partition to another partition.<br />

file A file refers to the support <strong>Implementer</strong> provides for traditional OS/400 files and<br />

objects in the IFS (referred to as IFS files). To avoid confusion, whenever an IFS file object is<br />

referenced in <strong>Implementer</strong>, the term IFS file is used.<br />

<strong>Implementer</strong> supports all traditional OS/400 files, for example, physical files, logical files,<br />

display files, message files, printer files, SQL tables, and SQL indices and views. See also IFS<br />

file.<br />

folder A folder represents the OS/400 term for a collection of documents in a single<br />

location. The term is used as part of support <strong>Implementer</strong> provides for IFS objects. It<br />

corresponds to IFS directory. See also IFS directory.<br />

461

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!