Capture Same/Diff Rule for an Entity (mpxrule)
This job writes out "same rule" or "different rules" for a given entity type to .bin files.
The Capture Same/Diff Rule for an Entity (mpxrule) job must be run before running the Link Entities (mpxlink) job if you select the Same (identity) and/or Diff (non-identity) option in mpxlink.
||This option identifies the type of entity being
computed. If you are implementing multiple entity types (for example,
id for Identity and hh for Household), you must run Capture Same/Diff
Rule for an Entity (mpxrule) for each type.
Default: varies depending on available types
||This is the directory in which you want the
Capture Same/Diff Rule for an Entity (mpxrule) output binary files
located. This is typically relative to the work directory on the server
hosting the operational server configuration.
|Use explicit different records from entrule||
This option controls whether
Link Entities (mpxlink) job uses existing entity rules when forming
entities. For example, if the users broke two members in an entity
apart in InfoSphere® MDM
a non-identity rule is created by InfoSphere MDM (likewise
if two members are manually linked, an "identity" rule is created).
The mpxrule utility captures these rules as "same" or "diff" rules
(identity or non-identity). If the user is "re-crossmatching" an existing
database, including these rules prevents the Link Entities (mpxlink)
job from reforming linkages (in the case of diff rules), or force
members to be in the same entity (in the case of a "same" rule). The
input data used here is created with the corresponding Use
explicit different records from entrule (
|Use explicit same records from entrule||
The input data used here is created
with the corresponding Use explicit same records from entrule (
|Trace logging||Produces a trace of activity as interactions
flow through the system. This option is very verbose and should only
be used for short periods of time.
|Debug logging||Produces low-level diagnostics used internally
by IBM® to identify what was
happening on the system before an error condition occurred. This option
generates a large amount of output per activity and should only be
used for short periods of time.
Attention: Debug logging can potentially include personal member information such as member identification number, name, and so forth.
|Timer logging||Produces timings on certain operations to help
identify where significant processing time is elapsing.
|SQL logging||Outputs the SQL that is sent by the InfoSphere MDM database
layer to the RDBMS. This helps in diagnosing database-related issues.
This option can produce large amounts of output depending on the activity.
|Audit logging||Produces activity information and non-critical
warnings. Often, this option is used when a new system is first implemented
to monitor activity.
|Algorithm logging||A separate logging level for algorithm-related
debug information without the risk of including protected health information