Table of Contents

Search

  1. Preface
  2. Introduction
  3. Defining a System
  4. Flattening IDTs
  5. Link Tables
  6. Loading a System
  7. Persistent-ID (Dynamic Clustering)
  8. Cluster Governance
  9. Static Clustering
  10. Simple Search
  11. Search Performance
  12. Miscellaneous Issues
  13. Limitations
  14. Error Messages

Loader Definition

Loader Definition

This begins with the
LOADER-DEFINITION
keyword. The fields are as follows:
Field
Description
NAME=
A character string that identifies a Loader-Definition. It is used when scheduling a Table Loader job. This is a mandatory parameter. The name must not match any Search-Definitions nor Multi-Search- Definition names in the same System.
COMMENT=
Free-form description of this Loader-Definition.
JOB-LIST=
A list of Job-Definition names that are to be executed when this Loader-Definition is scheduled to run. Up to 32 jobs may be listed. This is a mandatory parameter.
DEFAULT-PATH=
MDM-RE will create various files while processing some jobs. The
PATH
parameters can be used to specify where those files will be placed. This parameter overrides the value in the System Definition. MDM-RE will use the path specified in the
DEFAULT-PATH
parameter.
If
DEFAULT-PATH
has not been specified, the current directory will be used. It is valid to specify a value of "+" for the path. This represents the value associated with the environment variable
SSAWORKDIR
. This is especially recommended when running an API program and/or system remotely, that is from a directory other than the
SSAWORKDIR
directory.
SORT-WORK1-PATH=
MDM-RE will create sort work files during the Load. This parameter controls the placement of these files, and overrides the
DEFAULT-PATH
parameter in the Loader-Definition.
SORT-WORK2-PATH=
MDM-RE will create sort work files during the load. This parameter controls the placement of these files and overrides the
DEFAULT-PATH
parameter in the Loader-Definition.
OPTIONS=
This is used to nominate various options for the Loader.
APPEND
append records to the IDT and IDXs. If omitted, the loader will assume this is an initial load and create the IDT and IDXs.
APPEND
must not be used with synchronized source input, as IDTs created from synchronized data sources must be loaded with a single execution of the Table Loader.
KEEP-TEMP
keep temporary files. If omitted, temporary files are deleted when no longer necessary.
KEEP-LOG
keep Loader log files. If omitted, log files are deleted when the Loader completes successfully. Loader log files are copied to the Table Loader’s log file before being deleted.
FIXED
Create the IDT load file using fixed-length records instead of variable length delimited records. This option is necessary if the data contains any columns with binary values that are not permitted in a delimited file, that is, CR/LF, Ctrl-Z and/or the field delimiter character. Unicode data should always be loaded using fixed-length records.
The MS SQL Server interface always generates fixed length records, so this parameter does not need to be specified.
CONVENTIONAL-PATH
Oracle: instructs the Loader to invoke Oracle’s SQL*Loader without the
DIRECT-PATH
option. This degrades performance but enables SQL*Loader to load tables over a network when the version of SQL*Loader does not match the version of the database instance.
DIRECT-PATH
loads will specify the UNRECOVERABLE option. This means that all IDTs and IDXs should be backed up after being loaded as they can not be restored during media recovery.
UDB/DB2:
Conventional-Path
performs an Import operation. If not specified, the Loader runs the UDB Load utility.
MS-SQL Server:
has no effect.
GENERIC-LOAD
instructs the Loader to load records using the DBMS’ native insert and commit statements. This is provided as a "catch all" solution for those DBMSs that do not have a high-speed massload utility.

0 COMMENTS

We’d like to hear from you!