This section describes tasks that you perform for MPC engines.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
The MPC Preprocessor engine can be scheduled using the Data Steward Maintain Events to run at any predefined interval. The preprocessor launches the MPC Calculation engines, so it is not necessary to schedule the individual calculation engines, the preprocessor takes care of that. See the following figure in Maintain Events for the MPC event definition.
...
...
...
...
...
...
The following figure shows the MPC Engine Names in Event Queue. You see the MPC Preprocessor engine as well as each individual MPC Calculation engine.
...
...
...
...
...
...
|
In the DataSteward, MPC Calculation engines appear in a grouping under the MPC Preprocessor engine in the Event Queue. See the following figure.
...
...
A plus sign 
appears next to the MPC Preprocessor engine entry.
...
...
...
| Anchor | ||||
|---|---|---|---|---|
|
To include new fields, PACE reports automatically refresh the field cache on the PACE engine at the start of each execution. The MPC does this same refresh at the beginning of the preprocessor and as each calculation engine is spawned. This avoids the problem wherein an MPC field requires a newly created performance Field Attribute that was not updated in the PACE engine field cache.
On this page
| Table of Contents |
|---|