| Author |
Message
|
| praveenmq |
 Posted: Sun Jan 06, 2013 1:57 am Post subject: amqzlaa0.exe |
 |
|
Voyager
Joined: 28 Mar 2009
Posts: 96
|
Hi All
What is amqzlaa0.exe?
Recently in my mq logs i can see that this particular process is failed throwing internal MQ process error occured ..(AMQ6118 followed by AMQ6184)
The failing process is xxxxxx. When i check the process id in task manager it is amqzlaa0.exe. Is this process(amqzlaa0.exe) has an greater impact.
FFDC files are generated with probe id:XC377010 regularly
Sorry for not pasting the logs, Since am in VPN connectivity i cant get the log files.
I am running a MQV5.3.0.13 in windows server 2000
I know its out of support but client insists to keep it that way
_________________
Jack |
|
| Back to top |
|
 |
| exerk |
| Posted: Sun Jan 06, 2013 3:28 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Amazingly there are a large number of hits for amqzlaa0, both on this board and Google in general...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| mvic |
| Posted: Sun Jan 06, 2013 5:02 am Post subject: Re: amqzlaa0.exe |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| praveenmq wrote: |
| I know its out of support but client insists to keep it that way |
I suppose they are not happy about the FDCs, though? I think they should obtain the latest MQ code from IBM and if the problem continues, then open a PMR to get support from IBM.
XC377010 does not appear in any document on the internet. Did you mis-type it? |
|
| Back to top |
|
|
| zpat |
| Posted: Sun Jan 06, 2013 5:08 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
You can apply the last fixpack for v5.3
However there is a point here, and I think it applies especially to Indian IT staff, is that the customer is not always right.
It's important to push back and to do the right thing - you are the IT person - it's up to you to make these decisions.
Running v5.3 except on an old system that is about to be turned off, is not a good idea. |
|
| Back to top |
|
|
| praveenmq |
| Posted: Sun Jan 06, 2013 6:25 am Post subject: Re: amqzlaa0.exe |
|
|
Voyager
Joined: 28 Mar 2009
Posts: 96
|
| mvic wrote: |
| praveenmq wrote: |
| I know its out of support but client insists to keep it that way |
I suppose they are not happy about the FDCs, though? I think they should obtain the latest MQ code from IBM and if the problem continues, then open a PMR to get support from IBM.
XC377010 does not appear in any document on the internet. Did you mis-type it? |
No i havent mistyped the XC377010, thats the probe id. I dont find any links related to it on google.
We cant open PMR since it is out of support.
_________________
Jack |
|
| Back to top |
|
|
| praveenmq |
| Posted: Sun Jan 06, 2013 6:27 am Post subject: |
|
|
Voyager
Joined: 28 Mar 2009
Posts: 96
|
| zpat wrote: |
You can apply the last fixpack for v5.3
However there is a point here, and I think it applies especially to Indian IT staff, is that the customer is not always right.
It's important to push back and to do the right thing - you are the IT person - it's up to you to make these decisions.
Running v5.3 except on an old system that is about to be turned off, is not a good idea. |
Latest fix pack is already applied CSD13. I have pushed a lot. If client is not ready to migrate i cant insist them to migrate.
_________________
Jack |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sun Jan 06, 2013 7:05 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You can't insist that they migrate.
However, as the IT person, you can explain that from an IT perspective, this is a no-brainer. You have done everything you can to solve the problem, and it can't be fixed without migration. And from an IT perspective, you always stay current simply to avoid being in this exact position.
If they choose to view it as a business problem, rather than an IT problem, then the choice is to pay the cost of living with the problem, or pay the cost to upgrade. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Jan 06, 2013 7:46 am Post subject: Re: amqzlaa0.exe |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
| praveenmq wrote: |
Hi All
What is amqzlaa0.exe?
Recently in my mq logs i can see that this particular process is failed throwing internal MQ process error occured ..(AMQ6118 followed by AMQ6184)
The failing process is xxxxxx. When i check the process id in task manager it is amqzlaa0.exe. Is this process(amqzlaa0.exe) has an greater impact.
FFDC files are generated with probe id:XC377010 regularly
Sorry for not pasting the logs, Since am in VPN connectivity i cant get the log files.
I am running a MQV5.3.0.13 in windows server 2000
I know its out of support but client insists to keep it that way |
I've seen this before. Management perceives that there is no problem because no applications have failed, no money transactions have been lost. This is not an external problem. This is only an inconvenience for IT folks.
You might want to begin logging these events, and reporting monthly the number and frequency. At some future date, you might sway management to upgrade.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.
Last edited by bruce2359 on Sun Jan 06, 2013 7:55 am; edited 2 times in total |
|
| Back to top |
|
|
| exerk |
| Posted: Sun Jan 06, 2013 7:48 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
A starting point for identifying the 'area' that and FDC falls within can be found HERE.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| mvic |
| Posted: Sun Jan 06, 2013 8:18 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| exerk wrote: |
| A starting point for identifying the 'area' that and FDC falls within can be found HERE. |
A starting point, indeed! I don't understand who that page is supposed to help, and what task it is supposed to help with. |
|
| Back to top |
|
|
| mvic |
| Posted: Sun Jan 06, 2013 8:26 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
|
| Back to top |
|
|
| markt |
| Posted: Sun Jan 06, 2013 8:29 am Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 508
|
|
| Back to top |
|
|
| exerk |
| Posted: Sun Jan 06, 2013 11:56 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| mvic wrote: |
| exerk wrote: |
| A starting point for identifying the 'area' that and FDC falls within can be found HERE. |
A starting point, indeed! I don't understand who that page is supposed to help, and what task it is supposed to help with. |
It can help eliminate what it isn't - the OP is way out of luck because of the unsupported configuration, so who knows, anything might be of help ultimately.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Jan 06, 2013 1:32 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
You can't insist that they migrate.
However, as the IT person, you can explain that from an IT perspective, this is a no-brainer. You have done everything you can to solve the problem, and it can't be fixed without migration. And from an IT perspective, you always stay current simply to avoid being in this exact position.
If they choose to view it as a business problem, rather than an IT problem, then the choice is to pay the cost of living with the problem, or pay the cost to upgrade. |
You need to tell your client this:
"As these errors only started to happen recently, and you've not changed MQ versions in years, it's mostly likely they were caused by an external change (OS or similar) somewhere else. As we have all the maintenance available for MQv5.3 applied, and you insist we stay on it, there's nothing more to be done. It's possible these errors will continue, and may cause disruption in the future. It's also possible that as you keep applying maintenance to the rest of the stack without upgrading WMQ these errors will get worse until WMQ stops working completely. I therefore need you to sign this paper <hand them a document> which indicates:
you accept this as a consequence of your decision not to upgrade WMQ;
you accept that I've warned you of possible future failures resulting from this course of action and you indemnify me against legal or other consequences resulting from such failure;
you accept that in the event of such a failure the only remediation will be a panic upgrade of WMQ which, as will be not the planned, staged and tested upgrade you'd get now if you stopped being stupid and allowed it, could cause further knock on effects and you similarly indemnify me against those;
you certify that you have reported the situation, my concerns and my suggestions to whoever is responsible in your organization for managing corporate risk & you have received acknowledgement of your report from them".
Once that's been signed & witnessed take a dozen copies, give one to your account manager for that client, one to whoever you report to and a few to various trusted friends. Do not give the original to your employer; rent a safety deposit box and put it there.
Because this is a disaster waiting to happen and when it does, it's going to come screaming down on your head and the same client management who don't want to take the time or the money to upgrade because it could affect their performance bonus will have no memory of any warnings you've given & will be leading the lynch mob.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
