To display the contents of the Segment call section, you must select a Segment line in the -CS list or click the Segment button. In this section, you enter information identifying the Segment, then the logical and physical characteristics of the Segment (external name, organization), and all the other use characteristics (Use, Access Key Source...).
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.
Options | Comments | |
---|---|---|
None | ||
V: Indexed | Segment organization: Indexed The Description of data is generated. The access orders for reception and display procedures are entirely generated according to the logical access procedure and the use. |
|
D: DL/1 | DL/1 segment. The description of data is generated. The Segment access orders for the reception and display processing are entirely generated, according to the type of logical access processing and use. |
|
G: Table-type | Table-type Segment. The generated access corresponds to the call of the general module of the Pactables function. |
|
A: ADABAS-type | 'ADABAS'-type Segment. In this case, the Segment the Description is generated, but no access is executed. Generation of the Control Block and Buffers used in the accesses |
|
T: Total-type | Total-type Segment. The Description of the Segment is generated but no access is executed. |
|
2: DB2 or VAX SQL | DB2 or VAX SQL Segment generation and description.
Only local accesses are not generated. The structure of variable indicators
corresponding to the columns of a DB2 or VAX SQL table is always generated. For all Segments of a Relational Database accessed via SQL: The Segment description and physical accesses are generated. For Segment access in the repetitive category, the cursor declarative is also generated. For this organization, as for all relational database with SQL access in this table, the Description of the Segment and the physical accesses are generated. |
|
C: INTEREL RBBC or RFM | Relational Database with SQL access | |
O: Oracle V5 | Relational Database with SQL access | |
P: Oracle V6 or V7 | Relational Database with SQL access | |
Q: SQL/DS, ALLBASE/SQL, DB2/2, or DB2/6000 | Relational Database with SQL access | |
S: DB2 or VAX SQL | Relational Database with SQL access | |
R: RDMS | Relational Database with SQL access, the Description
of the Segment and the physical accesses are generated. Other related information required: A database block code is required, you must indicate the SQL object type (description type field) and the primary access key. |
|
4: SQL 400 | ||
7: TurboImage | For a TurboImage organization. Other information required: the name of the TurboImage block and primary access key are required. |
|
N: Nonstop SQL | For this relational database, the Description of the Segment and the physical accesses are generated | |
M: DATACOM/DB | Relational database with SQL access | |
I: Informix, Ingres, Sybase, SQL Server | Relational database. For these cases, the Description of the Segment and the physical accesses are generated. | |
U: Managed by procedures | Physical access to the Segment managed by specific procedures. | |
W: Managed by procedures, fill display keys | Segment access is managed by specific procedures and the display keys are automatically filled in(functions F40 and F60). |
|
Y: IBM 38, UNISYS 2200 | Database organization. Value used with IBM SYSTEM 38. UNISYS 2200: SFS indexed organization. |
Option | Comments |
---|---|
Conventional (fixed) | Conventional and multi-record files of fixed length This type of Segment will be appended to the '00' (common key) Segment. |
1: Database Segments | Database Segments Those that do not have their keys isolated in a separate Segment. (Default value for a DL/1 Segment, Organization 'D'' or for a table, ORGANIZATION 'G'.) |
E: TABLE-type | TABLE-type Segments: The input format of the Segment's Data Elements is taken into account. |
2: conventional (variables) | Conventional and multi-record files of variable
length This type Segment will be appended to the '00' (common key) Segment. For Type P organization (ORACLE V6) and Type I organization (SYBASE): automatic generation of CONNECT AT Database, DECLARE Database and access SQL AT Database. Note that the generated description may vary according to the generation variant. |
For Type P organization (ORACLE V6) and Type I organization (SYBASE): automatic generation of CONNECT AT Database, DECLARE Database and access SQL AT Database. Note that the generated description may vary according to the generation variant.