Ist there a way to catch the "output" that is piped out of the prowin32.exe (in batchmode( in the ABL Session?
At the moment i pipe the output to a textfile with an external exe but i would like to catch the messages in the ABL Session.
Sadly that is not what i want.
I want to "catch" the messages that are written by the prowin32.exe in batchmode through stdout (i guess) in the abl session.
Like a "global" catch for all messages.
Error Messages for example.
Afaik OE Pipes all Messages to the stdout (when batch mode is activated).
Long story short: I wand to get everything that the prowin32.exe pipes out when batch mode is activated.
You mean you want to redirect your own default output stream to your own default input stream?
If you are in an interactive session and you want to start a batch job and get its output, you can do this:
INPUT THROUGH prowin32 -b -p mybatch.p.
IMPORT UNFORMATTED cLine.
Thank you for you answer Simon,
The reason behind it is that i want to store the (error) messages in my OE database for our custom monitoring system.
The answer you provided would work but i would really like to avoid doubling the number of running prowin32.exe processes on the server.
I mean the Progress Messages, i don't display any messages myself when in batchmode.
I know that i could write the Messages to a file (and currently that is what i do).
I was just wondering if there is a possibility to do this without a logfile.
I guess i have to keep my logfile :(