SQL/MP Reference Manual

HP NonStop SQL/MP Reference Manual—523352-013
C-100
Enscribe Files and DDL Record Definitions
Executing the EDIT file with OBEY requires authority to read the EDIT file; authority to
write to the affected catalogs (for creating the table and indexes); authority to read the
DDL dictionary, the Enscribe source file, and the catalog in which the table is
described; and authority to read and write to the table (for loading the table and
indexes).
If you press the Break key while the CONVERT command is executing and the
BREAK_KEY option is ON, SQLCI stops execution, displays a message stating that
the command was terminated by a Break, and displays the standard SQLCI prompt.
The EDIT file is closed. If the BREAK_KEY option is OFF, control returns to the
previous Break key owner (usually the command interpreter process).
The CONVERT utility does not check any version information; therefore, the versions
of the table and any indexes you are creating cannot be greater than the version of the
catalog in which they will be registered.
CONVERT supports the HEADING, UPSHIFT, and HELP TEXT attributes.
Enscribe Files and DDL Record Definitions
CONVERT operates on Enscribe files only. CONVERT derives a table's file
organization and primary key location from the Enscribe file and derives column names
and column data types from the DDL record definition for the Enscribe file. CONVERT
also generates commands to create indexes on the table from the alternate key
specifications in the Enscribe file.
When a structured Enscribe file is converted to a table, the table is assigned the same
file organization as the file: key-sequenced, relative, or entry-sequenced. An
unstructured file is converted to an entry-sequenced table.
The file must have an associated DDL record definition. The actual file organization
and record length must be the same as the specifications for these attributes in the
DDL record definition.
If a DDL record definition defines an elementary item or group by means of a DDL DEF
structure, CONVERT uses the DEFs to convert the record definition, but a DEF does
not translate to an SQL data structure. During the conversion of a record definition,
CONVERT echoes the SQL table definition on the home terminal screen. (If you work
with data that includes multibyte characters, be aware that column DEFAULT clauses
can contain multibyte characters unsupported by the terminal and this can cause
unpredictable results in the screen display.)
DDL Primary Keys and Alternate Keys
CONVERT uses the primary key specification in the Enscribe file to assign the primary
key of the table. The SQL primary key is defined on columns derived from a field or
fields specified in the DDL record definition. If the key definition spans multiple fields, a
multicolumn SQL primary key is produced.