| Author |
Message
|
| ivanachukapawn |
 Posted: Fri Apr 16, 2010 9:51 am Post subject: MAK7 - event log error for trigger on Win XP Pro |
 |
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
Invalid application type received: type=9. (See Data: for message received)
My process definition specifies Windows for the application type.
I'm running on a Windows XP Pro laptop - the INITQ and Process Definition are on an ZOS QM.
Why invalid? |
|
| Back to top |
|
 |
| ivanachukapawn |
| Posted: Fri Apr 16, 2010 10:18 am Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
For your info:
I wandered through the table for Application Type (in the Process Definition) trying different application types (because Windows was invalid for my Win XP Pro laptop). I tried batch, dos, default, etc. Nothing worked until I tried Windows NT. Now everything is OK.[/list] |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Apr 16, 2010 12:23 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Yeah.
The code right now specifically looks for MQAT_WINDOWS_NT.
I will make this more flexible in the next release, but I don't have a firm ship date for the next release (except "as soon as I can now that I've shipped ms03"). |
|
| Back to top |
|
|
| ivanachukapawn |
| Posted: Tue Apr 20, 2010 7:28 am Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
| Thanks for that info about WINDOWS_NT specification on app type. Now everything is working smoothly. I notice that ma7k has retry/reconnection logic built-in which is configurable. That is very good. In the event that the service can't re-establish reconnection to the qmgr the service will be stopped and a message will be written to the Windows event log. If this happens at 3am I will want to get a message on my BlackBerry/iPhone. So I am researching Windows event log monitoring/alerting off-the-shelf products. I know this subject is out-of-scope for ma7q but could you provide any information you might have as to how people have been meeting this requirement? I'm not looking for a recommendation, just some information about possible solutions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Apr 20, 2010 7:58 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I don't actually have any information about how other customers are doing that.
You can probably get an inhouse programmer to do something fairly simple with PowerShell or .NET to read the event log and send an email or a page or something.
There are probably thousands of "free" utilities to do this as well. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Apr 20, 2010 1:51 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Talk to the monitoring people in your shop. I'm sure they have a product that can monitor Windows Event logs and alert accordingly on whatever Event ID you want.
Additionally you can monitor the IPROCS count on the Init queue and alert when it drops to zero, although this isn't 100% (maybe something else opens the queue, maybe the queue is open but the TM is hung.)
Monitor the Init queue for Q Depth > 1.
Have multiple MA7Ks on multipel MQ Client app machines all racing for the same trigger messages.
Implement all of the above and sleep easy.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
