A project represents the physical distribution of your instances in your workspace. There can be various projects for each location (a location is the equivalent of a database).
In the 'Navigator' view of the 'Design' perspective, you will see that the packages represent the branches of your projects. Each package contains its own instances.
So naming a package after a library is be a good idea. To reflect the library hierarchy, you can enter the library names (starting from the highest-level library), and separate each with a period (ex: 'COM.CIF') . This way, the 'Navigator' view will display a first-level branch, COM, with its instances, and a second-level branch, CIF, with its own instances.
You select the library by clicking the Browse... button.
The internal format is used when the Data Element is called:
The internal format must be coded like a COBOL picture (without print characters).
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.
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 |
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-1.ibm.com/support/docview.wss?rs=37&context=SSEP67&uid=swg27005478
All the other sections provide links to the corresponding editor tabs.
If no information is displayed in the section, just click on the arrows located in front of the section name. This gives you access to the More... button. Click on it to access the corresponding tab.
The Documentation section does not directly display the assigned documentation. You must access the Documentation tab to see it.
So the current instance is associated with the generation parameters indicated in the library displayed here. You can click the Change... button to select another library.
Value | Meaning |
---|---|
AA to ZZ and 0A to 0Z | These values cause the lines entered in this tab to
be generated at the beginning of the Working-Storage Section. Relatively
to the Data Structures called in the -W Lines tab, these
lines will be generated as follows:
|
00 to 09, 1A to 19... 9A to 99 | The lines entered in this tab will be generated in the Working-Storage Section, after all the Data Structures whose ' COBOL position' is lower than this prefix |
$n | This represents a parameterized value in a Macro-Structure |
In a Macro-Structure, it can be parameterized by assigning it a $n value
It sets the sequence in which the Data Structure or Report will be processed in the Program/Macro.
When the Data Structure or Report is used only once in a Program, it is recommended to indicate the same code as the one entered as the Data Structure/Report name (chosen upon creation). However if it is called more than once in a Program, you may differentiate these calls. You can parameterize this code in a Macro-Structure with $n.
You should select the format according to the usage of the Data Structure, specified in the 'Usage definition' group of the 'Data Structure Line Definition' section, in the '-CD Lines' tab.
Value | Meaning |
---|---|
Redefined records | No VALUE clause is generated |
1: Records without initial values | Records without initial values or occurs. These records
are presented with the Segment common part followed by the different specific
parts. If the Data Structure description appears in the COBOL File Section, the 'Level' field must be set to 2. With this value, the specific Segments are described without redefines, at the COBOL level 02. Several Segment descriptions are grouped together under the same I/O area. |
2: Records with initial values | Records with the specific initial values indicated in the Segment -CE Lines tab. These values may also default to blank or zero depending on the format. Initial values are also generated for the occursed fields if the 'Generated language' of the Library is set to COBOL II, 85, or 370. |
3: Records with occurs (used with level 2) | Records which incorporate the occurs number indicated
in the 'Table size' field of the Segment Definition tab. No VALUE clause will be generated. If the description of the Data Structure appears in the COBOL File Section, the 'Level' field must set to 2. This type of description cannot be used if the common part Segment of this Data Structure is assigned a value in the 'Table size' field of the Segment Definition tab. (In that case, use the 'W: File description in Working' Organization and the 'T: Table stored in memory' Usage). |
4: Records with occurs (used with level 3) | Records which incorporate the occurs number indicated
in the 'Table size' field of the Segment Definition tab. The associated
'Level' field must be set to 3. A COBOL level 02 is used to access the table made up of occurs of the same record (ddssT). A COBOL level 01 is used to group the whole D.S. together - common or specific parts, whether occurred or not. A group level field that incorporates all instances is generated. This type of description cannot be used if the common part Segment of this Data Structure is assigned a value in the 'Table size' field of the Segment Definition tab. (In that case, use the 'W: File description in Working' Organization and the 'T: Table stored in memory' Usage). |
Value | Meaning |
---|---|
1: COBOL 01 level for DS area and segments | If the Data Structure description appears in the COBOL
File Section, the Segments must be redefined. If a Data Structure has no common part with a non- redefined description, the D.S. Area will only appear when the 'Generated description type' is set to 'Redefined records'. |
2: COBOL 01 level for DS area and segments at 02 level | If the 'Generated description type' is set to 'Redefined records', the D.S. Area and Segments will be described at level 02 (Preferably use a 'L: Working with placement' Organization and define the higher levels through Work Areas). |
3: COBOL level varying with records description type | Level 02 for D.S. Area & level 03 for Segments if
the 'Generated description type' is set to '1: Records without initial values',
'2: Records with initial values' or '3: Records with occurs (used with level
2)'. Level 01 for D.S. Area & level 03 for Segments if the 'Generated description type' is set to '4: Records with occurs (used with level 3)'. Level 03 for both D.S. and Segments if the 'Generated description type' is set to 'Redefined records'. |
4: COBOL 02 level for Data Elements, DS Areas and Segment levels disappear | Reserved for D.S. with an Organization set to 'L: Working
with placement' or 'W: File description in Working'. Level 02 for group Data Elements or elementary Elements that are not part of a group. Elementary Elements that are part of a group appear but the D.S. Area and Segment levels disappear. Level 01 is to be defined in the -W Lines tab. |
5: COBOL 01 level for Data Elements, DS Areas and Segment levels disappear | Reserved for D.S with an Organization set to 'L: Working
with placement' or a Usage set to 'D: Output file'. Level 01 for group Data Elements or elementary Elements that are not part of a group. Elementary elements that are part of a group appear but the D.S. Area and Segment levels disappear. |
You can choose whether the Data Structure must be generated in the Working Storage Section, or as the description of a Pactables Table.
You can also use this field to specify Database descriptions when the Database Description function is not used. These values are taken into account by application Programs.
Value | Comment |
---|---|
S: Sequential | This is the only authorized value for a Report, a Sequential file or a Sort file Data Structure. |
V: VSAM, UFAS | This is one of the two possible values for an Indexed
file Data Structure This value generates the STATUS KEY IS clause and the corresponding field is declared in the 'File Status' field of the Data Structure call Definition section of the '-CD Lines' tab (the part which can be viewed by clicking the More... button). |
I: Indexed | This is the other possible value for an Indexed file
Data Structure. This value corresponds to an indexed sequential organization (ISP for GCOS8 BCD). An ISP file coded 'LE' will be generated in three work areas: LE-FILE, LE-DATA and INVKEY. The VALUE of LE-DATA will be the external file name which must be the file code in the preceding $ DATA line. In the job control lines, the ISP lines give the physical characteristics of the file. |
G: Table description | This value generates the communication area with the Pactables access function. |
L: Working with placement | This is the only possible value for a Linkage Data Structure. File descriptions are generated in the Working Storage Section, but in a location you indicate in the 'COBOL position' field. |
W: File description in Working | This is the only possible value for a Working Storage Data Structure. File descriptions are generated in the Working Storage Section, before the 'WSS-BEGIN' constant. |
Y: Pacbench C/S | Call of the COPY clause which corresponds to the communication area between the client and the server (Pacbench C/S Business Components only). |
X: Comment | Data Structure used as a comment, not used for generation. |
2: DB2 segments or VAX/SQL | Generation-Description of a DB2 or VAX/SQL Segment. Only physical accesses are not generated. The structure of the variable indicators corresponding to the columns of the DB2 or VAX/SQL table is always generated. |
Q: DB2 or ALLBASE/SQL | Reserved for the description of SQL/DS, DB2/2 or DB2/6000 Databases (IBM), or ALLBASE/SQL Databases (HP3000), or DB2/2 or DB2/600 Databases (MICROFOCUS). |
D: DL/1, IDS I and II | Reserved for the description of Segments or records of the IMS (DL/1), IDS I or IDS II databases, in the generation of DBD, SYSGEN, schemas or application programs |
B: IDMS | |
A: ADABAS | |
T: 'TOTAL' files | |
O: ORACLE (< V6) | |
C: INTEREL RDBC or RFM | |
R: RDMS | |
4: DB2/400 | |
M: DATACOM DB | |
N: NONSTOP SQL | |
P: ORACLE V6 and V7 | |
9: INFORMIX, SYBASE, INGRES/SQL, or SQL SERVER | |
2: Data Structure for Socrate/Clio | |
F: Formal for Socrate/Clio |
A sub-schema is a group of Data Elements called in the Segment.
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 |
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.
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. or 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-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. |
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. |
These lines are used for documentation purposes. Comments are available with all entities and allow you to write, edit text in relation to the selected instance. This tab allows you to write, modify, move or delete text lines using basic word processing functions.
Value | Comments |
---|---|
* or blank | Standard documentation line. |
A | Alias for the Segment name. |
On a blank-type line, you enter a free comment.
On an A-type line, enter the COBOL Segment name.
Values | Comments |
---|---|
T | Call of a text section. |
* | Line which will not be generated. It is used to insert a comment or an override. |
S | Replacement of an automatic error message. Automatic messages can be replaced by specific messages such as: ’THE ORDER NUMBER IS REQUIRED These messages are indicated on ’S’ type lines assigned to data element call lines (-CE lines tab) in the Segments. |
F | Data Element call |
U | Error message |
C | Comment |
D | Documentary messages. |
Type | Description |
---|---|
D | Column 1:
Column 2: blank Column 3:
Column 4: blank Column 5: Begin the documentary message or Enter the text and paragraph code being called. Two asterisks (**) for the paragraph code is a permitted value, it will call all the paragraphs of the text. |
S | Column 1: ERROR TYPE (2, 3, 4 or 5) Column 2: blank Column 3: ERROR GRAVITY (E, C or W) Column 4: blank Column 5: enter the message beginning here. |
For the ’Y: Pacbench’ organization, this field must contain the code of the COBOL COPY clause which represents the communication area of the Pacbench C/S Application Component which accesses the Logical View.
For an SQL Database Data Structure, this field must contain the code of the SQL block.
For any other Data Structure, the contents of this field depend on the value of the 'Type of COBOL code' in the Program Definition tab
Type of COBOL code | Field value |
---|---|
IBM OS/390 (COBOL type X) | DDNAME |
IBM DOS (COBOL type 1) | This field may take three forms:
|
COBOL II IBM z/VSE (COBOL type X) | The ASSIGN clause (for sequential files, ’S’ organization), with SYSnnn as external name, is generated in the following form: SYSnnn-UT-....-S-SYSnnn |
BULL Gcos7 (COBOL type 4) | INTERNAL-FILE-NAME |
BULL Gcos8 (COBOL type 5) | File code (2 characters) |
TANDEM (COBOL type F) | External name |
DEC/VMS (COBOL type I) | This field must contain LUnn (nn = 00 to 99). |
Value | Meaning |
---|---|
S: Sequential | Sequential access |
R: Direct / Random | The Read function is not generated automatically |
D: Dynamic | This value is reserved for VSAM files. |
Value | Comment |
---|---|
F: Fixed | At generation time, the lengths of the different records are aligned with the length of the longest record. |
V: Variable | |
U: Undefined | |
S: Spanned | This value is reserved for IBM MVS and DOS variants. |
Value | Can be selected with: |
---|---|
I: Input | The following usages: 'C: Consultation', 'T: Table stored in memory', 'X: Table partially stored in memory', 'M: Transaction to be validated', 'N: Transaction not to be validated' and 'P: Principal' |
O: Output | The following usages: 'D: Output file', 'S: Selected', 'R: Result', 'E: Transaction with error checking', 'I: Direct printing' and 'J: Indirect printing'. |
E: Output plus OPEN EXTEND clause | The following 'Type of Code to generate': GCOS7, GCOS8, IBM 36 or 38, IBM MVS VS, Unisys 2200, Tandem, Dec/Vax, Control Data Corp., Perkin Elmer, ICL 2900, SFENA or DPPX. |
R: Input / Output | A direct access Data Structure |
T: Sort | An Input or Output usage |
O is the default value.
1 to 9 levels, according to the number of Elements to be used for control break processing. These Elements are identified as the sort keys for this Data Structure.
When there is a control break processing on one or more Data Structures, two indicators keep track of the status of the records being processed
O is the default value.
1 to 9 levels. Enter the number of Elements (Elementary or Group) on which file matching is to be synchronized for this Data Structure. This number identifies the number of the key fields (identified in the Sort key composition field) that are involved in the synchronization.
For an automatic synchronization, the following conditions must be met:Value | Meaning |
---|---|
C: Consultation | Any input file |
D: Output file | Any output file |
P: Principal | Input file, likely to be updated by a transaction file (whose usage is 'M: Transaction to be validated' or ’N: Transaction not to be validated’) |
R: Result | Updated principal file in sequential access mode. (When the Data Structure contains an ’Occurs depending on’ clause, the output/result D.S must be declared as ’D: Output file’). |
S: Selected | Output file extracted from another file. It differs from the 'D: Output file' usage since the generated description in the output area is not detailed. For Data Elements with an ’Occurs depending on’ clause, the usage must be ’D: Output file’. |
T: Table stored in memory | A file to be fully stored in memory. The table is generated according to the number of occurs indicated on each Segment Definition. The maximum number of selected Segments per D.S. is 50. |
X: Table partially stored in memory | A file to be partially stored in memory. Fillers included in the Segment composition are not stored. Elementary Data Elements other than fillers are limited to 10 (in addition to the 'Record type Element') for the ’00’ Segment and to 29 for each specific non-00 Segment. |
M: Transaction to be validated | Input file to be validated which can update other file(s).
The generated functions range from 30 to 76. Note: Only one ’M’ or ’N’ Data
Structure is allowed per Program.
|
N: Transaction not to be validated | Input file which can update other files. The generated
functions are: 30, 33, 39, 70 to 76. Note: Only one ’M’ or ’N’ Data Structure
is allowed per Program.
|
E: Transaction with error checking | Output transaction file containing a field identifying
records with errors. The system will generate the field(s) to track the erroneous Elements, erroneous Segments and user-defined errors using the reserved Data Elements ENPR, GRPR and ERUT. (The option is selected in the RESERVED ERROR CODES IN TRANS. FILE field). Selected or not, the descriptions of these Elements are generated (using the Data Elements DE-ERR and ER-PRR). |
I: Direct printing | Direct printing (or by SYSOUT in IBM MVS). Upon generation, the lines whose 'Structure Identifier' is 00 in the Report will be ignored. |
J: Indirect printing | Indirect printing to be processed by a spool Program. The fields required to identify the lines, line skips... are indicated in the 'Structure Identifier' 00 in the Report. |
Y: Internal codification table |
They are identified by the value entered in the 'Sort key' field on the Segment -CE Lines tab.
The order for sorting these key Data Elements may be entered here using the values assigned on the -CE Lines tab in the desired order from major to minor - left to right.
If no explicit entry is made here, Elements coded with value 1 to 9 will be taken as the default.
It must contain a numeric value, which corresponds to the block size, i.e. the size of the physical record. Spaces and zeroes are equivalent.
If the Data Structure has a 'Usage' = 'P: Principal', you must enter the 'code in program' of the result output Data Structure (2 characters).
If the Data Structure has a 'Usage' = 'R: Result' or 'D: Output file', you must enter the 'code in program' of the principal input Data Structure (2 characters).
If the Data Structure has a 'Usage' = 'M: Transaction to be validated' or 'N: Transaction not to be validated', you must enter the 'code in program' (on 2 characters) of the transaction file containing the errors ('Usage' = 'E: Transaction with error checking'), if such a file has been called.
If the Data Structure has a 'Usage' = 'E: Transaction with error checking', you must enter the 'code in program' (on 2 characters) of the corresponding transaction file ('Usage' = 'M: Transaction to be validated' or 'N: Transaction not to be validated').
Value | Meaning |
---|---|
IBM DOS (Type of COBOL code = '1'): Enter the model type (examples: 2314, 3330, 2400). |
|
. EXT LS EXLS |
MICROFOCUS, COBOL II, IBM VISUAL SET (Type of COBOL code = '3'): Generation of the EXTERNAL clause at the file FD level Generation of the LINE SEQUENTIAL clause Generation of the LINE SEQUENTIAL clause and of the EXTERNAL clause at the file FD level |
. LS |
ACU COBOL (Type of COBOL code = 'Q') : Generation of the LINE SEQUENTIAL clause |
. SSF OUT |
Gcos7 (Type of COBOL code = '4'): Option WITH SSF in the SELECT clause Option -SYSOUT suffix after the filename in the SELECT clause (WITH SSF is generated). |
. PT CR SSF IBM xxx ..V |
Gcos8 ASCII (Type of COBOL code = '5'): Printer Card reader. ORGANIZATION IS GFRC SEQUENTIAL SSF CODE SET IS IS GBCD. ORGANIZATION IS IBM-OS SEQUENTIAL. WITH xxx. A ’V’ in the 4th position generates the clause ’VALUE OF FILE-ID is 3-FF00-IDENT’ (FF is the program Data Structure code being called). You must define the 3-FF00-IDENT field in the -W Lines tab. |
. DK or blank DKS DKM RD PT PO TP ... ..P ..R ..L ..S ..V |
BURROUGHS large system (Type of COBOL code = '8') UNISYS A Series: Disk Sort Disk (with T opening). Merge Disk (with T opening). Reader Printer File Tape For the 2-character codes, a third character can specify a particular final disposition: Purge Release Lock Save A ’V’ in the 4th position generates the clause ’VALUE OF D.S. NAME IS 3-FF00-IDENT’. |
. CR CP UN TP PN PT PF |
UNISYS 2200 (Type of COBOL code = 'U'): Card reader. Card punch. Uniservo. Tape Printer with external name. If the 'Complement' field contains input, the RECORDING clause is also generated. Printer without external name. Printer with external
name and
VALUE OF PRINTER-FORMS 3-FF00-FORMS LINAGE IS 3-FF00-LINES TOP IS 3-FF00-TOP BOTTOM IS 3-FF00-BOTTOM These 4 data-names are to be declared in Work Areas (-W lines) with their appropriate values. |
. DB RD CP PT TP DK or blank |
AS 400 (Type of COBOL code = 'O'): Database Reader Card Punch Printer Tape Disk |
Value | Type of COBOL code |
---|---|
R: Reader | IBM DOS (Type of COBOL code = '1') |
P: Punch | IBM DOS (Type of COBOL code = '1') |
S: EBCDIC set code | BULL Gcos8 (Type of COBOL code = '5') and UNISYS 2200 (Type of COBOL code = 'U') |
C: ASCII set code | BULL Gcos8 (Type of COBOL code = '5') |
O: OPTIONAL option not to be generated | BULL Gcos7 (Type of COBOL code = '4') and Gcos8 (Type of COBOL code = '5') |
A: ALLOWING ALL file optioning option & REGARDLESS sequential reading | DEC VAX VMS (Type of COBOL code = 'I') |
If you fill it in, it is recommended to specify a character string, on 10 characters maximum, in the following format:
You enter here the code (6 characters) of the Data Element whose values identify the different record types of a Data Structure.
This Data Element must belong to the common part Segment (00 Segment).
This name can also be specified in the 'Structure code' field of the Segment Definition tab.
You must specify the replacement values of the respective parameters in the form of character strings. Each occurrence of the parameter in the original Macro is then replaced by the value entered for this particular Program.
The number of characters used for each parameter value must correspond to the appropriate field length for the element being parameterized. For example, if $1 is being used as a Function code, the value must be two characters.