Filler definition

Fillers are not defined in the repository. They are used as alignment fields, and do not contain any information. Consequently, they are characterized only by their lengths. Their length is represented by the values to be 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 data-entry 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.

Occurs
Enter a number of occurrences in this field to generate an OCCURS COBOL clause. The COBOL restrictions on the OCCURS clause also apply here. You can indicate a number of occurrences on an elementary or a group Data Element or a filler. The number is limited to 99; it is pure numeric field.
Format
The format is required for a filler. The format and usage represent the length of the filler.

The internal format must be coded like a COBOL picture (without print characters).

Note: For Unicode-type Data Elements (U type), you must indicate N(n) or a signed or unsigned numeric 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.

Note: For Unicode-type Data Elements, you must indicate N(n) or a signed or unsigned numeric format. The usage is always Display, except for Unicode-type Data Elements, whose usage is N (default), X, or 1.
The INTERNAL USAGE clause is associated with this format.
Note: If Unicode-type Data Elements have a signed numeric internal format, their internal usage must be X or 1.
Data Elements that represent a date can be assigned a symbolic format:
Table 1. 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 2. 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).

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 - UNISYS 2200, GCOS8, IBM, TANDEM, GCOS7.

or NATIONAL SIGN IS LEADING SEPARATE CHARACTER for Unicode-type Data Elements (U type).

2 DISPLAY-2 GCOS8 = DISPLAY. Fields are compared in accordance with the commercial collating sequence and not in accordance with the standard BULL sequence.
3 COMPUTATIONAL-3 IBM or equivalent.

COMPUTATIONAL GCOS7

PACKED-DECIMAL UNISYS 2200 (COBOL 85)

5 COMPUTATIONAL-1 GCOS7 GCOS8
6 COMPUTATIONAL-2 GCOS7 GCOS8
7 COMPUTATIONAL-5 ICL 2900.
8 COMPUTATIONAL BULL 66 GCOS8.
9 COMPUTATIONAL-3 GCOS7 and GCOS8.
Redefines
The Data Element that containis 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).

More

Click More to open a dialog box in which you indicate the presence check values for the filler that is called in the Segment.

-G Lines

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


Feedback