SDF syntax representation

This syntax description is based on SDF Version 4.7. The syntax of the SDF command/statement language is explained in the following three tables.

Table 4 : Metasyntax

Certain characters and representations are used in the statement formats; their meaning is explained in table 4.

Table 5 : Data types

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

The description of the data types is valid for all commands and statements. Therefore only deviations from table 5 are explained in the relevant operand descriptions.

Table 6 : Data type suffixes

The description of the “integer” data type in table 6 also contains a number of items in italics. The italics are not part of the syntax, but are used merely to make the table easier to read.

The description of the data type suffixes is valid for all commands and statements. Therefore only deviations from table 6 are explained in the relevant operand descriptions.

Representation        

Meaning

Examples                                                           

UPPERCASE LETTERS

Uppercase letters denote keywords. Some keywords begin with *.

OPEN DATABASE

COPY-NAME = *NONE

=

The equal sign connects an operand name with the associated operand values.

CONFIGURATION-NAME = <name 1..8>

< >

Angle brackets denote variables whose range of values is described by data types and their suffixes (Tables 5 and 6).

DATABASE = <dbname>

Underscoring

Underscoring denotes the default value of an operand.

SCHEMA-NAME = *STD

/

A slash separates alternative operand values.

CMD = *ALL / <dal-cmd>

(...)

Parentheses denote operand values that initiate a structure.

*KSET-FORMAT(...)

Indentation

Indentation indicates that the operand is dependent on a higher-ranking operand.

USER-GROUP-NAME = *KSET-FORMAT(...)
	*KSET-FORMAT(...)
		|	HOST = <host>

|

|

|

A vertical bar identifies related operands within structure. Its length marks the beginning and end of a structure. A structure may contain further structures.
The number of vertical preceding an operand corresponds to the depth of the structure.

USER-GROUP-NAME = *ALL-EXCEPT(...)
	*ALL-EXCEPT(...)
		|	NAME = *KSET-FORMAT(...)
		|		*KSET-FORMAT(...)
		|			|	HOST = <host>
		|			|	...

,

A comma precedes further operands at the same structure level.

,SPACE = STD

list-poss(n):

list-poss signifies that the operand values following it may be entered as a list. If a value is specified for (n), the list may contain no more than that number of elements. A list of two or more elements must be enclosed in parentheses.

NAME = list-poss(30): <subschema-name>

Table 4: Metasyntax

Data type	Character set	Special rules
alog-seq-no	0..9	1..9 characters
appl	A..Z 0..9 $,#,@ Structure identifier: hyphen	1..8 characters String that can consist of a number of substrings separated by hyphens; first character A..Z or $, #, @ Strings of less than 8 characters are filled internally with underscore characters.
catid	A..Z 0..9	1..4 characters must not start with the string PUB
copyname	A..Z 0..9	1..7 characters, starting with A..Z
c-string	EBCDIC characters	1..4 characters Must be enclosed in single quotes; the letter C may be used as a prefix. Single quotes within c-string must be specified twice.
csv-filename	A..Z 0..9 Structure identifier: hyphen	1..30 characters Must be enclosed in single quotes
dal-cmd	A..Z 0..9 hyphen	1..64 characters
date	0..9 Structure identifier: hyphen	Date specification Input format: yyyy-mm-dd yyyy : year; may be 2 or 4 digits long mm : month dd : day
dbname	A..Z 0..9	1..17 characters, starting with A..Z
device	A..Z 0..9 $,#,@ Structure identifier: hyphen	5..8 characters, starting with A..Z or 0..9 String that can consist of a number of substrings separated by hyphens and and whicch corresponds to a device. In the dialog guidance, SDF shows the permissible operand values. Information as the possible devices can be found in the relevant operand description.
host	A..Z 0..9 $,#,@ Structure identifier: hyphen	1..8 characters String that can consist of a number of substrings separated by hyphens; first character A..Z or $, #, @ Strings of less than 8 characters are filled internally with underscore characters.
integer	0..9,+,-	+ or - may only be the first character.
kset	A..Z 0..9 $,#,@ Structure identifier: hyphen	1..8 characters String that can consist of a number of substrings separated by hyphens; first character A..Z or $, #, @ Strings of less than 8 characters are filled internally with underscore characters.
name	A..Z 0..9 $,#,@	1..8 characters Must not consist only of 0..9 and must not start with a digit
realm-name	A..Z 0..9 Structure identifier: hyphen	1..30 characters String that may consist of a number of substrings by hyphens; first character: A..Z
realmref	0..9	1..3 characters
record-name	A..Z 0..9 Structure identifier: hyphen	1..30 characters String that can consist of a number of substrings separated by hyphens; first character: A..Z In the case of record types with a search key it is recommendable to use names with no more than 26 characters, otherwise the set name created implicitly (SYS_...) will be truncated in accordance with the restriction on the name length for sets.
recordref	0..9	1..3 characters
schema-name	A..Z 0..9 Structure identifier: hyphen	1..30 characters String that can consist of a number of substrings separated by hyphens; first character: A..Z
set-name	A..Z 0..9 Structure identifier: hyphen	1..30 characters String that can consist of a number of substrings separated by hyphens; first character: A..Z
structured-name	A...Z 0...9 $, #, @ hyphen	Alphanumeric string which may comprise a number of substrings separated by a hyphen. First character: A...Z or $, #, @
subschema-name	A..Z 0..9 Structure identifier: hyphen	1..30 characters String that can consist of a number of substrings separated by hyphens; first character: A..Z
time	0..9 Structure identifier: colon	Time-of-day specification { hh:mm:ss | hh:mm | hh } hh, mm, ss: Leading zeros may be omitted
userid	A..Z 0..9 $,#,@	1..8 characters, beginning with A..Z or $,#,@ BPRIVACY: Strings of less than 8 characters are filled internally with underscore characters.
volume	A..Z 0..9 $,#,@	1..6 characters starting with A..Z or 0..9
x-string	Hexadecimal: 00..FF	1..8 characters Must be enclosed in single quotes and prefixed with the letter X. There may be an odd number of characters

Table 5: Data types

Suffix

Meaning

x..y unit

For the “integer” data type: range specification.

x	Minimum value permitted for “integer”. x is an (optionally signed) integer.
y	Maximum value permitted for “integer”. y is an (optionally signed) integer.
unit	for “integer” only: additional units. The following units may be specified: Mbyte, Kbyte, seconds

Table 6: Data type suffixes