public interface AbstractDialogFolder extends AbstractRadicalElement
The Folder entity allows to describe a set of elementary data aggregates, i.e. Logical Views, and the functional relationships between them, thus defining a complex information concept - equipped with access and processing services.
Dependencies between the different Logical Views and data integrity are managed in standard via the Folder.
Functional relationships define the behavior of instances contained in two linked data aggregates.
They are of two types:
- The hierarchical relationships, where an instance of a child aggregate depends on one and only one instance of the parent aggregate.
- Referencing relationships, where an aggregate instance references one and only one instance of the referenced aggregate or none.
Modifier and Type | Field and Description |
---|---|
static java.lang.String |
copyright |
Modifier and Type | Method and Description |
---|---|
java.lang.String |
getCobolFolder() |
java.lang.String |
getCobolProject() |
CobolTypeValues |
getCobolType() |
java.util.List<CPLine> |
getCPLines() |
java.lang.String |
getDestinationFolder() |
java.lang.String |
getDestinationProject() |
Server |
getErrorServer() |
java.lang.String |
getExternalName() |
Library |
getGenerationLibrary()
Indicates the Library on which we can find the generation parameters for the entity. |
java.util.List<GLine> |
getGOLines() |
LockOptionValues |
getLockOption() |
MapTypeValues |
getMapType() |
PaginationModeValues |
getPaginationMode() |
getGCLines
getCalledEntities, getDescriptionTypes, getDesignId, getEntityVersion, getKeywords, getLabel, getName, getPackage, getProject, isResolved
static final java.lang.String copyright
java.lang.String getCobolFolder()
Returns the folder where the cobol is generated.
java.lang.String getCobolProject()
Returns the project where the cobol is generated.
CobolTypeValues getCobolType()
In this field, you have the COBOL variant for the generated Folder.
java.util.List<CPLine> getCPLines()
List of called predefined Macros into the generated program.
java.lang.String getDestinationFolder()
Returns the folder where the proxy is generated.
java.lang.String getDestinationProject()
Returns the project where the proxy is generated.
Server getErrorServer()
Returns the Error message Server
java.lang.String getExternalName()
The name entered here is the name of the file generated from this instance. The generated file name can then differ from the instance name.
Library getGenerationLibrary()
Indicates the Library on which we can find the generation parameters for the entity.
Parameters are related to the adaptation to the operating system in use.
java.util.List<GLine> getGOLines()
The GOLines indicates the list of the generation options.
Some options are mandatory : LOCATION
LockOptionValues getLockOption()
The upload-download mechanisms used in the management of Folders increase the time taken between the reading of the initial image of a Folder and the return of its updated image.
In this context, a lock process may adequately prevent simultaneous updates on the same Folder occurence. In this manner, the coherence of accumulated updates is enured.
You have the choice between two locking options : pessimic mode and optimistic mode.
- The pessimistic lock mode (P) creates an exclusive appropriation of the Folder wich is locked to all others users during updating.
- The optimistic lock mode (O) is triggered only when the update is requested and compares the initially loaded Filder image with its current image in the database. If they are identical, the update is accepted.
MapTypeValues getMapType()
In this field, you have the variant of the TP monitor for the generated Folder.
PaginationModeValues getPaginationMode()
You can choose between two paging modes:
- Non-extend mode (N) allows to page forward and backward through a predefined population. Each paging operation (forward or backward) executes a read request and its result replaces that of the previous read.
- Extend mode (E) allows you to page forward through a predefined population, and the result of each paging adds to the preceding read. The reading of the previous pages is the handled by the graphic client.