-CD Line Definition (Report)

To display the contents of this section, you must select a Report CD line, that is the first level of a Report call in the table, or click Add Report. You must give the Report a code in Program, an external name, a COBOL position and some physical characteristics. With the More button, you access another window that contains additional physical characteristics.

Code in program
This code is two characters long. The first character must be alphanumeric and the second character must be either numeric or alphabetic.

It sets the sequence in which the Data Structure or Report is processed in the program.

When the Data Structure or Report is used only once in a program, it is advised to indicate the code that is entered as the Data Structure or Report name. This name is entered upon creation. However, if it is called more than once in a program, you can differentiate these calls.

You can parameterize this code in a Macro with $n.

External name
This field is optional, on six characters maximum.
COBOL position
This field can contain two characters. It concerns the main description of a Data Structure (ddss) and not the descriptions that are preceded by a prefix (1-ddss or 2-ddss).

This field is used to obtain a Data Structure description in a particular area (communication area with DBMS or LINKAGE SECTION) or at the beginning of the WORKING-STORAGE SECTION.

This field is reserved for Data Structures whose organization is W: File description in Working or L: Working with placement.

To obtain the description of a Data Structure in the WORKING-STORAGE SECTION, you are advised to indicate it in the work area lines of the COBOL code, using micropatterns.

Table 1. Values of the COBOL position
Value Meaning
00 The description of the Data Structure is inserted after all the work areas.
Alphabetic characters The description of the Data Structure is inserted after all the work areas whose COBOL position corresponds to this value.

The description and work areas are found at the beginning of the WORKING-STORAGE SECTION of the generated program. These lines are displayed before the Data Structures whose organization is W: File description in Working and before the Data Structures whose code in the Program is greater than this alphabetic code.

Note: Do not select a COBOL position identical to the Data Structure 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 areas 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.

Note: With ORACLE, you must use numeric values so that the DECLARE SECTION is correctly generated (with data fields and indicators included in it).

Organization definition

Organization
Select an organization value.

You can select 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.

Table 2. Possible values for the organization
Value Comment
S: Sequential Only authorized value for a Report, a sequential file or a sort file Data Structure.
V: VSAM, UFAS One of the two possible values for an indexed file Data Structure

This value generates the STATUS KEY IS clause. The corresponding field is declared in the File Status field of the -CD Line Definition of the -CD Lines tab (the part that can be viewed by clicking More).

I: Indexed 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 is generated in 3 work areas:
  • LE-FILE,
  • LE-DATA
  • INVKEY.
The VALUE of LE-DATA is the external file name that 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 function.
L: Working with placement File descriptions are generated in the WORKING-STORAGE SECTION, in the location you indicate in the COBOL position field.
W: File description in Working File descriptions are generated in the WORKING-STORAGE SECTION, before the WSS-BEGIN constant.
Y: Pacbench C/S Call of the COPY clause that corresponds to the communication area between the client and the server (Pacbench C/S Business Components only).
X: Comment Data Structure that is used as a comment, not used for generation.
2: DB2 Segments or VAX/SQL Generation and description of a DB2® or VAX/SQL Segment. Only the 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 (MICRO FOCUS).
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 IDMS
A: ADABAS ADABAS
T: TOTAL files TOTAL files
O: ORACLE (< V6) ORACLE (< V6)
C: INTEREL RDBC or RFM INTEREL RDBC or RFM
R: RDMS RDMS
4: DB2/400 DB2/400
M: DATACOM DB DATACOM DB
N: NONSTOP SQL NONSTOP SQL
P: ORACLE V6 and V7 ORACLE V6 and V7
9: INFORMIX, SYBASE, INGRES/SQL, or SQL SERVER INFORMIX, SYBASE, INGRES/SQL, or SQL SERVER
Z: Data Structure for SOCRATE/CLIO Data Structure for SOCRATE/CLIO
F: Formal for SOCRATE/CLIO Formal for SOCRATE/CLIO
Access mode
You specify the way the Data Structure is accessed by the Program
Table 3. Values of the access mode
Value Comment
S: Sequential Sequential access
R: Direct / Random The read function is not generated automatically
D: Dynamic This value is reserved for VSAM files.
Input/Output mode
Table 4. Values of the input/output mode
Value Comment
I: Input Can be selected with a usage set to 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 Can be selected with a usage set to 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 Can be selected with a Types of Code to generate set to 4: BULL GCOS7, 5: BULL GCOS8, 0: IBM MVS/ESA OS/390, U: UNYSIS 2200 Series, F: TANDEM, I: DEC/VAX VMS, and K: ICL 2900
R: Input / Output Direct-access Data Structures only
T: Sort In input or output, depending on the usage
Unit type
The value of this field is important in the Types of COBOL code for which the ASSIGN clause, the FD level, and the WRITE statements are dependent on the selected unit type.

Usage definition

Usage
This code defines the role of the Data Structure in the Program and determines the generated functions.
Table 5. Values of the Data Structure usage
Value Comment
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 Data Structure must be declared as an D: Output file).
S: Selected Output file that is extracted from another file.

