Filler definition

Fillers are not defined in the repository. They can be called from Segments, but not from Tables. They are used as alignment fields, and do not contain any information. Therefore, they are characterized only by their lengths. Their length is represented by the values that are entered in the Format and Usage fields in the Filler definition section. To display the content of the Filler definition section, you must select a filler call line in the list of the called elements. In this section, you define the length of the filler for the current Segment in the Format and Usage fields. Redefines are possible for fillers.

Note: If you use the Segment in a Database Block, fillers are ignored at generation time.

To display the Filler definition section, select the filler call line in the -CE lines of the Segment.

Label: The label is optional for a filler.

Occurs: This field represents the OCCURS clause of an elementary Data Element, a group, or a filler. The restrictions of the COBOL OCCURS clause apply.

Sort key

This field identifies all the Data Elements that can be used as control break sort keys, or as access keys to a file, a database or a Pactables Table.

Note: It is advised to dedicate a Segment to only one type of use. Each Data Element that can belong to a sort key must be referenced by a unique alphabetic or numeric character. It is advised to reference the indicators by a series (1, 2, 3 for example). The actual sort sequence is selected at the Program level (on the -CD Lines tab).

You must not forget that the format of key group Data Elements must have been entered in the repository or at the Segment level.

Table 1. Possible values of the sort key for Pactables
Value	Comments
`U`	References the access key for a Table. This value must be indicated on the group Data Element if it is a group key.
`S`	Indicates that the Data Element belongs to at least one subsystem.

Table 2. Possible values of the sort key for DL/1 databases
Values	Comments
`U`	References a unique key for a DL/1 database.
`M`	References a multiple key for a DL/1 database.
`1 - 9`	Secondary index All other values designate a search field.

Table 3. Possible values of the sort key for AS400 and relational databases
Values	Comments
`0 - 9`	AS400 physical file key. relational databases
`V`	Variable length column
`Blank`	Fixed-length column
`W`	For DB2 SQL, SQL/DS and ORACLE, generation of a variable length column (`VARCHAR`).
`L`	For DB2 SQL, SQL/DS and ORACLE, generation of a `LONG VARCHAR`.

Note: Sort keys are not authorized on Data Elements redefining other Data Elements.

Format

The format is required for a filler. It is the internal format, defined in the same way as in the definition of a Data Element. The input and output formats are identical, but with a DISPLAY usage. The format and usage represent the length of the filler. There are three categories of fillers:

Fillers that contain alphanumeric characters. This category is also used for dates with a nonstandard format,
Fillers that contain numeric characters only,
Fillers for date with a standard format.

If the format of a numeric Data Element is more than 10 characters long, you must omit the 9 that would normally be entered after the V. For example, S9(10)V9(3) must be entered as S9(10)V(3). This way of coding must not be used when the format is shorter than 10 characters.

You must enter the internal format like a COBOL picture, without print characters.

The INTERNAL USAGE clause is associated with this format.

Data Elements that represent a date can be assigned a symbolic format:

Table 4. Format of a filler
Symbolic value	Meaning
D	Without century (DDMMYY or MMDDYY)
C	With century (DDMMCCYY or MMDDCCYY)
I	Without century (YYMMDD)
S	With century (CCYYMMDD)
E	Without century (DD/MM/YY or MM/DD/YY)
M	With century (DD/MM/CCYY or MM/DD/CCYY)
G	Gregorian format (CCYY-MM-DD)
T	Timestamp format

Note: For the formats that include a separator (E, G, M, and T), you can specify a separator after the character that represents the format, if you do not want to use the separator included by default in the format. For example, a G/ format generates CCYY/MM/DD instead of CCYY-MM-DD, which is the default Gregorian format.

Usage

It corresponds to the COBOL USAGE clause.

With the USAGE clause of a COBOL numeric variable, you indicate the internal representation of its value. Different usages are available depending on the COBOL variants adapted to the material in use.

You select a Data Element usage according to the following elements:

The type of COBOL to generate associated with the Library where you define the Data Element.
The internal representation that you want.
Example: If you generate for IBM, a C usage generates USAGE BINARY and F generates USAGE COMP-1. For UNISYS 1100, an H usage generates USAGE COMP.

You can use this Data Element in a lower-level Library whose type of COBOL to generate is different from the type of the higher Library.

Example: The DELCO Data Element is defined in the HIG Library with a C usage. You use it in a LOW Library with a type of COBOL to generate for UNISYS 1100.

The Data Element usage is automatically replaced with an equivalent that is compatible with the type of COBOL to generate. So when you view DELCO in LOW, the usage that is automatically displayed is H.

