|
Other manuals for this model:
manual abstract
Configuration
Configuring LOADER
Note: The Loader handles both Enscribe files where the primary key consists of
the entire record and the loading of key-sequenced SQL/MP tables where
all columns are in the key. The Loader will detect if all columns in the SQL
table are in the key. It will then delete and insert each row to be loaded
(inside the same transaction) instead of updating the first non-key column.
KEYVALUESTOP <
This parameter is used to specify the point in the file at which LOADER is to stop
reading a key-sequenced Enscribe file. The reading stops when it detects a
record that matches the stop value. Please note that the record at which it stops
reading is not included in the load. The value(s) entered can be any subset of
the left most significant bytes of the key you elect to read by. The value(s)
entered can be input as strings or their byte equivalents. Byte equivalents can
be entered in decimal, octal (by preceding the value with 0) or hexadecimal (by
preceding the value with 0x) format. If an alternate key is specified, the value
can be the full alternate key concatenated with any subset of the left most
significant bytes of the primary key. You can specify a stopping point without
having entered a starting point. If the string entered contains a space, the value
entered must be surrounded by double quotes. For example,
PARAM KEYVALUESTOP “’Smith, Bob’”
Please refer to the section on the KEYVALUESTART parameter for more
information on entering values for this parameter.
LOADFNAME
[\system.] [$volume.] [subvolume.] filename
This required parameter identifies the name of the file or table from which the
data is to be loaded. This should match the DBS parameter SOURCEFILE that
you want to load. Filename cannot contain any wildcard (*) or position holder (?)
characters.
When loading an Enscribe source file, you can specify the primary or a
secondary partition. If you specify the primary partition for a key sequenced file,
you can specify a KEYSPECIFIER to change the access path from the primary
key to an alternate key. If you specify a secondary partition, you should plan to
load the data in ascending primary key order; you should not use the
KEYSPECIFIER clause (only use the KEYSPECIFIER when the primary partition
is specified). If no KEYVALUESTART clause is specified, LOADER will start at
the base of the key values contained in that partition (no KEYSPECIFIER), or the
base key values along that alternate key path (KEYSPECIFIER is supplied). Use
the KEYVALUESTART to modify this primary key or alternate key path starting
position.
When loading an SQL source table, you should ALWAYS specify the primary
partition of the table, even if you want to load data contained in another partition.
This is because the SQL file system always opens the primary partition anyway
when you supply a secondary partition (the secondary partitions include a link
back to the primary partition). To set the starting and/or ending key values, or to
HP NonStop Shadowbase Autoloader Manual—785422-001
14
...
Desktops - HP Integrity NonStop J-Series (563.68 kb)