ESP Workload Automation

CA-iDash question for CA-7 v12 in z/OS Mainframe:

I need to understand why this is considered a predicted miss in CA-iDash.

--Deadline: 22:00  -->  Predicted miss occurrence: 17:00:46 ? ? ? 

*****JOB COMPLETED at 18:12

--Start Tracking: 300 mins

--End Tracking:  720 mins

--At risk warning: 60 mins

--Run validity:     300 mins

--Past Hrs:            12 hrs

NOTE: I did noticed a dependency (not triggered from the same job), This dependency is not scheduled to come in until 18:00 - Since it did not know of the dependeny's schedule, it predicteed missed from the start? If so, should iDash have known this?

I changed the start tracking at 240 mins. (I hour later to cover the start time of a dependency at 18:00)

Any suggestions or comments?

We would require to understand the dependency and the job flow in order to answer your question. We recommend you to open a support ticket so that we can gather the required information.

Thanks,

Chirag