How to recognize a schedule entry breakdown in MII 12.1

[martin_schindler2]

Hi,

at one of our customers an interesting question showed up regarding the maintenance of a running productive MII System.

This week is happend that there was a crash of a running schedule entry. The job was was obviously crashed but shown in scheduler as running.

The only hint to recognize the problem was, to find out that the actual functionality of the scheduled transaction was not woking any more and the only indicator from the scheduler, was that there was not history for this job.

the problem was solved with a restart of the job.

But the big question is: how can a normal customer who is running a productive MII system easyly recognize a crashed schedule entry unsing the MII internal tools???

By the way this behaviour we have seen on different versions of MII 12.0 and 12.1, normally our way to regognize such problem is to check if the job is running much longer than normal an checking if there is no history for the job. But this is a procedure which is not really usable for a customer.

Thanks in advance,

Martin

[Former Member · Accepted solution]

Hi Martin,

we have faced/are still facing the same problem (at least with MII internal tools). 

What I have done as a workaround (at least for the moment) is to use the scheduler service url's you can find here: https://help.sap.com/saphelp_mii122sp02/helpdata/en/4a/e77da4914834c9e10000000a421138/content.htm

So I have written my own java code that calls some of these URL's and depending on certain configurations raises an alert via E-Mail (e.g. when a job is running to long, when a job goes in failed state, when the system is not reachable at all).

It is maybe not the best way to do this but because of missing MII features I have seen no other way to do this (at least for the moment).

This self-made tool saved me a lot of time and helped me identifying a lot of problems (sometimes not even caused by mii itself 😉

Hope this helps and best wishes from Austria,

Roland

PS: If you have a proper monitoring tool in place you should be able to use this URL's more easily.