It differs from the D: Output file usage because 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 occurrences that is indicated on each Segment Definition. The maximum number of selected Segments for each Data Structure 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 files. The generated functions range from 30 to 76.
Note: Only one M: Transaction to be validated or N: Transaction not to be validated Data Structure is authorized in a Program.
N: Transaction not to be validated Input file that can update other files. The generated functions are: 30, 33, 39, 70 - 76.
Note: Only one M: Transaction to be validated or N: Transaction not to be validated Data Structure is authorized in a Program.
E: Transaction with error checking Output transaction file that contains a field that identifies records with errors.

Generation of the fields to track the erroneous Data Elements and Segments, and the user-defined errors by using the reserved Data Elements ENPR, GRPR, and ERUT. Selected or not, the descriptions of these Data Elements are generated (using the DE-ERR and ER-PRR Data Elements).

I: Direct printing Direct printing (or by SYSOUT in IBM MVS™).

Upon generation, the lines whose structure identifier is 00 in the Report are ignored.

J: Indirect printing Indirect printing to be processed by a spool program.

The fields that are required to identify the lines and line skips for example are indicated in the structure identifier 00 in the Report.

Y: Internal codification table  

Others

Format type
You select the format of the Data Elements that are called in the Segments of the Data Structure.
You must select the format according to the usage of the Data Structure, which is specified in the -CD Lines tab of the Program editor. This field does not apply to the Data Structures whose usage is I: Direct printing or J: Indirect printing.
Note: The Data Elements making up the Segments must not exceed 999 characters.
Table 6. Format types for Data Elements
Value Comment
E : Input Default value for Data Structures with a usage set to M: Transaction to be validated, N: Transaction not to be validated, or E: Transaction with error checking
I: Internal Default value for Data Structures whose usage is not set to: M: Transaction to be validated, N: Transaction not to be validated, or E: Transaction with error checking
S: Output  
Subschema
A subschema is a group of Data Elements that are called in the Segment.

This field is used with the Pactables function, to indicate which subschema is to be described. It is numeric, from 0 to 9 (0 corresponds to subschema 10).

Generated description type
You select the type of record description to be used in the COBOL program to allow different uses of the Segment description that is stored in the Library.
Table 7. Values of the generated description types
Value Meaning
Redefined records No VALUE clause is generated
1: Records without initial values Records without initial values or occurs. These records contain the Segment common part, followed by the different specific parts.

If the Data Structure description is included in the COBOL FILE SECTION, the COBOL record level field must be set to 2: COBOL 01 level for DS area and Segments at 02 level.

With this value, the specific Segments are described without redefines, at the COBOL level 02. Several Segment descriptions are grouped 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 can also default to blank or zero depending on the format. Initial values are also generated for the multiple occurrence fields if the Generated language of the Library is set to D: COBOL II, 85, LE.
3: Records with occurs (used with level 2) Records that incorporate the number of occurrences that are indicated in the Table size field of the Segment Definition tab.

No VALUE clause is generated.

If the Data Structure description is included in the COBOL FILE SECTION, the COBOL record level field must be set to 2: COBOL 01 level for DS area and Segments at 02 level.

You cannot use this description type if the common part Segment of this Data Structure is assigned a value in the Table size field of the Segment Definition. In that case, set the Organization to W: File description in Working and the Usage to T: Table stored in memory.

4: Records with occurs (used with level 3) Records that incorporate the number of occurrences that are indicated in the Table size field of the Segment Definition tab.

The associated COBOL record level must be set to 3: COBOL level varying with records description type

Comment specific to the OnLine Systems Development function: The index is not generated if the Generated description type is set to 4: Records with occurs (used with level 3), and the COBOL record level is set to 3: COBOL level varying with records description type,

The COBOL level 02 provides an access to the table that consists of the repetition of a record.

The COBOL level 01 consolidates all the Data Structure information (common part and specific parts that are repeated or not). A group level field that incorporates all the instances is generated.

You cannot use this description type 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, set the Organization to W: File description in Working, and the Usage to T: Table stored in memory.

COBOL record level
This option is used with the Generated description type field. It defines the COBOL level number for the descriptions of Data Structures, Segments, and Data Elements. In the following descriptions, the expression "D.S. area" is meant as the dd00 area (possibly 1-dd00, 2-dd00).
Table 8. Possible values for the COBOL record level
Value Meaning
1: COBOL 01 level for DS area and Segments If the Data Structure description is included 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 is only included 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 are described at level 02. Preferably set the Organization to L: Working with placement and define the higher levels through work areas.
3: COBOL level varying with records description type Level 02 for D.S. area and 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 and level 03 for Segments if the Generated description type is set to 4: Records with occurs (used with level 3).

Level 03 for both the 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 the D.S. with an Organization set to L: Working with placement and a Usage set to D: Output file.

Level 02 for group Data Elements or elementary Data Elements that are not part of a group. The elementary Data Elements that are part of a group are displayed but the D.S. area and Segment levels are not included.

Level 01 is to be defined in the work areas.

5: COBOL 01 level for Data Elements, DS areas and Segment levels disappear Organization set to L: Working with placement or W: File description in Working and a Usage set to D: Output file.

Level 01 for the group Data Elements or elementary Data Elements that are not part of a group. The elementary Data Elements that are part of a group are displayed but the D.S. area and Segment levels are not included.


Feedback