Page Comparison

This section describes tasks that you perform for MPC engines.

Anchor
_Toc521324314 _Toc521324314

Anchor
RTF320031003300300030003a00 RTF320031003300300030003a00

Schedule the MPC Preprocessor Engine

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.

AnchorRTF320031003300300030003a00RTF320031003300300030003a00

Anchor
_

Toc521324315 _

Toc521324315

Anchor

RTF310037003400360031003a00 RTF310037003400360031003a00

Monitor the Engine Status

The status of MPC events can be monitored through the DataSteward Event Queue. See the 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.

AnchorRTF310037003400360031003a00RTF310037003400360031003a00

Anchor
_

Toc521324316 _

Toc521324316

Anchor

RTF340033003400310032003a00 RTF340033003400310032003a00

MPC Engine Grouping in DataSteward Event Queue

In the DataSteward, MPC Calculation engines appear in a grouping under the MPC Preprocessor engine in the Event Queue. See the following figure.

AnchorRTF340033003400310032003a00RTF340033003400310032003a00 Anchor_Toc337537785_Toc337537785 Anchor_Toc361231382_Toc361231382MPC Preprocessor in the Event Queue
A plus sign appears next to the MPC Preprocessor engine entry. See the The following figure shows the MPC Preprocessor and MPC Calculation Engine in Event Queue. Doubleclicking the + displays all the MPC Calculation engines that were spawned by that preprocessor.

Image Removed

Image Added

Anchor
_Toc521324317 _Toc521324317

Refresh the Field Cache in MPC Engines

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.