#Dscp batch execution report - Daily

We will receive alert emails while batch execution has run with errors / long / late / do not run.

We need to check the logs to see what is the issue and if needed to relaunch the batchs.

Description

Frequency

Environment

How to Do

Screenshot

To monitor on 

Dscp batch execution

Daily / Every morning(China Time)


Dscp DPx / Dipx / DSCPx

1.1 Email received.(Alert email trigger point)

  • if the batch execution has run with errors
  • if the batch execution has run too long
  • if the batch execution has run too late
  • if the batch execution did not run

1.2 To check on the email # Dscp DPx / Dipx / DSCPx batch execution report of Dscp_Daily_Static / Dscp_Export_DR / Dscp_DP_Weekly / Dscp_DiP_Weekly 

to verify the batch execution report.

1.3 To analyze on the error jobs, if a jobs has run with errors. Check the attached logs to find which part is KO. Refer to the related logs to locate more error details.

1.4 Re-execute the Macros if needed.

1.5 Notify the functional team.



For example:

inside the Alert email，

you will see the Errors with red cross，and also logs attached in the end of the email.

To monitor on 

Dscp batch execution

Daily / Every afternoon(China Time)Dscp DPx / Dipx / DSCPx

2.1 Email received.(Alert email trigger point)

  • if the batch execution has run with errors
  • if the batch execution has run too long
  • if the batch execution has run too late
  • if the batch execution did not run

2.2 To check on the email # Dscp DPx / Dipx / DSCPx batch execution report of Dscp_Daily_Dynamic 

to verify the batch execution report.

2.3 To analyze on the error jobs, if a jobs has run with errors. Check the attached logs to find which part is KO. Refer to the related logs to locate more error details.

2.4 Re-execute the Macros if needed.

2.5 Notify the functional team.