Undefined Data call

You must enter all the required information to define a Data Element call in the Segment directly from the table or from the Undefined Data definition section. You can redefine another Data Element of the same COBOL level with the Redefines check box. You can also define controls or specify subschemas for the Data Element. You can also define -GC, -GE, -GG lines for this Data Element call.

Name
This name references the Data Element independently of any Data Structure, Report, or Screen to which the Data Element might belong. Including a Report, Screen or Segment name in the Data Element name is not necessary because it is automatically performed.

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

Table 1. List of reserved Data Element names
Name Reserved for
FILLER Field alignment
ENPR

GRPR

ERUT

Data Element error check in transaction files

Segment error check in transaction files

User-defined errors in transaction files

Label
Enter the label that identifies the instance. It will constitute a search criterion upon a subsequent search.
Internal format
This format, which is 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 one of the following components:

  • An application file (permanent file, database, temporary file).
  • A Screen as a data-entry field, if no conversational format was 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 that 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 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 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.

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 that are not specified in the repository, you must select a usage after the internal 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 that are 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 3. 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 GCOS7.

COMPUTATIONAL-11 GCOS8.

Floating point, simple precision for relational databases.

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.

Floating point, double precision for relational databases.

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 Reserved to batch applications. It is used only with an output format to generate a BLANK WHEN ZERO clause.
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.

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 4. 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 5. 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 6. 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.
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 that precedes it in the -CE lines of the Segment. 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 in a group (except for DL/1 database Segments).
Note: When Data Elements are redefined, Pacbase does not take their respective lengths into account. It is your responsibility. The redefined Data Element length is used for the calculation of the address length. 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 Data Element of the same level in the call structure. You must then define the Occurs option in the Set of Redefines section.

More

Click More to open a wizard where you indicate controls on the Data Element call or specify the subschema that the Data Element belongs to.
Note: To open this wizard, you can also click the button that appears when you click the columns CMS456, CONT, Values/Subfunction, and Update target in the table of the tab.

-G Lines

Click -G Lines to define -GC lines for the Data Element that is defined in the Segment or Table.


Feedback