Rational Programming Patterns for System z

Definition tab

In the Definition tab, you indicate the formats, type and usage of the Data Element. You can also indicate a parent Data Element, if any, and the Blank when zero option.

Type
Select one of the following types:
  • Data Element: elementary piece of information used in applications.

    DBD function: CODASYL elementary data, relational column.

  • Property: elementary piece of information defined at the conceptual level.
    Note: The format is optional.
  • Alias Data Element.

    This value is automatically set when retrieving existing data.

  • Large Object Data Element.
  • Unicode Data Element.
    Note: The usage must be 'N' (default), 'X' or '1'.
Inheritance
A Data Element is an elementary concept. In your applications, you might want to use several technical variants of this concept. So to guarantee the coherence of your data, you manage these variants by creating parent and child Data Elements.

The characteristics of the parent Data Element (its formats and its usage) are passed on to its child, where they are marked as Inherited. In the child, you can modify the characteristics inherited from its parent. In this case, you see Redefined next to the modified characteristic.

All Data Elements from the same family are logically linked in the database. A child Data Element cannot be a parent as well. The inheritance tree of the current instance displays its parent, if any, and its children, if any.

If a parent Data Element has already been indicated for the Data Element, you see its name here. If you want to specify a parent Data Element, click Change and select a Data Element in the selection wizard. You can remove the parent Data Element by clicking Remove.

If no parent is declared, this field displays No inheritance.
Internal format
This format, displayed in the Overview tab, is required, except if the Data Element is a Property.

The internal format is used when the Data Element is called in:

  • An application file (permanent file, database, temporary file),
  • A Screen as a data-entry field, if no conversational format has been specified (see the type of line field in the -D Lines tab of the Data Element editor).
This format is automatically transferred into the Segments where the Data Element is called. But you eventually select the appropriate format in the -CD Lines tab of the Programs which call these Segments.

You must ensure the compatibility between the input and internal formats.

The internal format must be coded like a COBOL picture (without print characters).
Notes:
  • 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
  • For Unicode-type Data Elements, you must indicate 'N(n)' or a signed or unsigned numeric format.
The INTERNAL USAGE clause is associated with this format.
Note: If a Unicode-type Data Element has a signed numeric internal format, its internal usage must be X or 1.
Data Elements that represent a date can be assigned a symbolic format:
Table 1. Symbolic formats for dates
Symbolic value Meaning
D Without century (DDMMYY or MMDDYY)
I Without century (YYMMDD)
E Without century (DD/MM/YY or MM/DD/YY)
S With century (CCYYMMDD)
C With century (DDMMCCYY or MMDDCCYY)
M With century (DD/MM/CCYY or MM/DD/CCYY)
G Gregorian format (CCYY-MM-DD)
T Time format (HH:MM:SS)
TS Timestamp format
Note: For the formats which include a separator (E, G, M, and T), you can specify a separator after the character which 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.

For details on the use of the formats with the various types of Database Blocks, see the summary tables in chapter Columns: Data Elements of the 'Relational SQL Database Description' manual at this URL:

http://www-01.ibm.com/support/docview.wss?rs=37&uid=swg27005477

Input format
This format is specific to the Batch Applications function. It is required when the Data Element is called in a transaction file, used as input in a batch flow.

This format is converted into the internal format when permanent files are transferred.

If you do not specify an input format, the internal format is automatically taken into account.

The input format is automatically transferred into the Segments where the Data Element is called. But you eventually select the appropriate format in the -CD Lines tab of the Programs which call these Segments.

You must ensure the compatibility between the input and internal formats.

The input format must be coded like a COBOL picture (without print 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.

Data Elements that represent a date can be assigned a symbolic format:
Table 2. Symbolic formats for dates
Symbolic value Meaning
D Without century (DDMMYY or MMDDYY)
I Without century (YYMMDD)
E Without century (DD/MM/YY or MM/DD/YY)
S With century (CCYYMMDD)
C With century (DDMMCCYY or MMDDCCYY)
M With century (DD/MM/CCYY or MM/DD/CCYY)
G Gregorian format (CCYY-MM-DD)
T Time format (HH:MM:SS)
TS Timestamp format
Note: For the formats which include a separator (E, G, M, and T), you can specify a separator after the character which 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.

For details on the use of the formats with the various types of Database Blocks, see the summary tables in chapter Columns: Data Elements of the 'Relational SQL Database Description' manual at this URL:

http://www-01.ibm.com/support/docview.wss?rs=37&uid=swg27005477

Output format
The output format is used when the Data Element describes:
  • A field in a Report
  • A protected field in a Screen, if no conversational format has been specified (see the type of line' field in the -D Lines tab of the Data Element editor).

The output format is automatically transferred into the Segments where the Data Element is called.

It must be coded like a COBOL picture.
Note: 'Unicode'-type Data Elements (U type) must have an N(n) output format (with the possibility to insert characters such as B, O, /...) or a numeric edited format.

The usage is always Display, except for 'Unicode'-type Data Elements whose usage is National (default), National sign is trailing separate char or National sign is leading separate char.

Data Elements that represent a date can be assigned a symbolic format:
Table 3. Symbolic formats for dates
Symbolic value Meaning
D Without century (DDMMYY or MMDDYY)
I Without century (YYMMDD)
E Without century (DD/MM/YY or MM/DD/YY)
S With century (CCYYMMDD)
C With century (DDMMCCYY or MMDDCCYY)
M With century (DD/MM/CCYY or MM/DD/CCYY)
G Gregorian format (CCYY-MM-DD)
T Time format (HH:MM:SS)
TS Timestamp format
Note: For the formats which include a separator (E, G, M, and T), you can specify a separator after the character which 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.

For details on the use of the formats with the various types of Database Blocks, see the summary tables in chapter Columns: Data Elements of the ″Relational SQL Database Description' manual at this URL:

http://www-01.ibm.com/support/docview.wss?rs=37&uid=swg27005477

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 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 type of the higher Library.
Example: You have defined the DELCO Data Element 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 which is compatible with the type of COBOL to generate. So when you visualize DELCO in LOW, the usage automatically displayed is H.
Table 4. 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, 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 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.
Blank when zero
This box is associated with the formats.

If you check this box, the Blank when zero COBOL clause is generated. Blanks replace the zero values that are normally printed or displayed.

It only applies to numeric Data Elements, for the retrieval of old versions.


Terms of use | Feedback

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