MQ

How is your trigger monitor running? Foreground/background.

How are you triggering the application? Foreground/background? Perhaps you can show us the queue and process object definitions involved. 

This page in IBM Docs might be useful.

Cheers,
Morag

How is your trigger monitor running? Foreground/background.

How are you triggering the application? Foreground/background? Perhaps you can show us the queue and process object definitions involved. 

This page in IBM Docs might be useful.

Cheers,
Morag

So, if memory serves, running the trigger monitor as a service means that it is definitely running in the background, and also the trigger started applications are also started in the background, rather than running inline in the trigger monitor.

It is also hard to know which runmqtrm you are using (bin or bin64) from your screenshot. Please read this post which might explain why you are not seeing anything traced.

Anyway, I'm not sure where your stdin is supposed to come from if everything is running in the background? Is there something about this plink.exe that will create a stdin or are you relying upon the environment running your application to have a stdin?

You say that using your example command from a Windows Command window works, but of course then you are running in the foreground and have a stdin. What happens if you invoke it (outside of the triggering stuff) as a background command?

To test out foreground/background theory, you could also try running the trigger monitor in a command window, and then your application will run inline in that command window, and then you might have a stdin?

Just some ideas anyway,
Cheers,
Morag

How is your trigger monitor running? Foreground/background.

How are you triggering the application? Foreground/background? Perhaps you can show us the queue and process object definitions involved. 

This page in IBM Docs might be useful.

Cheers,
Morag

So, if memory serves, running the trigger monitor as a service means that it is definitely running in the background, and also the trigger started applications are also started in the background, rather than running inline in the trigger monitor.

It is also hard to know which runmqtrm you are using (bin or bin64) from your screenshot. Please read this post which might explain why you are not seeing anything traced.

Anyway, I'm not sure where your stdin is supposed to come from if everything is running in the background? Is there something about this plink.exe that will create a stdin or are you relying upon the environment running your application to have a stdin?

You say that using your example command from a Windows Command window works, but of course then you are running in the foreground and have a stdin. What happens if you invoke it (outside of the triggering stuff) as a background command?

To test out foreground/background theory, you could also try running the trigger monitor in a command window, and then your application will run inline in that command window, and then you might have a stdin?

Just some ideas anyway,
Cheers,
Morag

How is your trigger monitor running? Foreground/background.

How are you triggering the application? Foreground/background? Perhaps you can show us the queue and process object definitions involved. 

This page in IBM Docs might be useful.

Cheers,
Morag

Glad to hear you are sorted - I guess not assuming you have a stdin is the takeaway here.

Your screenshot of the row in task manager sheds no light on whether you are using the bin or bin64 version. Did you have the "Image path name" column visible?

So if you have managed to locate the trace by tracing everything and then looking for the PID to locate the trace, what did the header at the top of the trace file suggest the name of the program was?

I never use the -p option on strmqtrc so I have no idea how reliable it is. Is that something you usually use and have success with? 

So, if memory serves, running the trigger monitor as a service means that it is definitely running in the background, and also the trigger started applications are also started in the background, rather than running inline in the trigger monitor.

It is also hard to know which runmqtrm you are using (bin or bin64) from your screenshot. Please read this post which might explain why you are not seeing anything traced.

Anyway, I'm not sure where your stdin is supposed to come from if everything is running in the background? Is there something about this plink.exe that will create a stdin or are you relying upon the environment running your application to have a stdin?

You say that using your example command from a Windows Command window works, but of course then you are running in the foreground and have a stdin. What happens if you invoke it (outside of the triggering stuff) as a background command?

To test out foreground/background theory, you could also try running the trigger monitor in a command window, and then your application will run inline in that command window, and then you might have a stdin?

Just some ideas anyway,
Cheers,
Morag

How is your trigger monitor running? Foreground/background.

How are you triggering the application? Foreground/background? Perhaps you can show us the queue and process object definitions involved. 

This page in IBM Docs might be useful.

Cheers,
Morag

Glad to hear you are sorted - I guess not assuming you have a stdin is the takeaway here.

Your screenshot of the row in task manager sheds no light on whether you are using the bin or bin64 version. Did you have the "Image path name" column visible?

So if you have managed to locate the trace by tracing everything and then looking for the PID to locate the trace, what did the header at the top of the trace file suggest the name of the program was?

I never use the -p option on strmqtrc so I have no idea how reliable it is. Is that something you usually use and have success with? 

So, if memory serves, running the trigger monitor as a service means that it is definitely running in the background, and also the trigger started applications are also started in the background, rather than running inline in the trigger monitor.

It is also hard to know which runmqtrm you are using (bin or bin64) from your screenshot. Please read this post which might explain why you are not seeing anything traced.

Anyway, I'm not sure where your stdin is supposed to come from if everything is running in the background? Is there something about this plink.exe that will create a stdin or are you relying upon the environment running your application to have a stdin?

You say that using your example command from a Windows Command window works, but of course then you are running in the foreground and have a stdin. What happens if you invoke it (outside of the triggering stuff) as a background command?

To test out foreground/background theory, you could also try running the trigger monitor in a command window, and then your application will run inline in that command window, and then you might have a stdin?

Just some ideas anyway,
Cheers,
Morag

How is your trigger monitor running? Foreground/background.

How are you triggering the application? Foreground/background? Perhaps you can show us the queue and process object definitions involved. 

This page in IBM Docs might be useful.

Cheers,
Morag

You said earlier that, "when starting a trace with runmqtrm -t all -p runmqtrm I get nothing traced at all"

I never use this -p option, so I just looked in the Docs about it.

-p Apps

The named processes to which the trace generation is restricted. Apps is a comma-separated list. You must specify each name in the list exactly as the program name would be displayed in the "Program Name" FDC header. Asterisk (*) or question mark (?) wildcards are allowed. You cannot use the -p parameter with the -e parameter.

This makes me think you would need to have put -p runmqtrm.exe in the command? If you do that, do you get trace out?

Cheers,
Morag

Glad to hear you are sorted - I guess not assuming you have a stdin is the takeaway here.

Your screenshot of the row in task manager sheds no light on whether you are using the bin or bin64 version. Did you have the "Image path name" column visible?

So if you have managed to locate the trace by tracing everything and then looking for the PID to locate the trace, what did the header at the top of the trace file suggest the name of the program was?

I never use the -p option on strmqtrc so I have no idea how reliable it is. Is that something you usually use and have success with? 

So, if memory serves, running the trigger monitor as a service means that it is definitely running in the background, and also the trigger started applications are also started in the background, rather than running inline in the trigger monitor.

It is also hard to know which runmqtrm you are using (bin or bin64) from your screenshot. Please read this post which might explain why you are not seeing anything traced.

Anyway, I'm not sure where your stdin is supposed to come from if everything is running in the background? Is there something about this plink.exe that will create a stdin or are you relying upon the environment running your application to have a stdin?

You say that using your example command from a Windows Command window works, but of course then you are running in the foreground and have a stdin. What happens if you invoke it (outside of the triggering stuff) as a background command?

To test out foreground/background theory, you could also try running the trigger monitor in a command window, and then your application will run inline in that command window, and then you might have a stdin?

Just some ideas anyway,
Cheers,
Morag

How is your trigger monitor running? Foreground/background.

How are you triggering the application? Foreground/background? Perhaps you can show us the queue and process object definitions involved. 

This page in IBM Docs might be useful.

Cheers,
Morag