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 with a 'Block type' = ’R: Records’ 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 with 'Block type' = ’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' = '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).

Source Data Structure code

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').

Transaction break level
By default, the value of this field is that of the 'Break level' entered in the 'Usage definition' section. The value must be one-character long.
Note: All spaces are replaced with zeros.
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.
Physical unit type
The possible unit type varies according to the Type of COBOL code.
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

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 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')
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' you indicate in the Program Definition tab and to the Organization of the Data Structure call:
  • For VSAM files, the 'FILE STATUS IS' clause is generated using 1-ddss-eeeeee (declared as a two byte field).
  • For non-VSAM files, NOMINAL, SYMBOLIC or ACTUAL KEY are generated, according to the 'Type of COBOL code'. You must define the corresponding work area, i.e. 1-ddss-eeeeee. You must also specify, in specific code, the positioning of this key as well as the reading of the Data Structure.
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)