In the -CS Lines tab of the Server and Server Dialog editors, you must specify, for each Business Component, the Logical View you are using. For this Logical View, you must indicate the accessed Segments of a file, a table, or an SQL view. In the Segment call section, indicate, for each Segment, the processing category (before repetitive, repetitive, and after repetitive), the type of logical access processing (validation, update and selection) to perform on the Segment and the key filling mode, the use in the generated processing, the access condition, and the physical organization.
The number of Segment description lines called in this tab is limited to 100 per category.
This field contains the code of the Segment called in the Business Component. The selected code can be identical to the code present in the database.
The EM00 value is reserved for the call of the error message file in an error message server (E type).
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, 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 S. It indicates that a Data Element, belonging to a key in the repetitive part, must remain constant during the selection. |
C: display break | Display break for organizations different from S. It indicates that a Data Element, belonging to a key in the repetitive part, must remain constant during the selection. |
E: Selection for control break (SQL) | For an SQL organization: it causes the generation of an equal condition in the WHERE clause of the SQL DECLARE CURSOR statement. |
Options | Description |
---|---|
V | Segment organization: Indexed. |
G | Table-type Segment. In this case, the generated access corresponds to the call of the Pactables general module. |
H | Segment of a relational database accessed with SQL: The Segment description and physical accesses are generated. For Segment access in the repetitive category, the cursor declarative is also generated. The type of the relational Database Block is required on the Database Block definition, in the External name field. |
D | DL/1 Segment |
A | ADABAS Segment |
A | Only one description in the WORKING-STORAGE SECTION is generated. |
W | Segment accesses managed by specific procedures. Only one description in WORKING-STORAGE SECTION is generated. In the -CS Lines of the Server Dialog, call the user buffer Segment. |
S | Call of the Logical View. |
X | Call of a Business Component All the Segments that are called in the repetitive category and in the selection service must be of the same type: Segments with an X organization cannot be combined with Segments with other organizations. |
2 | Call of a Business Component instance by instance |
Options | Description |
---|---|
Conventional (fixed) | Complete Segment (common and specific parts). |
1: Database Segments | Specific part only (forced value for a Logical View, DL/1 Segment, or SQL table). |
E: Table-Type | Table-type Segments: The input format of the Data Elements called in the Segment is taken into account. |
2: Conventional (variables) | Complete Segment with a variable length for
an indexed organization (V). Note: The generated
description might vary according to the generation variant.
|
Code of the SQL Database Block in which the table or view is called. You can select a table or view by specifying a T or V after the code of the selected Block. A space must be left between them.
At generation time, the external name of the table or view is searched for in the Block description. If it is not found, the external name is taken from the Segment Definition
These names cannot exceed six characters.
The PCBs must belong to the PSB of the Screen.
Enter the PCB code.
By default, this field displays the Data Structure code.
Enter the code of the Business Component.