You can call a Server from a TUI client Screen for a validation and selection service. The characteristics of the Server call are to be indicated in the Server call section of the -CS Lines tab.
You must use a Segment or a Logical View to call a Server.
For the Logical View code used for the call of a Business Component (X-type organization), the code must be identical to the code used in the associated Business Component.
If you click the Segment link, you switch to the Segment editor Overview tab.Here you can select or change a Server name by clicking Change , or remove a Server name from the Server call section by clicking Remove.
Segment belonging to the Screen top.
Segment belonging to the repetitive category (as many times as there are repetitions indicated),
Segment belonging to the Screen bottom.
Options | Description |
---|---|
N or Blank: | 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 |
---|---|
N or Blank: | For organizations different from X:
No order is generated for this Segment in the selection processing
(default option). No Server call is generated. |
A: | For organizations different from X:
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. X organization: Server call for selection (not compatible with the L value in reception). |
U: | X 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 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 in structure code. (organization different from X)
No description of Segment. (organization different from X)
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 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. |
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. |
Options | Comments |
---|---|
None | No comment |
V: Indexed | Segment organization: Indexed |
G: Table-type | Table-type Segment. The generated access corresponds to the call of the Pactables standard access module. |
H: Relational database accessed with SQL | Relational SQL database Segments accessed by
SQL: The Segment description and the physical accesses are generated; the cursor declaration is generated for the Segments of the repetitive category. The type of relational Database Block is required in the definition of the Block whose code must be entered in the External Name field. Note: Relational organization must be grouped
in the -CS Line of the Screen.
|
W: Managed by procedures, fill display keys | Segment access is managed by procedural code. Only one description in the WORKING-STORAGE SECTION is generated. |
X: Server call for validation and selection. | Server call for validation and selection. |
Option | Comments |
---|---|
Conventional (fixed) | Complete Segment (common and specific parts). |
1: Database Segments | Specific part only. (Default value for a table, organization 'G'.) |
E: Table-type | Table-type Segments: The input format of the Segment Data Elements is taken into account. |
2: conventional (variables) | Complete Segment with variable length for indexed
organization ('V'). The generated description might vary according to the generation variant. |
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.
The external name to enter is the code of the Database Block that contains the relational table indicated in the Database Block code.
The description and accesses are generated with the relational table code entered in this field.
In CICS: four characters for the DDNAMEs of the files managed by Pactables. These characters are the transaction code used to access Pactables files.