Download User`s Manual

Introduction to IMT
"Build ISAM files
with packed keys
(no conversion)"
"Build ISAM files
with Binary keys"
N
N
Y
N
N
Y
Y
Y
7
Result
Default behavior. Keys are assumed
to be ASCII and are toggled to the
Unix format
Packed keys retain their exact
format for proper unpacking
operations
Binary keys (keys that contain bytes
both above and below \200\) are
toggled, but will sort the same as
they did under IRIS
Enables both options
Table 2
NOTE
Contiguous-Indexed files are copied with their IRIS string and BCD record
format intact. These files are displayed by QUERY as BCD files and by
SCAN as having the 'Q' attribute.
Polyfiles
IMT converts polyfiles by collecting the various volumes of a polyfile and converting
them into a single uniBasic Indexed File. The IRIS logical unit image file is scanned
and polyfile volumes are transferred to the temporary directory for polyfile conversion. This directory is specified during the IMT Initialization phase. In order to
build the file, all base volumes must be loaded (for key format information) as well
as volume 0. Data volumes may be copied anytime after the file is created in
uniBasic. In order to copy a directory, the base and extension volumes (for that
directory) must be loaded. If all of the required data is not available when
attempting to process a volume, the volume is saved for later processing when all
the necessary data is available. IMT will not try to process the polyfile until it has
all the necessary parts. The order that polyfile volumes are loaded does not matter
since the conditions described are checked for each volume encountered. However,
if you load all master volumes first, IMT will use disk space more efficiently since
IMT USER'S MANUAL