mpxlink utility

This directory is typically the work directory on the server that hosts your hub configuration. This option is required and there is no default setting.

You can list multiple directories for this option; separate multiple directories with single spaces.

WAS_PROFILE_HOME\installedApps\YOUR_CELL_NAME\MDM-native-IDENTIFIER.ear\native.war\work\project_name\work\bxm_output_dir

Also generate bulk cross match data in the designated BXM output directory.

This directory is typically relative to the work directory on the server that hosts the hub configuration.

Generating the output in binary form is optional; specifying an output directory with this option is what causes binary output to be generated. In other words, if no directory is specified here, no binary output is generated.

The MemParts option differs from the MxmParts option in that MemParts breaks up the memHead and memCmpd data files, whereas MxmParts breaks up link and task files (the output of the mpxcomp utility).

The MemParts value set here must be the same as the MemParts value set in mpxcomp, and in the utility that created the input for mpxcomp (for example, mpxfsdvd, mpxprep, or mpxredvd). In other words, the MemParts setting in mpxcomp determines how many partitioned file segments are passed to mpxlink; the mpxlink MemParts setting must accurately reflect the number of partitioned file segments that come from mpxcomp.

There is a performance consideration to partitioning the data set: the higher the MemParts is set, the slower the mpxlink process.

Leave this value set to 1 unless memory is an issue. The maximum value is 100.

The MxmParts option differs from MemParts in that MxmParts breaks up link and task files (the output of the mpxcomp utility), whereas MemParts breaks up the memHead and memCmpd data files.

The MxmParts value set here must be the same as the MxmParts value set in mpxcomp, which provides the input to mpxlink. In other words, the MxmParts setting in mpxcomp determines how many partitioned file segments are passed to mpxlink. The mpxlink utility MxmParts setting must accurately reflect the number of partitioned file segments that come from the mpxcomp utility.

Leave this value set to 1 unless memory is an issue. The maximum value is 100.

The input data used here is created with the corresponding mpxcomp-bxmDiff option (Use explicit different records from entrule option in InfoSphere MDM Workbench).

The input data used here is created with the corresponding mpxcomp utility -bxmSame option (Use explicit same records from entrule in InfoSphere MDM Workbench).

The input data used here is created with the corresponding mpxcomp utility -bxmRvid (Use reviewid records from mpxcomp in InfoSphere MDM Workbench).

The input data used here is created with the corresponding mpxcomp utility -bxmRvid option (Use reviewid records from mpxcomp in InfoSphere MDM Workbench).

For example, if memrecnos 1, 2, and 3 are in a Potential Duplicate task, they are all assigned tskset=1. If memrecnos 4 and 5 are in Potential Linkage task, they are assigned tskset=2, and so on.

Typically, you would not run mpxlink with the tskSets option on. The TskSets functionality has two purposes.  The first is for reporting, so that you can see how many members are involved in a task (although a member can only belong to one task set, so counts can be off for a member that is the glue member). The count is not updated either. The count is valid for a point-in-time when the task is first created. Therefore, if you have member additions or updates, they are not reflected in the count later.

The second purpose is used to make tasks that will not be automatically broken up by operational server scoring. For example, a member enters the witness protection plan and thus has two sets of demographics. The operational server will not naturally join them in an entity or task, so this option could be used to create a task.

If you manually create a task, the tskSetno gets set just as it does when you run a bulk cross-match (BXM) with the -tskSets option turned on. Setting this option instructs the operational server to, no matter what these members score, leave the task alone. In this case, even if a member has demographic changes that would cause the task to go away, the operational server will ignore it.

There may be some circumstances where you might want this behavior (for example, in a data quality remediation [DQR] or some other process where you require the task population to remain static). However, the majority of implementations would not want to use this default behavior.

Disable this option to instruct mpxlink to ignore anomalies in the data. For example, inconsistencies or discrepancies that arise from live updates to the table. (That is, discrepancies that might occur because data is changing from updates as it is being collected by the mpx utilities that create the input for mpxlink.)

This option is typically used for reporting purposes.

The option allows for specifying an entity record number to start with for the creation of the mpi_entlink_xx.unl file. The parameter is optional. If not set, then the mpxlink utility defaults to applying 1 as the starting entity record number.