Access
To work with the logical entities in the current application area or generate the Physical Data Model for each entity, select the Logical Entities tab of the LDM/PDM screen.
There are two types of logical entities:
those resulting from LDM generation, having therefore a conceptual origin (conceptual entity or relationship);
those purely logical, which were created at the logical level.
Lists
Logical entities
Alphabetical list of logical entities of the current application area, with their names and descriptions, as well as the names of the relevant physical and logical files.
By default, this list is shown in alphabetical order of the logical entity names.
You can use a filter above the list to restrict what is displayed.
Multiple-selection list.
With correction environments, a check mark can precede each logical property name.
A red check mark shows that the entity is being held by the default correction.
A black check mark shows that the entity is being held by a correction other than the default correction.
Context-sensitive menu
The following options are accessible at all times via the context-sensitive menu.
In addition, there may be buttons to perform the same actions on the right-hand side of the window, depending on the settings in the Create/Modify a software engineer dialog box's Preferences tab.
Create
This option opens a dialog box which is used to create "purely" logical entities.
Modify
This option opens a dialog box which is used to display or modify the general characteristics of the selected logical entity.
This option is not active when no logical entity is selected in the list.
Delete
This option opens a message box for confirming the final deletion of the selected logical entities.
When the deletion is validated, the list of logicial entities is updated accordingly.
This option is not active when no logical entity is selected in the list.
Properties
This option opens a dialog box that lets you create (based on conceptual properties), edit, delete, sequence or print the logical properties of the selected logical entity.
This option is only enabled if one or more logical entities are selected in the list.
Copy
This option opens the dialog box which is used to copy a logical entity of the current application area.
It is not active when no logical entity is selected in the list.
Accesses
This option displays the accesses of the entities selected in the Accesses tab.
It is not active when no logical entity is selected in the list.
Constraints
Displays the integrity constraints management dialog box for the selected entities.
This option is only enabled if one or more logical entities have been selected from the list.
Constraints referencing the entity
Displays the list of foreign key constraints referencing the selected entities.
This option is only enabled if one or more logical entities have been selected from the list.
This option prints the characteristics of the selected logical entities.
The printing job is submitted to the Job manager.
This option is not active when no logical entity is selected in the list.
Secure
This option secures the entity, after confirmation.
The DDS code, the guide word, the associated DDS code and the associated guide word of the entity's properties, can no longer be modified by the LDM generation. This also affects the file name, the format name and the logical file name of the entity.
This option is not active when no logical entity is selected in the list.
Unsecure
This option unsecures the entity, after confirmation.
The DDS code, the guide word, the associated DDS code and the associated guide word of the entity's properties, can again be modified by the LDM generation. This also affects the file name, the format name and the logical file name of the entity.
This option is not active when no logical entity is selected in the list.
Note: The system recreates these names at once, so that they correspond to the names which would be issued from the LDM generation.
Attach
This option opens a dialog box which is used to attach logical entities of the repository to the current application area, by creating a link between these entities and the application area.
Detach
This option detaches the selected logical entities from the current application area. These logical entities may be re-attached by means of the Attach button.
This option is not active when no logical entity is selected in the list.
Logical servers
This option opens a dialog box which is used to modify the logical servers associated with a logical entity. It is not active when no logical entity is selected in the list.
Cut origins
Totally
The entity and the properties become purely logical.
Partially
The entity becomes purely logical. Logical properties are still linked to the conceptual properties; they become redundant properties.
Create from conceptual
This option opens a dialog box which is used to create - "in series" - logical properties based on conceptual properties.
This option is not active when no logical entity is selected in the list.
Application areas
This option opens a dialog box used to show the application areas to which the logical entity is attached. It also lets you attach and detach the logical entity to and from application areas.
Hold
This option opens a dialog box enabling the selected logical entities to be held by the default correction.
This option is only visible in correction environments.
It is only active when one or more logical entities are selected in the list and the user has a default correction.
Generation
List
Generation
Type of the database which is to be generated.
Possible values:
AS/400 native |
Generation of the Physical Data Model in the form of AS/400 files. |
Btrieve |
Generation of the Physical Data Model in the form of Btrieve files for Windows. |
AS/400 SQL |
Generation of the Physical Data Model in the form of AS/400 SQL tables. |
DB2 |
Generation of the Physical Data Model in the form of DB2 UDB SQL tables. |
Oracle |
Generation of the Physical Data Model in the form of SQL Oracle tables. |
SQL Server |
Generation of the Physical Data Model in the form of SQL Server tables. |
Access |
Generation of the Physical Data Model in the form of Access SQL tables. |
MySQL |
Generation of the Physical Data Model in the form of MySQL SQL tables. |
| PostgreSQL | Generation of the Physical Data Model in the form of PostgreSQL SQL tables. |
Note: The values presented in the list depend on the licence you own, and on the setup defined in the environment attributes.
Radio buttons
Database
The file will be generated directly in the database.
This button only appears if the generation type is not Native AS/400.
Generic script
The file will be generated as a generic script file.
This button only appears if the generation type is not Native AS/400.
SQL script
The file will be generated as an SQL script file.
This button only appears if the generation concerns an SQL database.
Data entry
File
Full name of the generated script file.
The file is generated on the client machine (generic scripts) or on the machine that runs the job manager (SQL scripts).
Data entry is only possible if the generation type is not Native AS/400 and either the "Generic script" or "SQL script" radio button is selected.
Check boxes
Create new file
Checked |
Creates a new script file. |
Not checked |
Adds the DB queries to the existing script file. |
This check box is only active if the generation type is not Native AS/400 and either the "Generic script" or "SQL script" radio button is selected.
Generate with key
Checked |
Generation of physical files with key. |
Not checked |
Generation of physical files without key. |
The generation of a physical file without key implies the generation of a logical file whose name is specified when defining the logical entity.
Default: box not checked.
Generate integrity constraints
Checked |
Generates the integrity constraints. In this case, the Generate button displays a window that lets you select the integrity constraint generation parameters. |
Not checked |
Only the entity is generated. |
This check box is only visible when an SQL generation mode is selected.
By default: unchecked.
Format the script
Checked |
Generation of a formatted script using a syntax compatible with the DBMS concerned. |
Not checked |
Generation of a script in which each query is expressed on a single line, with no separators (script compatible with previous Adelia generations). |
The SQL scripts can be generated in a readable indented form - with a query separator – that can be directly interpreted by the standard execution tools corresponding to the DBMS selected (sqlplus for Oracle, Query Browser SQL Server, etc.). Adelia tools can correctly interpret these scripts also (see the Database management tool topic) by analyzing the data provided in the script header comment.
Default value: checked.
Save data
This check box starts the generation of the Physical Data Model while saving the data of the existing Physical Data Model.
Checked |
Generation with the saving of existing data. |
For AS/400 generation, the data is saved in the HS#QTEMP library. |
|
For Btrieve generation, the data is stored in a file whose name will be indicated if a problem occurs (in order to allow data retrieval). |
|
Not checked |
Generation without saving of existing data. |
Buttons
Details
This button opens a dialog box that lets you display or edit a logical entity's specific generation characteristics.
It is only active if one or more logical entities are selected in the list.
Generate
This button starts the Physical Data Model generation for each entity selected in the list.
It is only active if one or more logical entities are selected in the list.