Aggregation

Aggregate Input-Events

This function can ONLY be implemented for file-based implementations of Rule Engine.

Reminder about setting parameters in AI Enabler

Input-Events are aggregated by applying the preprocessing steps that are associated with a specific Input-Event type.
To this end:

You must export the preprocessing and aggregation rules to Rule Engine.

Parameter settings in script.ges and sys.dat

Keyword Description/Values
>ScriptConfiguration< Section
I_Aggregation_IEvent Yes
I_Exit_Aggregation_IEvent

Yes, if you want to use exits for processing during aggregation of the Input-Event segments (See Manage exits and external calls)

Otherwise, No

Aggregation_Part_IEvent

Yes, to get the output from a partial aggregation without truncating the number of segments aggregated
This approach is recommended for large volumes or large numbers of aggregations

Otherwise, No

Print_Report_Aggregation_IEvent

Yes if you want counter details on the Input-Event aggregation

Otherwise, No

Counter_Aggregation_IEvent

The name of the file containing the data for the report on the aggregation counters

Report_Detail_Agreg_IEvent

Yes if you want details on the Input-Event aggregation

Otherwise, No

Detail_Agreg_IEvent

The name of the file containing the data to be used in the Input-Event Aggregation Detail report

IEvent_I (required parameter if the session consists solely of an input (T) step)

Name of the output file from an input (E) step or the input file to a subsequent processing (T) step

Aggregate Output-Events

This function can ONLY be implemented for file implementations of Rule Engine.

Reminder about setting parameters in AI Enabler

Output-Events are aggregated by applying the Mapping Rules and the options associated with the output.

To this end:

  1. You must export to Rule Engine the Transformation-Rules associated with the Input-Event types, the outputs associated with the Output-Events and the definitions of the aggregation rules.
  2. Moreover, to identify the aggregation rule by the contents of the Output-Event, you must declare the aggregation rule technical field among the Output-Event structures.

Parameter settings in script.ges and sys.dat

Keyword Description/Values
>ScriptConfiguration< Section
P_Aggregation_Osegt_Group

Yes, if you want to aggregate all Output-Event groups combined in the T step

P_Exit_Aggregation_OSegt_Group

Yes, if you want to use exits for processing during aggregation of the Output-Events in step T

O_Aggregation_OSegt

Yes, if you want to aggregate the Output-Events in step S

O_Exit_Aggregation_OSegt

Yes, if you want to use exits for processing during the aggregation of the Output-Events in step S (See Manage exits and external calls)

Aggregation_Part_OSegt

Yes, to get the output from a partial aggregation without truncating the number of segments aggregated
This approach is recommended for large volumes or large numbers of aggregations

Otherwise, No

Turnoff_Exit_OSegt
  • No: if the previous keyword is set to Yes
  • Yes: if you are not using an exit to enrich the Output-Events
Print_Report_Aggregation_OSegt<0}
  • Yes: to obtain Output-Event aggregation counters
  • No: if you are not aggregating the Output-Events
Counter_Aggregation_OSegt

The file containing the data for the report on the aggregation of the Output-Events

Counter_Aggregation_IEvent

File containing Output-Event aggregation report data

Print_Report_Aggreg_Accounting
  • Yes: to obtain accounting Output-Event aggregation details
  • No: if you are not aggregating the Output-Events
Aggreg_Account

File containing data for the accounting Output-Event  aggregation details report

O_Exit_Aggregation_OSegt

Yes, if you want to use exits for processing during the aggregation of the Output-Events in step S
(See Manage exits and external calls)

You must also supply the parameter settings specific to the sort that the procedure runs automatically

Related Links