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.
Note: To implement a service call, you must declare the Logical
View 2 which conveys data between the two Business Components. You
must also call a second-level Business Component and specify the type
of service to be run on Logical View 2.
Server
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.
Id
- Category
- This field indicates the Screen category in which the Segment
is processed. The category, and therefore the corresponding Segments
are processed in the following order:
- Blank: Top category:
Segment belonging to the Screen top.
- R: repetitive category:
Segment belonging to the repetitive
category (as many times as there are repetitions indicated),
- Z: Bottom category:
Segment belonging to the Screen bottom.
- Segment code
- This field must be entered when the Segment code in the Screen
is different from the Segment code stored in the repository.
- Line number
- Only one 00 line number (default) is authorized
in a Segment. This zero line is required to enter the physical characteristics
of the Segment (external name, organization), the name of the Segment
access key and the name of the Segment in the database Library. It
is a pure numeric field. The values from 01 to 99 are
required for any other references to this Segment.
Access key filling
- Previous Segment code
- Enter the code of the Segment which is to be accessed before the
Segment code in the program (see the Segment code field
in the Id panel). Several Segments can be accessed
in each category. Therefore, a hierarchy can be indicated concerning
the access to the Segments of a category. This field contains the
previous Segment code in the access hierarchy. This Segment must belong
to the same category. If several Segments have the same previous Segment,
they are processed alphabetically.
Note: It is not advised to link
Server calls and calls of Segments which correspond to databases or
files.
- Each Segment must be linked directly or indirectly to the Logical
View on which it depends. It must include the code of a previous Segment
or of its Logical View (S organization).
Exception: The error message Segment must not include the previous
Segment. A Logical View cannot have a previous Segment.
- Reception
- In this field, you indicate the type of service to be run for
an 'X' or '2' organization. The options are presented
in the tableTable 1.
Table 1. Possible
values in the reception fieldOptions |
Description |
N or Blank: 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. |
- Display
- For the 'X' or '2' organization, select one
of the following options:Table 2.
Table 2. Values for displayOptions |
Description |
Blank 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 |
- Access key source
- This field can be used as a working area or a literal.
Example: - 02 for a literal,
- ww10-delco for a working area.
Note: The key loading for the lists must always be performed
from the 1- area in the Servers if the key is in
the repetitive category of the Logical View.
Primary access key
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.
- Data Element
- This field contains the code of the Data Element used as an access
key to the Segment. You can select another code by clicking Change or
remove a Data Element code from this field by clicking Remove.
- Undefined Data Element
- If the primary access key is a group Data Element, and if different
values are given to the individual members of that group, enter the
code of the elementary Data Elements of the group in the Undefined
Data Element field.
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.
Logical characteristics
- Generation limitation
- In the list, select the generation limitation of the logical accesses
to Segments:
- Automatic:
The logical access is generated automatically, according
to the use of the Segment.
- U: User-defined Segment:
User-defined Segment access (organization
different from S).
- P: No description of Segment:
Segment accesses not described
(organization different from S).
- Control break
- Select the control break indicator in the list:
Table 3. Possible values for the control breakOptions |
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. |
- Control break
- Select the control break indicator:
Table 4. Possible
values for the control breakOptions |
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. |
- Subschema
- This field is used with the Pactables function,
to indicate which subschema is to be described. You must select either
the All Data Elements choice or a description
from 0 to 9 (0 corresponds to subschema 10). A subschema is a group
of Data Elements present in the Segment composition.
- For a 'G' - Type (Table) or 'H' - type (relational
database accessed through SQL) organizations:
For Tables defined
in
Pactables, it specifies the number of the Table
sub description (or subschema) to which the input/output area description
corresponds. If the called Segment corresponds to a view and no subschema
has been specified, the value is specified on the Block
-DR
Lines tab. The possible values are:
- All the Data Elements of the Segment.
- From 0: Sub description 0 to 9: Sub description
9 (or subschema) number (1 - 10, where value 0 corresponds
to subschema 10).
- For a V - type (indexed) organizations, it is the secondary access
keys to indexed files:
- Generate level
- Not used for a Business Component.
Physical characteristics
- Organization
- X: Global call of the Business Component: 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.
- Instance by instance Business Component call: The second-level
Business Component is called for each instance. Business Components
are then called as additional servers with respect to the first-level
Business Component. As a result, a service can call Business Components
and data access Segments.
Note: With this type of call, a TUI application
can work in Folder mode: The TUI client makes a service call to an
aggregated Logical View containing a number of Logical Views. The
service is run by a first-level Business Component whose role is to
call – for each instance of the aggregated Logical View – the different
Business Components associated with the other Logical Views.
- Description type
- The description type is automatically set to 1.
- External name
- Enter the code of the Business Component.