More -CD specifications
You use this wizard to specify more physical information about the Data Structure line Definition in the Program.
- Block factor
- This field, on 5 characters, is required for the generation of the BLOCK
CONTAINS clause.
It must contain a numeric value. It corresponds to the block size (the size of the physical record). Spaces and zeros are equivalent.
The block size can be zero for the following operating systems:The BLOCK CONTAINS clause is not generated in the following cases:- IBM® OS, except for indexed Data Structures.
- IBM MVS™. The BLOCK CONTAINS clause is generated for a VSAM file only if the Library is in COBOL II.
- Sort Data Structure,
- Data Structure that is stored on a disk if no number is indicated,
- File whose Unit type is set to R: Slow device for IBM DOS (Type of COBOL code set to 1),
- Block 0 for UNISYS A Series (Type of COBOL code set to 8) and AS 400® (Type of COBOL code set to O).
- Block 0 for IBM VSE COBOL II and file whose Block type is set to N: Ignore block management.
- Block type
- Specify whether the block size that is entered in the Block factor field represents a number of records, characters, or whether it must be ignored for the block management.
- Result Data Structure code
If the Data Structure has a Usage set to P: Principal, you must enter the Code in program of the result output Data Structure (2 characters).
If the Data Structure has a Usage set to R: Result or D: Output file, you must enter the Code in program of the principal input Data Structure (2 characters).
- Source Data Structure code
- You must enter various information according to the value of the Data Structure
Usage:
- With 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 that contains the errors (Usage set to E: Transaction with error checking), if such a file has been called.
- With a Usage E: Transaction with error checking, you must enter the Code in program (on 2 characters) of the corresponding transaction file (Usage set to M: Transaction to be validated or N: Transaction not to be validated).
- With a Usage S: Selected, you must enter the Code in program (on 2 characters) of the input source. On the source Data Structure call line, you must enter the Code in program of the selected Data Structure.
- Transaction break level
- In a transaction file, you must enter the position of the Action code
(from the Segment Definition tab) within the sort key. Example: If the value of the Sort key is ABCDE and the Action code is D, enter 4.It is the most minor key of the sort key. It is used to differentiate one type of transaction from another in the same principal file. Duplicates are detected if any key elements after this one are found to match.By default, the value of this field is the value of the break level that is already entered in the previous window. The value must be one-character long.Note: All spaces are replaced with zeros.
- Physical unit type
- The possible unit type varies according to the Type
of COBOL code:
- If the Type of COBOL code is 1: IBM DOS/VSE, enter the model type (examples: 2314, 3330, 2400).
- If the Type of COBOL code is 3: UNIX, WINDOWS,
enter the following values:
- EXT for the generation of the EXTERNAL clause at the file FD level.
- LS for the generation of the LINE SEQUENTIAL clause.
- EXLS for the generation of the LINE SEQUENTIAL clause and of the EXTERNAL clause at the file FD level.
- If the Type of COBOL code is Q: ACUCOBOL, enter LS for the generation of the LINE SEQUENTIAL clause.
- If the Type of COBOL code is 4: BULL GCOS7, enter
the following values:
- SSF for the option WITH SSF in the SELECT clause.
- OUT for the option -SYSOUT suffix after the file name in the SELECT clause (WITH SSF is generated).
- If the Type of COBOL code is 5: BULL GCOS8, enter
the following values:
- PT for printer
- CR for card reader
- SSF for ORGANIZATION IS GFRC SEQUENTIAL SSF CODE SET IS GBCD
- IBM for ORGANIZATION IS IBM-OS SEQUENTIAL
- xxx for WITH xxx
- If the Type of COBOL code is 8: UNYSIS A Series,
enter the following values:
- DK or blank for disk
- DKS for sort disk (with T opening)
- DKM for merge disk (with T opening)
- RD for reader
- PT for printer
- PO for file
- TP for tape
- P for purge
- R for release
- L for lock
- S for save
- If the Type of COBOL code is U: UNYSIS 2200
Series, enter the following values:
- CR for card reader
- CP for card punch
- UN for UNISERVO
- TP for tape
- PN for printer with external name. If the Complement field contains a value, the RECORDING clause is also generated.
- PT for printer without external name
- PF for printer with external name and the following lines:
- VALUE OF PRINTER-FORMS 3-FF00-FORMS
- LINAGE IS 3-FF00-LINES
- TOP IS 3-FF00-TOP
- BOTTOM IS 3-FF00-BOTTOM
- If the Type of COBOL code is O: AS/400, enter the
following values:
- RD for reader
- CP for card punch
- DB for database
- PT for printer
- TP for tape
- DK or blank for disk
- Complement
- It is a complement to the Physical unit type field.
The purpose of this field varies according to the Type
of COBOL code.
Table 1. Values of the complement to the physical unit type Value Type of COBOL code R: reader 1: IBM DOS/VSE P: punch 1: IBM DOS/VSE S: EBCDIC set code 5: BULL GCOS8 and U: UNYSIS 2200 Series C: ASCII set code 5: BULL GCOS8 O: OPTIONAL option not to be generated 4: BULL GCOS7 and 5: BULL GCOS8 A: ALLOWING ALL file optioning option & REGARDLESS sequential reading I: DEC VAX VMS
- File status
- This field is optional.
If you specify it, you are advised to specify a character string, on 10 characters maximum, in the following format: ddsseeeeee. In this format, dd is the Data Structure, ss is the record (00 is advised), and eeeeee is the Data Element.
The use of this field varies according to the Type of COBOL code and to the Data Structure call Organization.- For non-VSAM files and all environments except BULL GCOS8, the nominal, symbolic, or actual key, is generated according to the Type of COBOL code. You must define the corresponding work area (for example 1-ddss-eeeeee). You must also specify, with specific code, the positioning of this key and the reading of the Data Structure.
- For VSAM files, the return code area of input/output operations is generated. The corresponding VALUE OF clause is generated only if it is defined as a work area and specified in specific code.
- For BULL GCOS8, the Data Structure is identified. The corresponding FILE STATUS IS clause is generated if it is defined as a work area and specified in specific code.
- Access key Data Element code
This code, on 6 characters, is required for indexed files.
A free reference is set when you indicate a Data Element in this field.
Content assist is available on this field, as shown by the symbol
in front of the field. To activate it, press Ctrl+Space. A subreference link is automatically created, even if the instance does not exist. From the target instance in the subreference results, you can start a super reference search.
- Record type Data Element code
Enter 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.