Component - Datamodel - Composition

Entity Relationship Diagram datamodels are implemented via the EAR-datadictionary.

Below the structure of the EAR-files is descibed.

Naming convention.

The names of the EAR-files must comply to the following convention:

Name_Part	Value
model name	XXXX
Underscore-character	_
content type	YYY (ENT, ATR or REL)
Dot-character	.
version	ZZZ

For Example
BST1_ENT.00C
BST1_ATR.00C
BST1_REL.00C

Entitities.

For the entities the following meta-attributes have to be entered:

NAME TYPE ACCESS USER_TYPE ENTITY_TYPE SHORT_NAME
MEMBERS
DESCRIPTION

All entitities are described in 5 records, where fields are separeted by white space.

A record with all ‘=’-characters.
A record with name, type (R), a ‘-‘-character, a ‘-‘-character, a ‘-‘-character and a short_name.
A record, starting with the keyword MEMBER(S):, followed by a list of the members, that have a 1-N relation with the entity.
A record with a name
A records starting with the keyword description, followed by a description.
The entitities file is ended with a record with all ‘+’=characters.

For Example.

===========================================

EMPLOYEE - - - MEW

MEMBER(S): EMPLOYEE_PRIVILEGES

MEDEWERKER

description : Employee data

++++++++++++++++++++++++++++++++++++++++++++

Attributes.

For the attributes the following meta-attributes have to be entered:

NAME TYPE LENGTH MASK(na) ASPECT(na) PICTURE(na)
SCREENNAME
FUNCTIONNAME(na)
DESCRIPTION(na)

The structure of the attributes-files is described below :

All attributes are described in 5 records, where fields are separeted by white space.

A record with all ‘=’-characters.
A record with name, type (C=character, N=numeric, R=real or D=date), a length, an X() field with between brackets the length, a ‘-‘-caharacter, a set of ‘/’-characters.
A record with a name
A record with a name
A records starting with the keyword description, followed by a description.
The attributes file is ended with a record with all ‘+’=characters.

For Example

==============================================================

STATUS C 255 X(255) - ///////////////

STATUS

description : STATUS

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Relations.

For the relations the following meta-attributes have to be entered:

NAME and per attribute
NAME UNICITY dummy(na) dummy(na) dummy(na)

The structure of the relations-files is described below.

All relations are described in a set records, where fields are separeted by white space.

A record with all ‘=’-characters.
A record with the name of the relation (the name must occur in the ENTITIES file).
Per attribute in the relation a record with attribute-name, which must occur in the ATTRIBUTES file, unicity (‘U’=unique,’ –‘=not unique), a ‘-‘-character, a ‘-‘-character, a ‘-‘-character.
The relations file is ended with a record with all ‘+’=characters.

For Example

==============================================================

EMPLYOEE

EMPLYOEE _ID U - - -

EMPLYOEE_NAME - - - -

CREATION_DATE - - - -

SHORT_NAME - - - -

PASSWORD - - - -

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Component - Datamodel - Actions.

With the menu-option check the datamodel can be checked.

If no errors have been found, the DOC-file will contain a list of the tables, with their attributes, owners and members (in our example BST1_DOC.00C).

The GEN-file (in our example BST1_GEN.00C) represents the actual datadictionary file, that will be used as the basis for the generation-process. See Action scripts – Datadictionary-Actions.

The following datadictionary-actions can be used in Action Scripts (See Action Scripts - Datadictionary -actions).

Define the name of the Datadictionary file (FILNAM_DBN, FILNAM_DBV)
Load the datadictionary (GET_DATADIC). The complete datadictionary is loaded into a datadictionary memory structure.
Iterate over datamodel tables (BEGIN_RELATIONS … END_RELATIONS).

In the first iteration the variables of the first table are pointed to. In the next iteration the next table will be pointed to. The number of iterations equeals the table in the datamodel.

In the iterations over tables an iterations over fields can be executed (ATR_BEGIN … ATR_END).

In the first iteratie the variables of the first field are pointed to. In the next iteration the variables of the next field are pointed to. The number of iteration equals the number of fields of the table, that is currently pointed to.

Within iterations substitutions of datadictionary-variables are possible. By combining iterations of the datadictionary with iterations over other objectes complex substitution-actions are possible.

Picture fetch

If you like the header, it can be found here.

Images

If you're using firefox, put your cursor over the logo. But for some reason IE doesn't like image rollover effects. Its not that big of a deal.

Modgen : Component - Datamodel

Info

Custom designs

About the initiator

User Guide Modgen