SDF syntax description

The metasyntax used in the option formats is explained in the following tables.

Table 5: Metacharacters

The option formats make use of certain symbols and notational conventions whose meaning is explained in the following table.

Symbol

Meaning

Example

UPPERCASE LETTERS

Uppercase letters indicate keywords. Some keywords are prefixed with *

LISTING = STD

SOURCE = *SYSDTA

=

The equal sign links an operand name with its associated operand values.

LINE-SIZE = 132

< >

Angle brackets indicate variables whose range of values is described by data types and suffixes (see table 6 and table 7).

... = <integer 1..100>

underscoring

Underscoring is used to indicate the default value of an operand.

MODULE-LIBRARY = *OMF

/

A slash separates alternative operand values.

SHAREABLE-CODE = NO / YES

(...)

Parentheses indicate operand values which introduce a structure.

TEST-SUPPORT = AID(...)

indentation

|

|

Indentation indicates dependence on a higher-ranking operand.

The vertical bar indicates related operands belonging to the same structure. It extends from the start to the end of the structure. A structure may contain additional structures within itself. The number of vertical bars preceding an operand corresponds to the structure depth.

LISTING = PARAMETERS(...)
	PARAMETERS(...)
	|	SOURCE = YES(...)
	|		YES(...)
	|		|	COPY-EXP...
	|		|	.
	|		|	.

,

A comma precedes further operands on the same structure level.

,SHARABLE-CODE =

,ENABLE-INITIAL-STATE=

Table 5: Metacharacters

Table 6: Data types

Variable operand values are represented in SDF by data types. Each data type represents a specific set of values. The number of data types is limited to those described in table 6.

The description of the data types is valid for all options. Therefore only deviations from table 6 are described in the relevant operand descriptions.

Data type	Character set	Special rules
alphanum-name	A...Z 0...9 $,#,@
composed-name	A...Z 0...9 $,#,@ hyphen period	Alphanumeric string that may be delimited by periods or commas into several substrings
c-string	EBCDIC characters	A string of EBCDIC characters in single quotes, optionally with the letter C prefixed.
filename	A...Z 0...9 $,#,@ hyphen period	Input format: cat:$user. {  file             | file(no)             | group             | group{(*abs) | (+rel) | (-rel)}            } :cat: optional entry of the catalog identifier; character set limited to A....Z and 0....9; maximum of 4 characters; must be enclosed in colons; default value is the catalog identifier assigned to the user ID, as specified in the JOIN entry. $user. optional entry of the user ID; character set restricted to A...Z and 0...9; maximum of 8 characters; $ and period are mandatory; default value is the user' s own ID. $. (special case) system default ID file file or job variable name; last character must not be a hyphen or period; a maximum of 41 characters; must contain at least A...Z. #file (special case) @file (special case) # or @ used as the first character identifies temporary files or job variables, depending on system generation. file(no) tape file name no: version number; character set is A...Z, 0...9, $, #, @. Parentheses must be specified. group name of a file generation group (character set: as for “file”) group{(*abs) | (+rel) | (-rel)} (*abs) relative generation number (0-99); positive or negative signs and parentheses must be specified. (+rel) (-rel) relative generation number (0-99); positive or negative signs and parentheses must be specified.
integer	0...9,+, -	+ or -, if specified, must be the first character.

Table 6: Data types

Table 7: Suffixes for data types

Data-type suffixes define additional rules for data-type input. They can be used to limit or extend the set of values. This manual makes use of the following short codes to represent data-type suffixes:

generation	gen
cat-id	cat
user-id	user
version	vers

The description of the data-type suffixes is valid for all options and operands. Therefore only deviations from table 7 are described in the relevant operand descriptions.

Suffix

Meaning

x..y

Length specification

x y	Minimum length for the operand value; x is an integer. Maximum length for the operand value; y is an integer.
x=y	The length of the operand value must be x exactly.

with-low

Lowercase letters accepted

without

-gen

-vers

-cat

-user

Restricts the specification options for a data type.

A file generation or file generation group may not be specified.

The version (see file(no)) may not be specified for tap files.

A catalog ID may not be specified.

A user ID may not be specified.

Table 7: Suffixes for data types