Table 5. Possible values for the usage
Value	Meaning
B	`COMPUTATIONAL-1 ICL 1900 BINARY-1 UNISYS 1100`
C	`COMPUTATIONAL` (binary) IBM or equivalent. `BINARY` IBM and COBOL II variant.
D	`DISPLAY` (default option except for Unicode-type Data Elements). Required for date Data Elements.
F	`COMPUTATIONAL-1` IBM or equivalent. `COMPUTATIONAL-9` BULL GCOS7. COMPUTATIONAL-11 GCOS8. Relational DBD: floating point, simple precision.
G	`COMPUTATIONAL SYNCHRONIZED RIGHT` ICL 2900 `COMPUTATIONAL-5` MICRO FOCUS.
H	`COMPUTATIONAL` UNISYS 2200. `BINARY` UNISYS 2200 (COBOL 85).
I	`DISPLAY-1` UNISYS 2200.
J	`COMPUTATIONAL-6` GCOS8. `REAL` UNISYS-A.
N	`COMPUTATIONAL-4` aligned on a half-byte. You must add the complement if the length is uneven. `NATIONAL` (default usage) for Unicode-type Data Elements (U type).
O	`COMPUTATIONAL-4` UNISYS 2200
P	`COMPUTATIONAL-1` GCOS8.
Q	`COMPUTATIONAL` GCOS8.
R	`COMPUTATIONAL SYNCHRONIZED RIGHT`, IBM or equivalent. This value is preferable to `C` when binary data is aligned on even addresses, because the corresponding COBOL statements are more efficient.
T	`COMPUTATIONAL-3 PACKED SYNC`. GCOS8.
U	`COMPUTATIONAL-1` UNISYS 2200.
W	`COMPUTATIONAL-2` UNISYS 2200. `COMPUTATIONAL-12` GCOS8. Relational database: floating point, double precision.
X	`DISPLAY SIGN IS TRAILING SEPARATE CHARACTER`. or `NATIONAL SIGN IS TRAILING SEPARATE CHARACTER` for Unicode-type Data Elements (U type).
Y	`DB-KEY` GCOS8. `POINTER` IBM and MICRO FOCUS
Z	In batch mode only: this option, which is only used with an output format, generates a `BLANK WHEN ZERO` clause with the Batch Applications function.
0	`COMPUTATIONAL-7` GCOS8
1	`DISPLAY SIGN LEADING SEPARATE` for UNISYS 2200, GCOS8, IBM, TANDEM, GCOS7. `NATIONAL SIGN IS LEADING SEPARATE CHARACTER` for Unicode-type Data Elements (U type). `USAGE SQL TYPE IS BLOB (n/nK/nM/nG)` for Large Object-type Data Elements (L type) that are used as columns in DB2 databases. `SQL-BLOB` for Large Object-type Data Elements (L type) that are used as columns in ORACLE databases.
2	`DISPLAY-2` GCOS8 `= DISPLAY`. Fields are compared in accordance with the commercial collating sequence and not in accordance with the standard BULL sequence. `USAGE SQL TYPE IS CLOB (n/nK/nM/nG)` for Large Object-type Data Elements (L type) that are used as columns in DB2 databases. `SQL-CLOB` for Large Object-type Data Elements (L type) that are used as columns in ORACLE databases.
3	`COMPUTATIONAL-3` IBM or equivalent. `COMPUTATIONAL` GCOS7 `PACKED-DECIMAL` UNISYS 2200 (COBOL 85) `USAGE SQL TYPE IS DBCLOB (n/nK/nM/nG)` for Large Object-type Data Elements (L type) that are used as columns in DB2 databases. `SQL-BFILE` for Large Object-type Data Elements (L type) that are used as columns in ORACLE databases.
4	`USAGE SQL TYPE IS BLOB-LOCATOR` for Large Object-type Data Elements (L type) that are used as columns in DB2 databases.
5	`COMPUTATIONAL-1` GCOS7 GCOS8 `USAGE SQL TYPE IS CLOB-LOCATOR` for Large Object-type Data Elements (L type) that are used as columns in DB2 databases.
6	`COMPUTATIONAL-2` GCOS7 GCOS8 `USAGE SQL TYPE IS DBCLOB-LOCATOR` for Large Object-type Data Elements (L type) that are used as columns in DB2 databases.
7	`COMPUTATIONAL-5` ICL 2900. `USAGE SQL TYPE IS BLOB-FILE` for Large Object-type Data Elements (L type) that are used as columns in DB2 databases.
8	`COMPUTATIONAL` BULL 66 GCOS8 `USAGE SQL TYPE IS CLOB-FILE` for Large Object-type Data Elements (L type) that are used as columns in DB2 databases.
9	`COMPUTATIONAL-3` GCOS7 and GCOS8. `USAGE SQL TYPE IS DBCLOB-FILE` for Large Object-type Data Elements (L type) that are used as columns in DB2 databases.

Redefines: The Data Element that contains this option redefines the Data Element of the same COBOL level that precedes it in the Segment description. If a Data Element that redefines another Data Element is contained in a group, it is considered to be an elementary Data Element. It must be taken into account in the calculation of the number of Data Elements that are contained in a group (except for DL/1 database Segments).

Click More to open a wizard where you indicate controls on the filler call or specify the subschema that the filler belongs to.

Note: To open this wizard, you can also click the button that appears when you click the columns CMS456, Values/Subfunction, and Update target in the table of the tab.

-G Lines

Click -G Lines to define -GC lines, -GE lines, and -GG lines for the filler.

Feedback