DAC Preview Functionality to View Tasks and Dependencies

Question

Hello, I'm looking for a way to display or list out all of the DAC tasks for a particular execution plan and for each one of these then display each of their dependencies. I know that when you build a execution plan DAC is generating a dependency list and assigning depth levels behind the scenes, but it would be nice to display this in a graphical format or at least as a text list.
In my research I found the link below to seem to be what I'm looking for and also does a great job of explaining the Task Dependencies. However, the version of DAC I'm running (10.1.3.4.1) does not seem to have this feature, and if so, I'm unable to find it. Any and all help is greatly appreciated. Maybe there is a approach I'm unaware exists.
http://download.oracle.com/docs/cd/E12102_01/books/AnyInstAdm784/AnyInstAdmQuickStart17.html
Thanks

Answer 1

You might check with your apps' developers to see if they support AppleScript, Automator, or other scripting languages that might be used for this. Some programs have built-in macro and scripting options that can be set up in a built-in editor or run in a built-in command-line environment of sorts, while others supply libraries for external scripting with AppleScript and others.
As for live tracing of a program's commands, most that you use will be coded in a low level language like C, C++, Java, or Objective-C, which are compiled and run in binary machine code as opposed to an interpreted language (one that does not need compiling to run), as is the case with most scripting languages (shell scripts, AppleScript, Matlab, etc.).
For the most part, the only options you have for "tracing" a program's functions are to monitor output that it might log to the console. You can see this by opening the console, but the output here is diagnostic in nature and is programmatically limited to what the programmers have intended be output (ie, things like warnings and errors, as opposed to every action the program is taking). You can also use the Terminal to directly launch a program's executable so it is hosted in the Terminal shell. This will give you direct access to all of the program's output, as opposed to that only intended for logging in the Console, but it is still not the same as a full output of the commands and routines the program is performing.
Some of Apple's developer tools can allow you to better monitor a program's functions, but these are intended for developers, and have some requirements, and will not allow you to use any results for productivity automation.