Hi Dipesh,
Did you decide not to run the batch file with the Utility - Environment VBO action 'Start Process'? Depending on what the batch file is doing (like if it waits for user input or has a pause), the window would open and then Blue Prism could attach to it. Anyway, it sounds like you figured out a solution to the launching issue. I just wanted to mention it as a possibility. It does seem odd to me that you had to use AA Mode and that Win32 did not work.
As far as reading text from the cmd window, do you have the option to edit the batch file so that it could print output to a file for you? Otherwise, there's pretty much Surface Automation or copying the text from inside the window to the clipboard. You could click into the cmd window (or give it focus some other way) and use CTRL+A/CTRL+C to copy all the text to the clipboard, and then get the clipboard text into a Blue Prism text data item and manipulate as necessary. This seems like it could work solidly if the text output from the cmd window is structured in a predictable way.
Edit: I just went back up and read your initial post again. You mentioned you need to pass input arguments to the batch file so that makes sense why you'd need to call the batch file from command line. Also, you may want to take a look at the code in the AutomateC object because it is able to perform CLI commands as well as read the output from them. I imagine you'd prefer this kind of solution over any SA or copy/pasting.
------------------------------
Dave Morris
3Ci @ Southern Company
Atlanta, GA
------------------------------
Dave Morris, 3Ci at Southern Company