In the -CS Lines tab of a Server or Server Dialog with a Business Component type, you can call another Business Component to run a service. In the Server call section, you must specify the code of the first Logical View which sends the service call to the first-level Business Component. You must also indicate the call to the second-level Logical View (with the appropriate tree structure) by its code in the first level Business Component, and the service call to the second-level Business Component.
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. Click the code to open the Server editor.
Segment belonging to the Screen top.
Segment belonging to the repetitive category (as many times as there are repetitions),
Segment belonging to the Screen bottom.
Options | Description |
---|---|
No value or N: Not used | No Server call is generated. |
L: Read | No Server call is generated. |
E: Existence Validation | Server call for validation. |
M: Update (Modification) | Server call for validation and update. |
T: Update (Creation, Modification, and Deletion) | Server call for validation, update, and selection. |
X: Update (Creation and Modification) | Server call for validation and selection |
U: Call of a User Service | Call of a user service. |
Options | Description |
---|---|
No value or N: Not used | No Server call is generated. |
A: Used in display | Server call for selection (not compatible with the 'L' value in reception). |
U: Call of a user service | 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 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 | 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. |
The first-level Business Component runs service calls and acts like a client. Its function can be considered like a branching point to the second-level Business Components which run the full service requested. The second-level Business Component is called only once for all the instances.