In the -CS Lines tab of the Server and Server Dialog editors, for each Data Element called in a Business Component, you must indicate, in the Data Element call:: the processing category (before repetitive, repetitive, and after repetitive), the type of logical access processing (validation, update and selection) to perform on the Segment, the key filling mode, the use in the generated processing, and the access condition.
Segment that belongs to the Screen top.
Segment that belongs to the repetitive category (as many times as there are repetitions),
Segment that belongs to the Screen bottom.
Options | Description |
---|---|
No value or N: | For an organization different from X:
No access statement is generated for this Segment in the validation
and update processing (default). For an X organization: No Server call is generated. |
L: | For an organization different from X:
A simple read command is generated for the Segment. For an X organization: Server call for selection. |
E: | For an organization different from X:
Existence validation to run. A read command with the setting of an
error code is generated (if it is not found). For an X organization: Server call for validation. |
M: | For an organization different from X:
Updated Segment (modification only). For an X organization: Server call for validation and update. |
X: | For an organization different from X:
Updated Segment (creation and modification only). For an X organization: Server call for validation and selection |
S: | For an organization different from X only: Updated Segment (deletion only). |
C: | For an organization different from X only: Segment (deletion only) |
T: | For an organization different from X:
Updated Segment (creation, modification, and deletion). In these
cases, the existence validations and the update statements corresponding
to the selected options are generated. If the Segment is related to a previous Segment, regardless of the indicated use, only the update commands for modification and creation are generated. For an X organization: Server call for validation, update, and selection. |
U: | For an X organization only: User-defined logical accesses |
Options | Description |
---|---|
No value or N | For an organization different from X, S,
and 2: No access statement is generated for
this Segment in the validation and update processing (default).
For an X or 2 organization: No Server call is generated. |
L: | For an organization different from X, S,
and 2: A simple read command is generated for
the Segment. For an X or 2 organization: Server call for selection. |
E: | For an organization different from X and 2:
Existence validation to run. A read command with the setting of an
error code is generated (if it is not found). For an X or 2 organization: Server call for validation. |
M: | For an organization different from X, S,
and 2: Updated Segment (modification only).
For an X or 2organization: Server call for validation and update. |
X: | For an organization different from X, S,
and 2: Updated Segment (creation and modification
only). For an X or 2 organization: Server call for validation and selection |
S: | For an organization different from X, S, and 2 only: Updated Segment (deletion only). |
C: | For an organization different from X, S, and 2 only: Segment (deletion only) |
T: | For an organization different from X, S,
and 2: Updated Segment (creation, modification,
and deletion). In these cases, the existence validations and the
update statements corresponding to the selected options are generated. If the Segment is related to a previous Segment, regardless of the indicated use, only the update commands for modification and creation are generated. For an X or 2 organization: Server call for validation, update, and selection. |
U: | For an X or 2 organization only: User defined logical accesses |
Options | Description |
---|---|
No value or N | For organizations different from X, S,
and 2: No order is generated for this Segment
in the selection processing (default option). For an X or 2 organization: No Server call is generated. |
A: | For organizations different from X or 2:
Used in selection. The access order is generated for the selection
according to the type of logical access processing. If the previous
Segment code is blank and the Segment is used, the key is saved in
the conversation area. For an X or 2 organization: Server call for selection (not compatible with the L value in reception). |
U: | For an X or 2 organization only: Call of a User service |
In this pane, you select a Data Element or you enter the name of a new Data Element (not defined in the repository) that is to be used as the primary access key to the Segment. For a VSAM file (V organization), it must be entered on the Segment 00 line. The Data Element that is specified here is considered as a group Data Element, except for SQL organizations where it is considered as an elementary Data Element.
For a Table (G organization), you select a subsystem by indicating the value NUSSY in this field. The associated key (G-ddss-NUSSY) is generated.
For SQL database Segments, a key element must be entered on each line where the value of the Use in display field is not N.
In generated accesses, the Segments are selected when the keys are equal for an update or a direct read. For a sequential read in the repetitive category, the Segments are selected when their keys are equal or greater.
A Segment cannot contain more than 10 key Data Elements.
For an error message file or a Table, if the error message Segment is an SQL/DS Segment or if it has a V or W organization, the Data Element key must be ERKEY.
The logical access is generated automatically, according to the use of the Segment.
User-defined Segment access (organization different from S)
Segment accesses not described (organization different from S)
Options | Description |
---|---|
No control break. | No control break for organizations different
from X. Indicates that a Data Element, which belongs to a key in the repetitive category of a Screen, must remain constant during display. |
C: display break | Display break. Indicates that a Data Element, which belongs to a key in the repetitive category of a Screen, must remain constant during display. |
E: display break (SQL) | For an SQL organization: Display control break. It causes the generation of an equal condition in the WHERE clause of the SQL DECLARE CURSOR statement (and not >= which is generated otherwise). The use of CURSOR is optimized in the repetitive category. |