cncjay
Well Known Member
All,
We are using E1 9.0 TR 8.98.4.10. MSSQL 2008R2 backend.
Occasionally, one of our scheduled job fails. When we delete the runtime specs for it, then relaunch it, its fine. Its a long running job which is why we schedule it in the early part of the day, so, its a big deal for the users having to launch it again after arriving to the office.
Is there any way to suppress the creation of runtime specs for a selective UBE ?
or, is there way to turn it off, altogether ?
I suppose the right question should be, why does the runtime specs corrupt ?
Thank you
CNCJay
We are using E1 9.0 TR 8.98.4.10. MSSQL 2008R2 backend.
Occasionally, one of our scheduled job fails. When we delete the runtime specs for it, then relaunch it, its fine. Its a long running job which is why we schedule it in the early part of the day, so, its a big deal for the users having to launch it again after arriving to the office.
Is there any way to suppress the creation of runtime specs for a selective UBE ?
or, is there way to turn it off, altogether ?
I suppose the right question should be, why does the runtime specs corrupt ?
Thank you
CNCJay