| Author |
Message
|
| jefflowrey |
 Posted: Tue Nov 01, 2005 10:01 am Post subject: More information about a fix |
 |
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I've got an issue where a system generated an FDC.
I looked up the probe ID, and lucky for me, I've got a fairly unique probe ID, and there is also a fix available in newer CSDs
But I really need more information about the issue as well - and there doesn't seem to be any useful information, and the fix number doesn't have an IY or IC or any other prefix, and I can't get from the Fix list to more information about the fix itself.
The Probe ID is ZF154006, and the Fix has a number of 70872. But I can't get any more information than just the number and the basic description of the problem.
Also, alas, the FDC was thrown by WAS 5 embedded MQ, and not by full MQ.
Can I apply full MQ CSDs to a system that only has the Embedded MQ installed? (I seem to remember that it was okay, but I don't trust my memory).
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Tue Nov 01, 2005 12:32 pm Post subject: Re: More information about a fix |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| jefflowrey wrote: |
| Can I apply full MQ CSDs to a system that only has the Embedded MQ installed? (I seem to remember that it was okay, but I don't trust my memory). |
I seem to remember that you weren't supposed to do this. I thought the embedded JMS (ie, WMQ fixes) were bundled with WAS so that you were getting a complete package that worked. |
|
| Back to top |
|
|
| PGoodhart |
| Posted: Wed Nov 02, 2005 4:10 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
Yes you should be patching WAS not MQ. Which version/fix pac of WAS are you running?
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Nov 02, 2005 4:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| PGoodhart wrote: |
| Yes you should be patching WAS not MQ. Which version/fix pac of WAS are you running? |
I'm not sure at the moment (technically, I'm on vacation, so hopefully it will be resolved by the time I get back).
It's WAS on Solaris for the sole purpose of running IBM Tivoli Identitiy Manager - so I'm rather sure that it's whatever version of WAS is specified as being supported for whatever version of ITIM we're running - which I'm pretty sure is the most recent (it's definately either 4.2 or 4.3, not anything earlier).
But it seems there's no way to get more info about fix 70872?
I'm really not sure that the FDC from embedded MQ has much to do with the problems they're having with ITIM. So I'd rather treat it as symptomatic rather than causal.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Nov 02, 2005 7:36 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| jefflowrey wrote: |
| I'm not sure at the moment (technically, I'm on vacation, so hopefully it will be resolved by the time I get back). |
Ummmm....You are more dedicated than me. When I go on vacation, I usually don't check mqseries.net..... |
|
| Back to top |
|
|
| PGoodhart |
| Posted: Wed Nov 02, 2005 11:01 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
So all you could find was 70872 - An FDC with probe id ZF154006 occurred in component wasSecServiceInit from program amqzlaa0.
I think these unprefixed issues might be fixes made without user request found in house.
I think I'd have to open a ticket with IBM MQ and WAS Support and ask them. I bet support has a database with the issue described better then what you found.
WAS is at version 6, and I think 5.1 is low current. I think 5.1.1.3 is one of the lowest stable versions. I'll bet they last picked up the MQ fixes when they did the last major release. Also from experience the WAS fix pacs aren't always complete, you need supporting software upgraded as well to make everything work (xerces/xalan etc.) so if this is a production box, tread lightly if you can.
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Nov 02, 2005 12:22 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| PGoodhart wrote: |
| So all you could find was 70872 - An FDC with probe id ZF154006 occurred in component wasSecServiceInit from program amqzlaa0. |
I haven't seen this particular incident, but the 70872 sounds like an internal defect number for a problem that IBM found and fixed before a customer found it. Depending on the problem, there is (or is not) more information in the internal databases. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Nov 02, 2005 1:14 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| bower5932 wrote: |
| PGoodhart wrote: |
| So all you could find was 70872 - An FDC with probe id ZF154006 occurred in component wasSecServiceInit from program amqzlaa0. |
I haven't seen this particular incident, but the 70872 sounds like an internal defect number for a problem that IBM found and fixed before a customer found it. Depending on the problem, there is (or is not) more information in the internal databases. |
We agree.
I was hoping that there was some mechanism other than straight searching for getting at information that wasn't necessarily in the internal databases, but was perhaps just not indexed properly or etc.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
