IBM InfoSphere Master Data Management, Version 10.1The mpxprep utility is a cross match program used to generate bulk cross match (BXM) data.
This utility can be run from the command line or from IBM® Initiate® Workbench . See the usage topics about IBM Initiate Workbench.
All options and flags are case independent; option values are not.
For incremental cross match (IXM), use –srcRecno or –[min/max]MaudRecno, but not both.
-memType and -entType cannot be specified at the same time.
| Option | Type | Description | Default |
|---|---|---|---|
| -bxmOutDir | dirName | Directory where you want any .bin output files located. This directory is relative to the instance work directory on the server hosting the hub. | NONE but required |
| -{no}bxmBktd | Generate MEMBKTD output | -bxmBktd | |
| -{no}bxmCmpd | Generate MEMCMPD output | -bxmCmpd | |
| -{no}bxmQryd | Generate MEMQRYD output. This option is for use with the relationship linker and instructs the mpxprep utility to create BXM files containing query data. The relationship types, attributes, and rules should already be defined so that mpxprep knows what data to include in the BXM file. | -bxmQryd | |
| -nMemParts | N | Number of member partitions. Member partitions (MemParts) are
used to partition up the data set. Typically option is set because
of memory considerations. Because the mpxlink utility
requires the entire input data set (for example, the binary files
of comparison results) to be read into memory at one time, breaking
the data set into smaller pieces allows them to fit into the available
memory on the server. MemParts breaks up the memHead and memCmpd data files. If you set a value other than 1 here, you must set a matching MemParts value for any downstream utility that uses the output of the mpxprep utility (such as mpxcomp or mpxlink). In other words, the MemParts setting in those downstream utilities must accurately reflect the number of partitioned file segments coming from the mpxprep utility. Leave this value set to 1 unless memory is an issue. |
1 |
| -nBktParts | N | Number of bucket partitions. Like the -nMemParts option
(Maximum number of Member Partitions in IBM Initiate Workbench),
the maximum number of bucket partitions option partitions the output
of the mpxprep process. As with MemParts, this
option is used when the output file is too large to be read into memory
in its entirety, and needs to be broken up into smaller sections to
fit into available memory. BktParts differs from MemParts in that it breaks up the membktd data. This option is the most common one used for reducing your memory footprint (and can also help sort performance on large data sets). |
1 |
| -minBktTag | N | Minimum bucket tag to use (0=any). This setting specifies the lowest bucketing role to be included in the operation. | 0 |
| -maxBktTag | N | Maximum bucket tag to use (0=any). This setting specifies the highest bucketing role to be included in the operation. | 0 |
| -nQryParts | N | Number of query partitions. Setting this partition depends on the size of your data set, your algorithms, and how much memory you have access to on the hub. Leave this setting at the default unless you need the memory. This option is enabled only when the option to generate query BMX (-bxmQryd) is also enabled. | 1 |
| -minQryRole | N | Minimum query role to use (0=all). The lowest query role designation used in the algorithm to include in the process. This option is enabled only when the option to generate query BMX (-bxmQryd) is also enabled. | 0 |
| -minMemRecno | N | Minimum memRecno filter (0=any). Specifies the lowest MEMRECNO to include in the process. | 0 |
| -maxMemRecno | N | Maximum memRecno filter (0=any). Specifies the highest MEMRECNO to include in the process. | 0 |
| -blkSize | N | Bulk size (number of members) | 1000 |
| -buffSize | N | Size (in bytes) for each file input and output (I/O) buffer | 65536 |
| -memType | Name | Member type name. If you have multiple member types in the hub database and need to generate BXM data for only one of those member types, the Member Type filter can be used. All entity types for that member are processed. | NONE |
| -entType | Name | Entity type name | NONE |
| -ixmMode | Used with IXM only. Indicates IXM mode | FALSE | |
| -minMaudRecno | N | Used with IXM only. IMinimum audRecno filter (0=any) | 0 |
| -maxMaudRecno | N | Used with IXM only. IMaximum audRecno filter (0=any) | 0 |
| -srcRecno | N | Used with IXM only. IsrcRecno filter (0=any) | 0 |
