To display the contents of this section, you must select a Data element call line from the persistency objects tree in the -CS tab in the Screen editor. In this section, you must give the characteristics of the Data element call.
Segment belonging to the screen-top.
Segment belonging to the repetitive section.
Segment belonging to the screen-bottom.
the logical access is generated automatically, according to the use of the Segment.
Logical accesses to be written in Structured Code.
Segment accesses not described.
Header | Header |
---|---|
Blank: no control break. | |
C: display break | This provides an indication of the logical end-of-file
for control break processing in the repetitive section . Control
break processing will take place under either of these conditions:
|
E: display break (SQL) | Display control break, causes the generation of an equal condition in the 'WHERE' clause of the SQL 'DECLARE CURSOR' statement (and not >=, which is generated otherwise). Allows optimization of the use of 'CURSORs' in the repetitive category. |
Options | Description |
---|---|
N | Not used. No access statement will be generated for this Segment in the validation and update processing. |
L | Read. A simple read command is generated for the Segment. |
E | Existence validation to execute. A read command with the setting of an error code is generated (if it is not found). |
M | Updated Segment (modification only). |
X | Updated Segment (creation and modification only). |
T | Updated Segment (creation, modification and deletion). In the last three cases, the existence validations and the update statements corresponding to the chosen 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 Segments accesses conditioned by a previous Segment access, update commands for deletions will not be generated. |
U | User-defined logical accesses. |
Entered on the '00' line, the '*SSA' value inhibits the generation of the qualified SSA corresponding to the Segment in the PCB. The Access key source field must be entered with the code of the Data Element used as the display key. The K-.... field is generated with the access key indicated in the Primary access key field (Data element). The key will be filled in automatically in functions F25, F40, and F60.
The SSA of the processed Segment is filled in from the '-CS' lines whose key code has not been found in the hierarchical path
This specification is not available with the HLPI option (the key is directly coded in the 'WHERE' parameter).
In this pane, you select a Data element or you enter the name of a new Data Element (not defined in the Dictionary) that will be used as the primary access key to the Segment. It is used to generate the 'RECORD KEY' clause. The Data Element specified here is considered as a Group Data Element except for SQL organizations where it is considered as an Elementary Data Element.
If a group Data Element is used, and different values are given to the individual members of that group, the codes of those elementary Data Elements are named here. Key Data Elements are not updated in a 'SQL UPDATE' order.
For a Table ('G' organization), selection of a sub-system is executed by indicating the value 'NUSSY' in this field. The system generates the associated key (G-ddss-NUSSY).
In DL/1, the Data Element can belong to all SSA's that permit access to the Segment in the PCB indicated in the external name (code of the PCB).
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 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 can not contain more than 10 key Data Elements.
Key Data Elements are not updated in a 'SQL UPDATE' order.