Hi Nishanth,
I think that Publisher (a complementary sofware to Dollar Universe, which extract and displays DU objects definition) gives that information, but that's to check.
Otherwise you may use several other solutions:
- Production documentation with job definition, in which you may use "find" tool to look for dependancy. That documentation was a basis some time ago but I feel like it tends to disappear...
- In-house scripted solution to dynamically check all dependencies. Beware that the impacts of an aborted job are more complex than just dependencies:
* Inner session childs
* Inner and/or outer session dependencies
* Resources not released
* Completion instructions not run
* Scripted instructions not run (uxordre, uxadd, ...)
Childs, dependencies and completion instructions are the most easier to check as a query to DU uprocs and sessions gives the result. For example on Linux:
Create 2 awk files as follow:
[code]
# searchUproc.awk -- Identify which session(s) use(s) a given uproc
# The parameter "upr" is used for filtering
/^ ITEMS \| ses/ { ses = $NF }
/^ | upr :/ { if ( $4 == upr ) print "ses/" ses "#" upr }
[/code]
[code]
# searchDepcon.awk -- Identify which uproc(s) depends of a given uproc
# The parameter "depcon" is used for filtering
/^ ITEMS \| upr/ { upr = $NF }
/^ dep :/ { if ( $3 == depcon ) print "upr/" upr "#" depcon; }
[/code]
And call them as below, replacing <uproc_name> by the name of the aborted uproc.
[code]
$UXEXE/uxshw upr upr=* | awk -f searchDepcon.awk depcon=<uproc_name> | sort -u;
$UXEXE/uxshw upr upr=* | awk -f searchUproc.awk upr=<uproc_name> | sort -u;
[/code]
As stated above, this information is not complete to get all possible impacts of an aborted job; you have to consider the peculiarities of your production, and take some time to develop your own solution.
Kindly,
Stéphane.