DDS Syntax Coding Examples

Figure 2 through Figure 7 are syntax coding examples. Except for HLPARA, JFILE, JFLD, and PFILE, the keywords shown in these examples are not actual keywords. They simply indicate where you should specify the keywords.

Figure 2. Syntax for a Physical File

(1)

Comments (optional): Comments can appear on any line in DDS. They are identified by an asterisk in position 7.

(2)

File level (optional): File-level keywords appear before the record format name (RECORD on line 00040).

(3)

Record level (only one record is allowed in physical files): R in position 17 identifies RECORD as a record format name. The record level continues until the first field is named.

(4)

Field level (at least one field name is required, unless the FORMAT keyword is specified on the record): For fields in physical files, specify at least a name and length. Other attributes can be specified explicitly or by default.

(5)

Key field level (optional): K in position 17 identifies the field as a key field. A K must be specified for each key field. Specify the key field level by repeating a field name (here, FIELDA) after the field-level specifications.

Figure 3. Syntax for a Simple Logical File

(1)

Comments (optional): Comments can appear on any line in DDS. They are identified by an asterisk in position 7.

(2)

File level (optional): File-level keywords appear before the record format name (RECORD1 on line 00040).

(3)

Record level (at least one is required): R in position 17 identifies RECORD1 as a record format name. In simple or multiple format logical files, the PFILE keyword is required for every record format. The record level continues until the first field is named.

(4)

Field level: Field names and field attributes are not required for logical files. See "Keywords for Physical and Logical Files to Create DDS Files" for more information.

(5)

Key field level (optional): K in position 17 identifies the field as a key field. A K must be specified for each key field. Specify the key field level by repeating one or more field names (such as FIELDA) after the field-level specifications.

(6)

Select and omit levels (optional): S in position 17 identifies FIELDB as a select field. (O in position 17 identifies a field as an omit field.) The select and omit levels follow the key field level.

Figure 4. Syntax for a Join Logical File

(1)

Comments (optional): Comments can appear on any line in DDS. They are identified by an asterisk in position 7.

(2)

File level (optional): File-level keywords appear before the record format name (RECORD1 on line 00040).

(3)

Record level (exactly one required): R in position 17 identifies RECORD1 as a record format name. In join logical files, the JFILE keyword is required for the record format. The record level continues until the first join specification.

(4)

Join level: J in position 17 identifies the beginning of a join specification. At the join level, specify at least one join specification. Each join specification must include at least one JFLD keyword. There must be one JOIN keyword for each join specification in a join logical file if there is more than one join specification in the file. A join specification continues until the next join specification or field name.

(5)

Field level: At least one field name with usage other than N is required for join logical files.

(6)

Key field level (optional): K in position 17 identifies the field as a key field. A K must be specified for each key field. Specify the key field level by repeating one or more field names (such as FIELDA) after the field-level specifications.

(7)

Select and omit levels (optional): S in position 17 identifies FIELDB as a select field. (O in position 17 identifies a field as an omit field.) The select and omit levels follow the key field level.

Figure 5. Syntax for a Display File

(1)

Comments (optional): Comments can appear on any line in DDS. They are identified by an asterisk in position 7.

(2)

File level (optional): File-level keywords appear before the first record format name (RECORDA on line 00040).

(3)

Record level (at least one required): R in position 17 identifies RECORDA as a record format name. The record level continues until either the first field is specified or the first help specification.

(4)

Help level (optional): H in position 17 identifies the beginning of a help specification. A help specification continues until the next H in position 17 or until the first field. Each help specification must include at least one HLPARA keyword, and a HLPRCD or HLPDOC keyword.

(5)

Field level (optional): Display file fields that are passed between the display device and the program must be named fields and must have a length specified. Other attributes can be specified explicitly or by default. Constant (unnamed) fields require only a location and a keyword, as described in DATE, DFT, TIME, and MSGCON keyword descriptions in "Keywords for Display Files in DDS". Positions 17 through 38 do not apply to constant fields.

Figure 6. Syntax for a Printer File

(1)

Comments (optional): Comments can appear on any line in DDS. They are identified by an asterisk in position 7.

(2)

File level (optional): File-level keywords appear before the first record format name (RECORDA on line 00040).

(3)

Record level (at least one required): R in position 17 identifies RECORDA as a record format name. The record level continues until the first field is specified.

(4)

Field level (at least one field, whether named or unnamed, is required in each record format in the file): Printer file fields that are passed from the program to the printer must be named fields and must have a length specified. Other attributes can be specified explicitly or by default. Constant (unnamed) fields require only a location and a keyword, as described in the DATE, DFT, PAGNBR, TIME, and MSGCON keyword descriptions in "Keywords for Printer Files".

Figure 7. Syntax for an ICF File

(1)

Comments (optional): Comments can appear on any line in DDS. They are identified by an asterisk in position 7.

(2)

File level (optional): File-level keywords appear before the first record format name (RECORDA on line 00040).

(3)

Record level (at least one required): R in position 17 identifies RECORDA as a record format name. The record level continues until the first field is specified.

(4)

Field level (optional): ICF file fields must have at least a name (as in FIELDA) and a length. Other attributes can be specified explicitly or by default.