NonStop SQL/MP Reference Manual

NonStop SQL/MP Reference Manual—142115
L-28
LOAD Command
If you omit this option, LOAD leaves 15 percent slack space in both the data and
index blocks.
If you specify DSLACK, ISLACK, and SLACK, the LOAD utility uses the
DSLACK value for data blocks and the ISLACK value for index blocks. The
SLACK value is ignored.
move-option
specifies names of elements related to the table or file and how to map source names
to different target names.
SOURCEDICT dictionary-name
identifies the subvolume containing the DDL dictionary that contains the record or
DEF definition for an Enscribe input file. dictionary-name is a Guardian
subvolume name.
If you omit the SOURCEDICT option, LOAD assumes that the DDL dictionary
resides on the current default subvolume.
SOURCEREC ddl-record-name
identifies the name of the DDL record or DEF definition for an Enscribe input file.
ddl-record-name must be a valid DDL data name.
If you omit the SOURCEREC option, LOAD assumes that fields in the file occur in
the same order as the columns in the target table and that all variable-length
character fields are expanded to the maximum length and padded with blanks. For
information about how LOAD converts other data types if they are not explicitly
defined, see the Data type compatibility and field conversions item under
Considerations—LOAD
on page L-31.
TARGETDICT dictionary-name
specifies the subvolume containing the DDL dictionary that contains the DDL
record or DEF definition for an Enscribe output file. dictionary-name is a
Guardian subvolume name.
If you omit the TARGETDICT option, LOAD assumes that the dictionary resides on
the current default subvolume.
TARGETREC record-name
(for loading Enscribe files only) specifies the DDL record name of the record or
DEF definition for outfile.
If you omit the TARGETREC option, SQL assumes that fields in out-file occur
in the same order as fields or columns in in-file and that all variable-length
character fields are expanded to the maximum length and padded with blanks. For
information about how LOAD converts other data types if they are not explicitly
defined, see the Data type compatibility and field conversions item under
Considerations—LOAD
on page L-31.