Rational Developer for System z, Version 7.6

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 called Elements. In this section, you define the length of the filler for the current Segment via the Format and Usage input fields. Redefines are possible for fillers.

Note: If you use the Segment in a Database block, the Fillers will be ignored at generation time.

To display the Filler definition section, select the Filler's call line among in the -CE lines of the Segment. The Filler definition section shows up in the right part of the -CE Lines tab.

Occurs
Enter an occurs number in this field to generate an OCCURS COBOL clause. The COBOL restrictions on the OCCURS clause also apply here. You can indicate an occurs number on an elementary or a group Data Element or a Filler. The occurs 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 ('U' type), 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:
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 which include a separator (E, G, M and T), you can specify, after the character which represents the format, a separator if you do not want to use the separator included by default in the format (For example, A 'G/' format will generate CCYY/MM/DD instead of CCYY-MM-DD, which is the default Gregorian format).
Usage
This 'Usage' corresponds to the COBOL USAGE clause.

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

You should choose 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 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 to the one of the higher library.
Example: You have defined the DELCO Data Element in the HIG library with C usage and you use it in a LOW library with a type of COBOL to generate for UNISYS 1100.
When this happens, the System automatically replaces the Data Element usage with an equivalent which is compatible with the type of COBOL to generate. So, when you visualize DELCO in LOW, the usage automatically displayed is H. This value will be used to generate. If there is no equivalent, or if the provided one does not suit you, you can modify the usage of the Data Element in the lower library to obtain the result you want.
Value Meaning
D DISPLAY (default option).

Required for date Data Elements.

C COMPUTATIONAL (binary), IBM or equivalent;

BINARY, IBM and COBOL II variant.

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

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, since 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 DBD : 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 MICROFOCUS
Z In batch mode only: this option, which is only used with an output format, allows for the generation of a BLANK WHEN ZERO clause with the Batch D.S. 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-3IBM 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 containing this option redefines the Data Element of the same COBOL level which precedes it in the Segment description. If a Data Element which 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 contained in a group (except for DL1 database Segments).

More

Click the More... button to open a dialog box in which you indicate the presence check values for the Filler called in the Segment.

-G Lines

Click the -G Lines... button to define -GC lines, -GE lines, and -GG lines for the Filler called in the Segment.


Terms of use | Feedback

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