To display the content of the Data Structure Line Definition section, you must select a -CD Line, i.e. the first level of a Data Structure call. In the Data Structure Line Definition, you must give the Data Structure its code in the Program, its external name, its COBOL position and some physical characteristics.
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.
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). |
This field is used to obtain a Data Structure description in a particular area (communication area with DBMS's or LINKAGE SECTION that you must define in the -W Lines tab) or at the beginning of the WORKING-STORAGE SECTION.
This field is reserved for Data Structures whose organization is 'W: File description in Working', 'L: Working with placement' or 'D: DL1, IDS1 or II'. It places the I/O area in the WORKING-STORAGE SECTION.
To obtain the description of a Data Structure in the WORKING STORAGE SECTION, you should preferably use the -W Lines tab.
Value | Meaning |
---|---|
00 | The description of the Data Structure is inserted after all the Work Area lines |
Alphabetic characters | The description of the Data Structure is inserted after
all the Work Area lines whose COBOL position corresponds to this value. The description and Work Area lines are found at the beginning of the WORKING-STORAGE SECTION of the generated Program. These lines are displayed before Data Structures whose organization is W: 'File description in Working' and before those whose DS code in the Program is greater than this alphabetic code. Note: Do not
choose a COBOL position identical to the DS code in the Program for a Data
Structure with a 'W: File description in Working' organization.
|
Alphanumeric characters | The description of the Data Structure is inserted after
all the Work Area lines whose COBOL position corresponds to this value. The Work Area lines and the description can be found in the generated Program, at the end of the WORKING-STORAGE SECTION among the user areas. |
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 |
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.
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.
A sub-schema is a group of Data Elements called in the Segment.
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. |