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 using any standard text editor. Although it is not recommended, you can edit this file. Use caution when editing because Import requires a specific format for the statements in the file and deviations in the format may cause errors. The definition statements for exported objects are documented in the following pages.
You can import object definitions exported from an Optim Directory on MVS™. However, the definition statements differ, depending on the Optim z/OS® Solution component (e.g., ACCESS) that created the definition and the options in effect when the definition was created. These differences may include parameters that are not supported when importing definitions to Optim. You may need to edit the Optim z/OS Solution Output File before importing it to Optim.
Unsupported keywords and values from the Optim z/OS Solution definitions can result in errors when importing to Optim. These keywords and values must be removed from a file or edited before the definition can be imported. The keywords from Optim z/OS Solution definitions that are unsupported in Optim are listed after the discussion for each object type. Unsupported values for supported keywords are noted in the discussion for each keyword.
Additionally, definitions originating on MVS may contain parameters that are not relevant for Windows. These parameters have no effect when the definition is imported and used.
You must edit the names of the files (e.g., Extract Files, Control Files, Row List files, etc.) in the MVS definitions, to conform to Windows standards.
The following general format rules apply to the files:
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.
The definition statement syntax for each object type is documented in the following section. The syntax conventions for these statements are:
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.