Rational Developer for System z, Version 7.5

More -CD specifications

You enter here 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, which corresponds to the block size, i.e. the size of the physical record. Spaces and zeroes are equivalent.

The block size can be zero for:
  • 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.
The BLOCK CONTAINS clause is not generated in the following cases:
  • Sort Data Structure,
  • Data Structure 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 = '1'),
  • Block 0 for UNISYS A Series (Type of COBOL code = '8') and AS 400 (Type of COBOL code = 'O').
  • Block 0 for IBM VSE COBOL II and file whose Block type is set to N: Ignore Block management.
Block type
Here you select whether the block size entered in the 'Block factor' field represents a number of records, characters, or whether it should 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
If the Data Structure has a Usage set to:
  • 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 set to E: Transaction with error checking), if such a file has been called.
  • 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).
  • 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, within the sort key, of the Action code (entered on the Segment Definition tab).
Example: if the value of the Sort key is ABCDE and the Action code is D, enter 4 here.
This is the most minor key of the sort key and the one used to differentiate one type of transaction from another in the same principal file. Duplicates are detected if any key elements below this one are found to match.
By default, the value of this field is that of the Break level already entered in the prevous windiw. 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:
  • Type of COBOL code = 1: IBM DOS/VSE: Enter the model type (examples: 2314, 3330, 2400)
  • Type of COBOL code = 3: UNIX, WINDOWS:
    • EXT = Generation of the EXTERNAL clause at the file FD level
    • LS = Generation of the LINE SEQUENTIAL clause
    • EXLS = Generation of the LINE SEQUENTIAL clause and of the EXTERNAL clause at the file FD level
  • Type of COBOL code = Q: ACUCOBOL:
    • LS = Generation of the LINE SEQUENTIAL clause
  • Type of COBOL code = 4: BULL GCOS7:
    • SSF = Option WITH SSF in the SELECT clause
    • OUT = Option -SYSOUT suffix after the filename in the SELECT clause (WITH SSF is generated).
  • Type of COBOL code = 5: BULL GCOS8:
    • PT = Printer.
    • CR = Card reader.
    • SSF = ORGANISATION IS GFRC SEQUENTIAL SSF CODE SET IS GBCD
    • IBM = ORGANISATION IS IBM-OS SEQUENTIAL
    • xxx = WITH xxx
    A V in the 4th position generates the clause VALUE OF FILE-ID is 3-FF00-IDENT (FF is the Data Structure Code in program). The field 3-FF00-IDENT must be defined in -W lines by the user.
  • Type of COBOL code = 8: UNYSIS A Series:
    • DK ou blanc = Disk
    • DKS = Sort Disk (with T opening).
    • DKM = Merge Disk (with T opening).
    • RD = Reader.
    • PT = Printer.
    • PO = File.
    • TP = Tape.
    For the 2-character codes, a third character can specify a particular final disposition:
    • P = Purge.
    • R = Release.
    • L = Lock.
    • S = Save.
    A V in the 4th position generates the clause VALUE OF D.S. NAME IS 3-FF00-IDENT.
  • Type of COBOL code = U: UNYSIS 2200 Series:
    • .CR = Card reader
    • CP = Card punch.
    • .UN = Uniservo.
    • .TP = Tape
    • PN = Printer with external name. If the ComplĂ©ment field contains a value, the RECORDING clause is also generated.
    • PT = Printer without external name.
    • PF = iPrinter 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.
  • Type of COBOL code = O: AS/400 :
    • RD = Reader.
    • CP = Card Punch
    • DB = Database
    • PT = Printer.
    • TP = Tape.
    • DK or blank = Disk.
Complement
This is a complement to the 'Physical unit type' field. The purpose of this field varies according to the 'Type of COBOL code'.
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 fill it in, it is recommended to specify a character string, on 10 characters maximum, in the following format:

ddsseeeeee, where:
  • dd = Data Structure
  • ss = Record (00 is recommended)
  • eeeeee = 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:
    • Generation of the NOMINAL, SYMBOLIC or ACTUAL KEY, according to the Type of COBOL code.
    • You must define the corresponding work area, e.g. 1-ddss-eeeeee. You must also specify, in specific code, the positioning of this key as well as the reading of the Data Structure.
    VSAM files,
  • For VSAM files:
    • Generation of the return code area of input-output operations,
    • Generation of the corresponding VALUE OF clause, only if it is defined as a work area and specified in specific code.
  • For BULL GCOS8:
    • Identification of the Data Structure,
    • Generation of the corresponding FILE STATUS IS clause, provided 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 Data Structures.

Record type Data Element code

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.

Related tasks
Adding external resources to a Program

Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)