It's bee a few months since I worked on triggered app in a Windows
environment. However, one possibility to check is which user account is
being used by runmqtrm (or whatever the process is) that is starting your
application. I think you will find that it is NOT the currently logged on
user. Therefore you would not be seeing any application output.

My personal opinion is that triggered apps are intended to be automated
processes that run in the background. Having a triggered app be some type of
GUI app vs. a console app is probably not a great idea. I think that is also
a reaason you won't get too much response on what you are doing. It doesn't
really make sense. IMHO.

"Grzegorz Wiktorowski" wrote in message
news:fjch12$1ao46$1@news.boulder.ibm.com...
>I just start to play with WebSphere 6 under Windows. I've configured local
> queue, initiation queue and RUNMQTRM as a service. I notice the problem
> with defining the triggered process. I wrote the most simple Delphi
> application with one form. When the application runs it shows the window
> with a text. When I close the window it stops.
>
> First webSphere MQ embarrassed me when it does not accept spaces in
> ApplID.
> For example:
>
> C:\Test MQ\TR.exe
>
> (I put a space between Test and MQ) is wrong.
>
> After I corrected this, I expect my application will be fired. So I put a
> message into the local queue but I don't see that the fired application
> shows the information window. When I checked running processes with
> Sysinternals' Proccess Explorer, I notice that RUNMQTRM starts CMD command
> interpreter with C:\TestMQ\TR.exe as a parameter. CMD starts TR.exe but I
> don't see anything on my desktop. I just wonder what I miss here.
>
> --
> Grzegorz Wiktorowski
>