TSR for PACE Jobs

The task status responses (TSR) for PACE jobs have a specific structure which is slightly different different from common EJM TSRs.

There are more details available for such PACE events as DataMart and RDC Composites.

It includes Pace job execution status and error details - and event details for job substeps as well:

<eventDetails>
    <eventName>Data Strategy: [3][EGLRDC_25][Vanilla Option]. Gold Copy: [2][DEFAULT][Default]. Effective Date: [22-Apr-2016]</eventName>
    <eagleInstanceId>2804764</eagleInstanceId>
    <reason>
        <reasonTypeEnum>ERROR</reasonTypeEnum>
        <reasonCode>1</reasonCode>
        <description>The execution of the event Data Strategy: [3][EGLRDC_25][Vanilla Option]. Gold Copy: [2][DEFAULT][Default]. Effective Date: [22-Apr-2016](SD Instance - 2804764) failed. ERROR: Code:[102][EXCEPTION - RW Exception]. Message: [ERROR: Database operation failed with error: [[SERVERERROR] ORA-01400: cannot insert NULL into ("EAGLE_TEMP"."EGLU_2531394_SCRUBDBO_SECMAST"."PROCESS_SEC_TYPE")]]</description>
    </reason>
</eventDetails>

These additional details are available as of the January 2016 EagleML Release.

<EagleML
  eaglemlVersion="2-0"
  eaglemlType="TaskStatusResponse"
  xsi:schemaLocation="http://www.eagleinvsys.com/2011/EagleML-2-0 eagleml-main-2-0.xsd"
  xsi:type="TaskStatusResponse"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns="http://www.eagleinvsys.com/2011/EagleML-2-0">
<header>
    <messageId>B60EMK55QESDPYVC</messageId>
    <sentBy>http://www.eagleinvsys.com/</sentBy>
    <sendTo>www.client.com</sendTo>
    <creationTimestamp>2016-04-22T21:05:52-05:00</creationTimestamp>
</header>
<statusItem>
    <taskIdentifier>
        <correlationId correlationIdScheme="correlationIdScheme">TST_PJ_DK_03_2_4</correlationId>
        <businessTaskId correlationIdScheme="businessTaskIdScheme">TST_PJ_DK_03_2_4#RUN_JOB</businessTaskId>
    </taskIdentifier>
    <status>FAILED</status>
    <severityCode>1</severityCode>
    <reason>
        <reasonTypeEnum>ERROR</reasonTypeEnum>
        <reasonCode>1</reasonCode>
        <description>The execution of the event Run All Data Strategies For All Securities/PROCESS_ENGINE failed. One or more events failed</description>
    </reason>
    <taskUnit>
        <status>FAILED</status>
        <severityCode>1</severityCode>
        <eventDetails>
            <eventName>Run All Data Strategies For All Securities</eventName>
            <eagleInstanceId>2804762</eagleInstanceId>
            <reason>
                <reasonTypeEnum>ERROR</reasonTypeEnum>
                <reasonCode>1</reasonCode>
                <description>The execution of the event Run All Data Strategies For All Securities/PROCESS_ENGINE failed. One or more events failed</description>
            </reason>
        </eventDetails>
    </taskUnit>
    <taskUnit>
        <status>FAILED</status>
        <severityCode>1</severityCode>
        <eventDetails>
            <eventName>Run All Data Strategies For All Securities</eventName>
            <eagleInstanceId>2804763</eagleInstanceId>
            <reason>
                <reasonTypeEnum>ERROR</reasonTypeEnum>
                <reasonCode>1</reasonCode>
                <description>The execution of the event Run All Data Strategies For All Securities(SD Instance - 2804763) failed. </description>
            </reason>
        </eventDetails>
    </taskUnit>
    <taskUnit>
        <status>FAILED</status>
        <severityCode>1</severityCode>
        <eventDetails>
            <eventName>Data Strategy: [3][EGLRDC_25][Vanilla Option]. Gold Copy: [2][DEFAULT][Default]. Effective Date: [22-Apr-2016]</eventName>
            <eagleInstanceId>2804764</eagleInstanceId>
            <reason>
                <reasonTypeEnum>ERROR</reasonTypeEnum>
                <reasonCode>1</reasonCode>
                <description>The execution of the event Data Strategy: [3][EGLRDC_25][Vanilla Option]. Gold Copy: [2][DEFAULT][Default]. Effective Date: [22-Apr-2016](SD Instance - 2804764) failed. ERROR: Code:[102][EXCEPTION - RW Exception]. Message: [ERROR: Database operation failed with error: [[SERVERERROR] ORA-01400: cannot insert NULL into ("EAGLE_TEMP"."EGLU_2531394_SCRUBDBO_SECMAST"."PROCESS_SEC_TYPE")]]</description>
            </reason>
        </eventDetails>
    </taskUnit>
</statusItem>
</EagleML>

This option is available since the May 2016 EagleML Release.

By default the details for successful substeps are switched off. They can be switched on by setting W_CONFIG_SKIP_SUCCESS_STEPS global parameter with the value 'N' in w_config_custom.inc configuration file.

TSR for DataMart PACE Jobs

For DataMart Pace jobs there are two additional options available for TSR messages:

You can make the process treat NO_DATA status of a substep(s) as a warning and therefore not report it with FAILED status. By default this option is switched off. To switch this feature on, set ‘TreatNoDataAsWarning’ task parameter as ‘Y’ in the RTR message. Like this:
<taskParameter> <name>TreatNoDataAsWarning</name> <dataType>S</dataType> <value>Y</value> </taskParameter>
Note: This option is available since the March 2016 EagleML Release.

Toggle reporting Event Entity Details for DataMart Model Manager steps:
Summary details (number of failed entities, total number of processed entities)
Entity Details (the set of failed entity ids)

This option is available since the May 2016 EagleML Release.

By default Event Entity Details are switched off. To enable these details in the Final TSR, the task parameter ReportEventEntitiesDetails = Y should be populated in the RTR message or the set as global parameter W_CONFIG_INCLUDE_ENTITIES_DETAILS = Y in w_config_custom.inc.

Example of task parameter in the RTR:

The example of DataMart Model Manager step with Event Entity Details:

Security-Level Details in the TSR for RDC Composites

By default RDC event security details are switched off. To enable adding security details to the Final TSR the task parameter ReportEventSecurityDetails = Y should be populated in the

RTR message:

or W_CONFIG_INCLUDE_SECURITY_DETAILS = Y set in the configuration file w_config_custom.inc.