The physical information that is required to generate a
Database Block must be entered on the -GG Lines of
the -G Lines tab of the Block. You can also
add generation elements that are associated with a Block description
line from the -Dx Lines tab (-DR, -DH, -DC
lines). It complements the logical information that is entered on
the Database Block Definition.
In the -GG Lines tab,
you can modify the information that is indicated in the Block description
lines before the generation. Lines are automatically displayed to
guide you when you enter the physical information of the Block. These
lines are identified by VIRT or GUID in
the Source column. These lines are called virtual
lines. Only the lines that are identified by VIRT are
generated.
To modify these lines,
you must override them (Override button) and
create lines between the beginning and end insertion lines. When you
override these lines, the VIRT and GUID identifiers
are changed into FROMVIRT and FromGUID.
The lines can then be entered.
You can create
lines anywhere in the table. To edit a line, select it and press the
F2 key.
- Error
- This column displays a dot on all the existing description lines
that are not empty.
Moreover, if this line is not correct, this
column also displays an error or warning symbol, depending on the
severity of the error. A hover help indicates the source of the error.
- Type
- You can select one of the following values:
- G: Line to add the following elements:
- The physical characteristics of a Block on the Block Definition,
- Generation elements on the Block Description.
The line is generated instead of the automatically generated
elements.
- *: Line that is not generated. It is used
to insert a comment or an override.
- P: Line that is generated between the automatically
generated elements and their descriptions.
- Z: Line that is generated after the automatically
generated elements.
- V: Line that is generated before the automatically
generated elements.
The P, Z, and V types
are associated with the SOCRATE databases. P and Z types
are also available for -GG lines that are associated with CODASYL
Block Definition and -DC Lines.
- Description
- This column must contain the following information:
- If you inserted a line other that an Input Aid call, the column
content depends on the line type and the Block type. The first part
of the description can contain 60 characters, the second part 40.
- If you inserted an Input Aid call line, the variable
labels and the symbolic values that are indicated in the selected
Input Aid -D Lines tab are displayed.
- From
- This column identifies the virtual lines that are automatically
generated to help you modify the generated lines according to the
required format. These lines are identified by VIRT or GUID If
these lines are overridden, the VIRT and GUID identifiers
are changed into FROMVIRT and FromGUID.
- Input Aid
- This column contains the name of a called Input Aid. If you click
the button that is displayed when you click in this column, you can
see the Input Aid description in a detail window. In this window,
you can modify the variable labels and symbolic values.
Lines associated with DL/1 Database Blocks
- Lines associated with a Physical DBD:
Several virtual documentation
lines are associated with an IP- or IS type
Database Block. You must complete the generated virtual lines to provide
the information that is required to determine the characteristics
of an index (such as ACCESS or PASSWD).
- Lines associated with a Physical DBD (Type of Block
= DR):
The definition of a DR type
Block is identical to that of a DP type Block.
All of the Data Elements that are called into a Segment of a DP type
Database Block are generated as FIELD statements.
You can reduce the DBD description to the Data Elements that are used
as access keys. With the DR type Database Block,
you can generate as FIELD statements the Data
Elements that are identified by an alphanumeric character in the Access
Key field and labeled K on the
Segment -CE Lines tab. The virtual lines are
identical to the virtual lines of the DP type
Database Block.
- Lines associated with a Logical DBD (Type of Block
= DL):
The generated lines (Block name and ACCESS=LOGICAL)
are sufficient. Rewriting them is not necessary.
Lines associated with CODASYL databases
- TANDEM:
- Complement to the generated lines:
In the
-GG Lines,
you specify the physical characteristics of the TANDEM database and
its components, and all the information about insertion modes. You
can therefore create lines, modify, or delete lines that have been
automatically generated: you can insert a new line in the adequate
location, or override a line
Example: Overriding
a virtual line:
G RECORD < RECORD NAME >
G RECORD SS00
- Overriding a Data Element:
You must create lines between the
beginning of insertion and end of insertion boundaries. To override
a Data Element, you must specify
<DELCO > on
the first line, and the new description on the following lines. If
you do not want the new Data Element to be displayed, you must not
create any line after this first line. You must enter at least six
characters between the two delimiters.
Example: G RECORD < RECORD NAME > .
G FILE IS < FILE NAME > .
G KEY-SEQUENCED .
G ---> ELEMENT INSERTION BEGINNING <---
G<NUCLIE>
G 10 NUCLIE PICTURE X(8).
G ---> ELEMENT INSERTION END <---
G KEY IS < FIELD NAME > .
The lines to be included in the generation must have a G type.
- DSMII:
You can insert comments, commands, descriptions, labels,
print requests wherever you want to in the generated structure. You
can also erase and replace the description that is automatically generated.
You insert comment lines on
* type lines. These
lines are not taken into account at generation time. Several types
of lines can be inserted. Two types of insertions are possible:
- Within the definition lines of an element,
- Within a particular item of the element.
All the lines that are related to the entity definition must
be at the beginning. All the lines that are related an item must be
consecutive.
- Items:
The Data Element code is indicated between the < and
> symbols on a general documentation line of the affected entity:<datel
>. This notation is taken into account in the Data Element
use definition. In a data set or a "remap" description, the Data
Element marked this way does not interfere in the generation. It must
not have any line type. For access, set and subset, Data Elements
marked this way are taken into account for the generation. They must
have a type.
- Data indication:
Most often, data is described from column
two. If the data description starts in column one, a semicolon line
is inserted before the line generated for this data.