Rational Developer for System z, Version 7.6

CS line - Segment call

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...).

Id

Category
This field displays the category in which the Segment is used. The category, and therefore the corresponding Segments are processed in the following order:
  • A category:

    Segment belonging to the screen-top.

  • R: repetitive category:

    Segment belonging to the repetitive section.

  • Z: Bottom category:

    Segment belonging to the screen-bottom.

If you move a Segment from a category to another, the value in this field is modified accordingly.
Segment code
This field contains the Segment code used by the generated program associated to the Screen. The Segment code used can be identical to the one present in the Database.
Line number
This is a pure numeric field. Only one 00 line number per Segment is permitted (default). The values from 01 to 99 are required for any other references to this Segment.

Logical characteristics

Generation limitation
In the dropdown 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.

  • User defined Segment:

    Logical accesses to be written in Structured Code.

  • No description of Segment:

    Segment accesses not described.

Control break
This is the control break indicator for display option. Select an option in the dropdown list:
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:
  • The value in the field of the group key Data Element identified with this 'C' is different from the previous value in this field.
  • The value of a superior key Data Element does not match its previous value.
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.
Sub-schema
This field is used with the Pactables function, to indicate which sub-schema is to be described. You must select in the dropdown list between the All data elements choice and a description from 0 to 9 (0 corresponds to sub-schema 10). A subschema is a group of Data Elements present in the Segment composition.
Generate level
The Dialog function automatically generates in the Program associated with the Screen:
  • Values entered between 06 to 98: a sub-function of the F20 function per Data Element called in the Segment to control,
  • a sub-function of the F25, F35 and F60 functions per each accessed Segment.
The hierarchical level of these sub-functions is set to 10 by default. It can be modified for a Data Element or a Segment.

Access key filling

Previous Segment code
In each processing category, several Segments can be accessed. You may thus have to specify the hierarchy of accesses to the Segments within a category. In this field, you specify the code of the preceding Segment in the hierarchy of accesses. This Segment must belong to the same category. It is not recommended to link Server calls and calls of Segments that correspond to Databases or files.
Display
Select one of the choice in the dropdown list.
  • If you select A: Used in display, the Segment is used in display. The access statement will be generated for the display 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.
  • If you select N: not used, no access order is generated for this Segment in the display processing. Otherwise, access orders are generated according to the generation limitation.
Reception
Here you specify the way the Segment is used in validation and update processing. Select an option in the dropdown list:
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.
Access key source
This field (14 characters long) indicates the source to be used to fill in the key fields of the Segment.

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

Note: If the Segment is used in display in the repetitive category, the K-....-......(2) key is not filled in since the Segment's access key is not defined.

This specification is not available with the HLPI option (the key is directly coded in the 'WHERE' parameter).

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 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.

Data element
This field contains the code of the Data Element used as an access key to the Segment and you can select another one via the Change button.
Undefined Data element
If the primary access key is a group Data Element, you enter in the Undefined Data element field the code of the elementary Data Elements composing the group.

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.

Segment

Segment
Field to be entered when the Segment name in the Screen is different from the Segment code stated at the Specifications Dictionary level. You can change for another Segment name via the Change button. If you click the Segment link, you switches to the Segment editor's overview tab.

Database

Database block
Here you can select a database block name via the Change button.

Physical characteristics

Organization
It corresponds to the organization of the Segment. The values entered at this level are the physical characteristics of the Segment. Th etype of organization is required for the ’00’ line number of the Segment. Select a type of organization in the dropdown list. Required in a creation context.
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.
Description type
This field defines the type of Segment being used. Select one of the following option in the dropdown list:
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.

External name
The default value corresponds to the first two characters of the Segment code in the program.
For a DL/1 Segment, it corresponds to the PCB name.
For SQL: Code of the SQL View is called.
For other variants, the external name of the file which corresponds to the SELECT clause in the generated program.

Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)