I rewrote my RunAndWait example. It now can capture console output. It runs the program redirecting the output to a Pipe. Then when the program finishes, it reads the pipe and displays it in a MLE.

https://www.topwizprogramming.com/freecode_runandwait.html

Hi, Rick - 

Have you looked at this example in CodeXchange?

https://community.appeon.com/index.php/codeexchange/powerbuilder/57-redirect-console-output#54

I tried it with the Tasklist command (only on my local machine) and it appears to capture the output and the filter option appears to work. The example app redirects stdout to a multiline edit control, but I'm pretty sure this could be easily changed to a DataWindow or DataStore. Worth a look.

Regards, John

There is a way for a PB app to write to the console if run as a 'batch' program. I have used it myself.

https://www.rgagnon.com/pbdetails/powerbuilder-print-to-the-console.html

Here is an example in VB6 of running an external program and capturing its STDOUT using pipes. I haven't tried this. Maybe sometime I can add this to my RunAndWait example.

http://www.vb-helper.com/howto_capture_console_stdout.html

I would change the app to set the AppName and Host database parms.

You can set Host to the computer's name and AppName to a short version of the application name along with a version number.

Then you can use sp_who or a custom query to see who is connected, what machine they are on, and what version of the app they are running.

Have you considered using the database server to see who's still connected? ASA and ASE let you query the database server to see who is connected, and can even retrieve the connection name (which you can set when the app connects to the server). This way you can track if your app has any open connections that need to be closed.

Hi Rick,

You could send the output to a temporary file using something like the following:

String ls_command

ls_command = 'cmd /c tasklist /v /fi "STATUS eq running" > c:\users\rick\desktop\allrunning.txt'
Run(ls_command, Minimized!)

Then process the 'allrunning.txt' file whatever way you want...display in MLE control, import into DW control etc. (or in your case search for the existence of "running" or "not found").

HTH...regards,
Mark