Hello @ErikLund_Jensen ,
thank you so much for this very detailed and precise, yet profound descritpion of the "mechanics" behind deploying a Job (via DI).
So, to summarize, it can be said, that:
A JfJob-Object always has one and only one corresponding Job-Object (which in turn corresponds to exactly one source file)
Viewed from "the other way around", it is possible, that a particular Job-Object corresponds to either none, one or many JF-Job-Objects, depending on whether the Job isn't deployed at all, or is just deployed once with a particular name, or is deploy multiple times with corresponding different JfJob-Object Names (and definitely different metadata IDs!), respectively.
You mentioned that:
We have automated these checks along with many others, so we receive a daily rapport over obsolete files, more than one JFJob for each Job, Jobs changed after latest deployment etc.
Are these checks done by means of SAS utilities, like self-written macros, STPs, etc.? If possible, I'd be interested in getting the underlying code 🙂
Cheers,
FK1
... View more
