Output/Input File Format
The Export Utility generates a set of SQL-like statements for selected object definitions in the current Optim™ Directory and stores the statements in the Output File. This Output File is the input for the Import Utility.
The output from the Export Utility is a text file that can be viewed with any standard text editor. Although it is not recommended, you can edit this file. Use caution if you edit the file because Import requires a specific format for the statements in the file and deviations in the format might cause errors. The definition statements for exported objects are documented in the following pages.
MVS Definitions
Although the definition statements are different between the Optim Solution and the Optim z/OS® Solution, you can import object definitions that are exported from an Optim Directory on MVS™. To import files created on the Optim z/OS Solution, you have to specify the “Default Qualifier” (see Options tab in Import GUI).
Format Rules
The following general format rules apply to the files:
- Each statement begins at the first position of a line with the keyword CREATE.
- Each statement is terminated with a semicolon. Export inserts a blank line after the semicolon, but it is not required.
- At least one space is inserted between parameters.
- The qualifiers for individual objects in sets of specifications, such as the Table List entries for an Access Definition, are enclosed in parentheses.
- If the length of the statement exceeds the length
of the line, a break occurs before or after a parameter and its qualifiers.
The remaining text continues on the next line. Export indents the
continued text, but this is not required.
Long character strings, such as description text entries, Row List definitions, SQL WHERE clauses, or selection criteria text, are delimited by two forward slashes (//). Continuation characters are not used.
No spaces or indentations are added. (If you insert additional spaces or continuation characters, they are assumed to be part of the string.) The text continues for the complete length of the line, wrapping to the next line until the forward slashes are reached, indicating the end of the text.
Definition Statement Syntax
The definition statement syntax for each object type is documented in the following section. The syntax conventions for these statements are as follows:
- KEYWORD
- Statement keywords are shown in uppercase and must be supplied as shown.
- text
- Variable text is shown in lowercase italics.
- ( )
- Required as a statement delimiter to group a series of qualifiers for a parameter.
- [ ]
- Indicates an optional parameter.
- { }
- Indicates a choice of two or more settings from which one (and only one) must be selected.
- < >
- Indicates a choice of two or more settings from which none or any can be selected.
- |
- Separates options.
The syntax for Local and Named objects is the same, except that Local objects are preceded by the keyword LOCAL (for example, LOCALAD), and the associated parameters are delimited by parentheses or double slashes.