Properties reference: The Operational Decision Manager (ODM) stage in DataStage

Usage

Engine mode

Select the mode in which to access the ODM engine:

• Type: selection
• Default: Core engine
• Values:
  • Core engine

For more information, see Operational Decision Manager (ODM) engine mode in DataStage.

Ruleset location

Enter the path to the ruleset

• Type: string
• Minimum length: 1

Enable batch processing

Select Yes to use the batch size value for correlating records across the input links

• Type: Boolean
• Default: false

For more information, see Operational Decision Manager (ODM) stage batch mode and key mode processing in DataStage.

Batch size

Enter the batch size. Enter 0 to put all available records on the link in a single batch.

• Type: integer
• Default: 1
• Minimum: 0
• Maximum: 999999999

Enable key processing

Select Yes to utilize key columns for correlating records across the input links

• Type: Boolean
• Default: false

Key column

Select column to include in the key definition

• Type: category

Column name

Select the column name to be added to the key definition

• Type: string

Sort direction

Select the direction in which the records are sorted based on this key column

• Type: selection
• Default: Ascending
• Values:
  • Ascending
  • Descending

XOM type

Select the execution object model (XOM) type of the ruleset parameters

• Type: selection
• Default: Java XOM
• Values:
  • Java XOM
  • Dynamic XOM

For more information, see Operational Decision Manager (ODM) stage Execution Object Model types in DataStage.

Propagate unmatched fields

Select Yes to propagate unmatched fields from input links to output links. An unmatched field is a field present on the input link and not utilized by the connector to prepare values of the ruleset parameter for that link.

• Type: Boolean
• Default: false

Field propagation strategy

Select the strategy to use when propagating unmatched fields from input links to output links

• Type: selection
• Default: Match by using order of records
• Values:
  • Match by using order of records
  • Match by using key values present in records
  • Match by using input and output Java object identifiers

For more information, see Operational Decision Manager (ODM) stage field propagation strategies in DataStage.

Java properties

Specify custom JVM options to use for the stage

• Type: category

Classpath

Enter the classpath value

• Type: string

For more information, see Operational Decision Manager (ODM) stage Java class path configuration in DataStage.

Heap size

Enter the heap size (in megabytes)

• Type: integer
• Default: 256
• Minimum: 128

JVM options

Enter the additional JVM options

• Type: string

Ruleset parameter name

Enter the ruleset parameter name associated with this link

• Type: string
• Minimum length: 1

Ruleset parameter class

Enter the fully qualified Java class name for the ruleset parameter associated with this link. This value is applicable only to ruleset parameters based on Java XOM.

• Type: string
• Minimum length: 1

Buffer link

Select Yes to use this link as the buffer link. Records that arrive on the buffer links are cached and reused across all ruleset executions.

• Type: Boolean
• Default: false

For more information, see Operational Decision Manager (ODM) stage buffer links (DataStage).

Propagation key column

Specify the propagation key column to be used for mapping input records to output records when propagating unmatched fields based on the key values present in the records

• Type: string

For more information, see Operational Decision Manager (ODM) stage field propagation strategies in DataStage.