access path
A view of the data in a physical file, in a given key sequence, implemented as an i OS physical or logical file.
access path format entry
A process that establishes which fields are present in the access path, which of those fields are key fields for the access path, and the order of those key fields.
access path relation
The set or subset of a file’s relations that apply to a particular access path.
access path types
Types which differentiate the functionality of the various access paths. The types of access paths include Physical, Update, Retrieval, Resequence, Span, and Query.
action bar
A construct that appears at the top of an end user panel. It provides a set of choices which define the actions available to the end user.
action bar choice
An option that allows application users access to the actions available for the panel.
action diagram
A notation for defining and showing procedural processing logic. It is made up of a number of basic logic constructs: Iterative, Sequential, and Conditional. Most functions have an action diagram associated with them.
action diagram editor
A facility that lets you modify the default processing logic automatically supplied for a function by adding action diagram constructs at specified user points.
All Objects Model Object List
A unique list within a model that contains an up-to-date detailed model object description for each model object in the model. A model object’s description is updated automatically whenever it changes. It is also referred to as *ALLOBJ.
animation
A process that converts a device design to a Toolkit panel design that you can use to interactively simulate (prototype) a system design. This is useful for demonstrating a design to end users to ensure that the design meets operational requirements before you begin programming.
application
A set of implementation objects, primarily programs and files that together satisfy business needs. For example, a payroll application or an order entry application.
attribute
A property of an entity. It is any detail that qualifies, identifies, classifies, quantifies, or expresses the state of an entity. Attributes are usually implemented as fields.
based-on file
The file to which a given object is attached.
built-in function
Type of function which provides commonly required low level operations such as addition and multiplication.
capture file
One of the two types of database files. Capture files generally contain transaction data.
change type
The change type indicates the impact a change to a model object has on other model objects. The change type indicates whether impacted model objects require editing and/or regeneration to ensure the integrity of the model and the application.
component change processing
An automated impact analysis tool that determines how a change to a model object affects other objects in the model and records whether the affected objects need to be edited or regenerated.
condition
A value that specifies the circumstances under which an action or set of actions are to be executed. It also defines the particular value for a field.
conditional construct
A construct that allows steps to be conditionally executed within the action diagram logic and generally conforms to nested IF THEN ELSE logic statements or SELECT sets.
construct
The system of notation in an action diagram to define a boundary for procedural logic.
context
The source of a field within a function. A particular field name can be present several times in a function. The context of the field differentiates between these instances of the field. For example, a field may appear on a panel and also be part of a database file.
cross reference facility
The operations provides for identifying dependencies between objects. This is also referred to as the model object cross reference facility.
current version
This refers only to versions of functions or messages. A version is current when it is the version that is active in the model. In other words, the current version is the one used by and referred to by other model objects and is the one shown on panels that are not specific to processing versions. Only one version in a group of versions can be current at a time.
data model
A representation of the information used by a business. A data model contains groups of data called entities, attributes of the entities, and the relationships between those entities or between an entity and an attribute.
database function
An internal function which reads or updates the database. The database functions are: Change Object (CHGOBJ), Retrieve Object (RTVOBJ), Create Object (CRTOBJ), and Delete Object (DLTOBJ).
design model
The library that holds the i OS database files that compose the model. The model library has an associated library, the generation library, which contains the source code generates for the model.
design object
See model object.
designer
The user type that can change any aspect of the design model including data relationships and functional specifications. In general when a designer is using a model, no other user can access that model. A designer also has the authority to lock and unlock objects. Also known as *DSNR.
developer
A term used to designate either a designer (*DSNR) or a programmer (*PGMR) when a distinction between the two user types is not necessary. Designers and programmers are often referred to collectively as "developers."
device design
The layout of a panel or report associated with a function.
device function
A function which has a device design associated with it, such as Edit Record (EDTRCD), Display File (DSPFIL), Edit Transaction (EDTTRN), and Print File (PRTFIL).
domain
A set of possible values an attribute can take, along with its definition of length and data type, such as numeric or alpha.
dynamic selection
An option that specifies that all records are included in the access path regardless of any select/omit criteria. The records are then filtered by the system as they are read by a program.
end user
The person who uses the generated application once it is in production.
entity
An object which is significant or relevant to the business it represents; for example, a company, a person, a product. An entity is a potential file to be created in the data model of your application system.
entity-relationship diagram (ERD)
A graphic chart used to record the entities and entity relationships using boxes, lines, and notation.
expansion
The process of resolving all relations for a file or for all files in a model. For example, synchronizing a model causes the expansion of all relations to rebuild the file entries for all files in the model.
external function
A function which is implemented as a separate HLL program rather than as a subroutine. All functions are either external or internal.
field ()
A description of an item of data. It must have a name and a field type. Field names may be up to 25 characters long. The names of fields must be unique within the design model.
field type
An assigned type which defines the type of data that the field represents; for example, a number or a date.
file ()
A list of relations that describe an entity. can automatically resolve the relations into a list of file entries or fields. File names may be up to 25 characters long. The names of files must be unique within the model.
file entry
A field that arises as a result of resolving relations. An entry indicates the presence of a field on a file. The three types, depending on the type of relation from which the field is resolved, are: key field entry, attribute entry, and virtual field entry.
file type
The description of how the file will be used. Each file must be one of the allowed file types: structure (STR), reference (REF), or capture (CPT).
first normal form (1NF)
The normalization rule that eliminates repeating groups of data from an entity.
foreign key
A file entry that is the result of a relationship between two entities. The relationship is defined by a non-key attribute of one entity that exists as the primary key of the other entity.
function
A template process that operates on a file or field. A function serves as a building block with which to design applications.
function field
A field whose value is not physically stored in the database but is derived from other fields or files. Function fields can be placed on device designs and used in action diagrams.
function options
The optional features of the standard functions.
function parameter
A field whose value is passed into or out of a function when it is executed. Each parameter can have a parameter role and a parameter usage.
function parameter role
The parameter role that specifies how a parameter is to be used in a function into which it is passed. Standard parameter roles include Restrictor, Positioner, Map, and Vary.
function parameter usage
The parameter attribute that specifies whether a function parameter is to be passed to and/or returned from a function. Function parameter usage includes Input, Output, Both, and Neither.
function redirection
A process whereby the using objects of a given function (FUN) or message (MSG) are redirected to use an alternative FUN or MSG. This occurs when you make a version of a function or message current.
function type
One of a group of process templates provides such as EDTFIL.
generalization
The process during data modeling of combining two entities of the same class into one entity and renaming it.
generatable objects;defined generation
The creation of application source code from a function definition and device design.
generation library
The library that holds generated source code, compiled objects, and help text for a model.
group
This term relates to versions of functions or messages. Versions of the same model object form a group of versions.
i OS
The IBM i operating system.
impact analysis
The process of determining the impact of a proposed or actual change to model objects in order to ensure the integrity of a set of changes by identifying and including dependent objects. impact analysis tools include, cross reference commands, interactive panels to determine usages and references, simulation, and automated component change processing.
implementation
The process of setting up your application and moving it into production once you have generated and compiled source objects.
implementation objects;defined implementation object
Objects such as generated source and compiled objects as opposed to model objects. They are also known as traditional or 3GL (third generation language) objects.
internal function
A function which is generated as in-line code within the calling function.
involution
A process that occurs when an entity refers to itself. This is known as an involuted relation. Also called a self referencing relation.
iterative construct
A programming construct that represents repetitive statements or loops that will be implemented as REPEAT WHILE logic within the main action diagram logic.
key
The field(s) used to uniquely identify a record in a file.
list entry
This is another term for model object list entry.
logical file (i OS)
A logical view of the data in the physical file based on key sequence. Access paths can be implemented as logical files.
message function
Function types which allow you to send error, status, or information messages to the invoking program or to send information to other destinations such as submitting a job to batch.
model object
design objects such as, access paths, functions, and fields, as opposed to implementation objects such as, generated source or a compiled object.
model object description
A reference to a model object in the All Objects list (*ALLOBJ). It contains detailed information about the actual model object. A model object’s description is automatically updated whenever the model object changes, and as a result, always reflects the current state of the object.
model object list
A list of references to model objects.
model object list entry
A reference to a model object in a named model object list. It reflects the state of the model object at the time the list entry was created or refreshed, and as a result, provides an historical record of the model object.
model profile
A user profile associated with a model where you can define defaults for various processes and file specifications for an interactive session.
model value
A specific value for a model that controls particular features of the interactive use of , code generation, or implementation.
normalization
The process of eliminating data redundancy using specific standards and rules in data modeling.
notepad
A temporary action diagram which can be used to copy constructs between action diagrams.
object ()
A design element of a model; for instance, a field or function. See also model object.
object type
Each object must belong to one of the object types: file, field, condition, message, function, access path, or application area.
open functions
All functions a single user currently has open for editing.
owning model object
Certain object types exist associated with an owning type. For example, functions (FUN) and access paths (ACP) are owned by a file (FIL) object type.
panel
A panel is displayed by a device function. Panels are composed of a header, a footer, and a body.
panel entry
The appearance of a field on a panel device design. Panel entries arise either from the resolution of access path relations, from function parameters, or from explicit specification by the application user.
parameter
See function parameter.
primary key
A chosen attribute or group of attributes assigned to a particular entity to uniquely define it within an entity relationship model.
program
The result of generating and compiling a function.
programmer
A user type who can create, change, and delete any help text, access paths, functions, and arrays, including working with action diagrams and field conditions for database and function fields. A programmer cannot alter the database files or fields. In general, programmers cannot use a model while a designer is using it. Also known as *PGMR.
prototyping
The presentation of a realistic mock up of a system used to verify that the design meets the operational requirements.
redirection
See function redirection.
reference file
One of the two types of database files: Reference files contain static data, in contrast to capture files which contain volatile transactional data.
references
The references for a model object are all objects the model object refers to, or contains. For example, an internal function is a reference of the external function that contains it. In other words, references are the model objects the referring model object requires in order to be complete or to exist.
referential integrity checking
The process that ensures that proper relations between files are maintained. This usually means making certain foreign keys contain valid values in the referenced files. functions generate source code by default to provide referential integrity checking.
relation
A connection between one entity and another or between an entity and an attribute. When specified in , a relation defines the connection between files or between a file and a field in the file.
relation type
A relation must be one of a fixed number of types; the type is indicated by the verb used to represent the relation such as Has or Known by.
restrictor parameter
One of the allowed function parameter roles. If a function has a restrictor parameter, it can only process database records whose keys match the restrictor. Any device design is modified automatically to meet restrictions. Restrictor parameters must be key field entries on the access path to which the function is attached.
second normal form (2NF)
The normalization rule that eliminates attributes that are not dependent on the primary key. In 2NF, non-key attributes are fully functionally dependent on the primary key.
select/omit set
A choice that defines criteria for the inclusion or exclusion of records from the physical file.
sequence construct
The simplest action diagram construct which specifies a list of actions or other constructs that are to be executed sequentially.
session list
A model object list to which all objects you change during a session are logged.
simulation of a change
A process that lets you see the impact of a proposed change to a model object on other objects in your model before you actually make the change.
source file (i OS)
A file specially formatted to contain program source code. It is usually multi-member with each member containing a different set of source.
standard function
A function which specifies entire programs (external functions) or subroutines (internal functions). There are three main classes of standard functions: device functions, database functions, and user functions.
static selection
An option that specifies that only those records that satisfy select/omit criteria are included in the access path.
subfile
The part of a panel that contains a repeating detail format such as that needed for a list longer than one page.
subfile selector
A field on the left hand side of a subfile used for specifying an action to be taken against a particular subfile record or records. For device designs there will normally be a subfile selection value explanation text field to explain the allowed values for the subfile selector.
synchronize a model
The expansion of relations to rebuild the file entries for all files in the model.
third normal form (3NF)
The normalization rule that eliminates non-key dependencies between attributes of an entity. In 3NF, non-key attributes are mutually independent.
unique key
A file key that ensures each record in the file is unique.
usages
The usages for a model object are all objects that use the model object. They are also called using objects.
user
A user type that is limited to viewing the model and cannot change it. Also known as *USER.
user function
A function that is entirely user specified.
user point
A point in an action diagram at which you can insert logic. A user point is indicated by an arrow on the far right in the action diagram editor.
version
A model object that originated as a copy of either a function (FUN) or a message (MSG). Versions of the same originating model object are linked together to form a group of objects.
virtual field
A field that is logically, but not physically, present on an access path. Virtual fields are the result of specifying that fields in a related file are to be included on an access path.
virtual field entry
An entry which describes the presence of a field on a file or access path as a result of a join with another file. Virtual fields can only be specified for the Owned by, Refers to, and Extended by relations.
window
A panel on which information appears that is not necessarily a full panel. Windows can be varying sizes and can be positioned in varying locations.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|