I’m trying to make sense of a huge repository at a client where every table extract is a single job. In essence, I want to document which jobs are using which data stores.
I made a copy of the repository database and I had the idea to flatten the AL_PARENT_CHILD table so I could at least see which objects and datastores are used in which jobs. Unfortunately, even the standard JDE date job seems to through a cyclic loop so I had to turn on the do-not-abort-on-cycle option.
Long story short - 24 hours of running later, DS is still busy and I have no idea of progress, it very much seems to be stuck in a loop. So scratch that idea.
Don’t get me wrong, I can easily get the data store information out through a simple query - I just need to tie this back to the jobs in which they are used? Also writing a SQL CTE recursive query immediately hits max recursion limits unless I disable this and then I’m in the same boat again.
Other than going through each of several hundred jobs and selecting export and writing down the data stores, is there a better way to get this information out?
ErikR 
(BOB member since 2007-01-10)
(BOB member since 2007-09-12)