Rational Developer for System z, Version 7.6

Undefined Data call

To display the content of the Undefined Data Definition section, click on the undefined Data Element line call. You must enter all information required to define a Data Element at the Segment level: its name, label, internal format, usage, occurs, sort key. You can also redefine another Data Element of the same COBOL level via the Redefinescheckbox. Other characteristics associated with the Data element defined in the Segment can be completed via the More... button. Clicking the -G Lines... button allows you to define -GC, -GE, -GG lines for this Data element.

Name
This name references the Data Element independently of any Data Structure, Report or Screen to which the Data Element might belong (there is no need to include a Report, Screen or Segment name in the Data Element name since this is automatically performed).

This name consists of alphabetic or numeric characters only. The following table lists the Data Element names that cannot be created:

Name Reserved for
FILLER Field alignment

ENPR

GRPR

ERUT

Error check fields on transaction files (options of the Batch Function)

Data Element error check

Segment error check

User-defined errors

Label
Enter the label, which identifies the new instance. It will then constitute a search criterion for a subsequent search.
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 an input 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 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)
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, 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).

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

For Data elements not specified in the Dictionary, once the internal format entered, you need to select a usage.

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.
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.
Sort key
This field identifies all data elements that might be used as control break sort keys, or as access keys to a file, a database or a Pactables table.

Note: It is highly recommended to dedicate a Segment to only one type of use. Each data element that may belong to a sort key must be referenced by a unique alphabetic or numeric character. It is recommended to reference the indicators by a series (1, 2, 3 ...). The actual sort sequence will be chosen at the program level (on the Call of Data Structures (-CD) screen) by sequencing the characters in the appropriate order.
Don't forget that the format of key group data elements must have been entered in the Dictionary or at the segment level.
Value Comments
U References the access key for a VisualAge Pacbase 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 sub-system.
Values Comments
U References a unique key for an DL/1 database.
M References a multiple key for an DL/1 database.
1 to 9 Secondary index All other values designate a search field.
Values Comments
0 to 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 allowed on data elements redefining other data elements.
Redefine
Redefinition is possible within a Segment. It generates the COBOL REDEFINES clause. The Data Element containing this option redefines the Data Element of the same COBOL level which precedes it in the -CE lines of the Segment. 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).
Note: When Data Elements are redefined, VA Pac does not take their respective lengths into account. This is your responsibility. In the calculation of address length, the redefined Data Element length is used for the address calculation. Redefined Data Elements are ignored when generating for the Database Description function. If the 'Redefines' box is checked, no initial value can be entered.
To redefine a Data Element, check the Redefines option. A Set of Redefines line is created in the list, it contains the redefined Data Element and the preceding one of the same level in the call structure. You must then define the Occurs option in the Set of Redefines section.

More...

Click the More button to display more information such as the check types on each Data Element called in the Segment: presence check and class control.

-G Lines

Click the -G Lines... button to define -GC lines, -GE lines, and -GG lines for the Data Element defined in the Segment.


Terms of use | Feedback

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