Author |
Message
|
bruce2359 |
Posted: Thu Oct 08, 2009 8:19 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9475 Location: US: west coast, almost. Otherwise, enroute.
|
Quote: |
...OS version which they can Upgrade so that the current MQ 5.3.7 will work |
You are asking which o/s will work with an unsupported version of MQ.
What happens if (when) you install unsupported 5.3.7 on what IBM states is/was a compatible o/s AND there are MQ problems/issues? IBM will not support 5.3.7 - it's an unsupported version. What will you (your management) do then? Fall back to an unsupported version of the o/s?
This is exactly why you (your clients) should upgrade to supported versions - of all products. Upgrades should be part of ongoing application support, and not an event driven solely by new product features. _________________ 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. |
|
Back to top |
|
 |
satya_jammy |
Posted: Thu Oct 08, 2009 9:50 am Post subject: |
|
|
Acolyte
Joined: 01 Oct 2009 Posts: 66
|
ok i agree with all of you. But my manager says that he wants confirmation from IBM MQ Prodcut Team That Our Current Version MQ 5.3 CSD 7 wont work in SUNOS 10 before he goes and tell to client. I have never contacted IBm Product Team bfr.If you dont mind. Now can you please tell me how i can contact product team and get confirm with them. Please |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Oct 08, 2009 9:59 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9475 Location: US: west coast, almost. Otherwise, enroute.
|
Quote: |
he wants confirmation from IBM MQ Prodcut Team That Our Current Version MQ 5.3 CSD 7 wont work in SUNOS 10 |
I doubt IBM will make such a statement. Why? I doubt they have tested to determine if an out-of-support version of MQ will run on a current o/s.
What IBM will tell you is that version 5 is not supported on any platform, including sunos10. _________________ 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. |
|
Back to top |
|
 |
satya_jammy |
Posted: Thu Oct 08, 2009 10:12 am Post subject: |
|
|
Acolyte
Joined: 01 Oct 2009 Posts: 66
|
I agree with you.
But now all i can do is to contact the IBM product Team To get confirm whether We can INSTALL MQ 5.3 CSD7 on SUN OS 10 or not and need to show that email confirmation from IBM to my Client and ask them not to go for an OS Upgrade as of Now and to go for an MQ upgrade ASAP.
Please let me know how i can contact product team on this. |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Oct 08, 2009 10:15 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9475 Location: US: west coast, almost. Otherwise, enroute.
|
Open a PMR through the ibm support webpage. _________________ 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. |
|
Back to top |
|
 |
Vitor |
Posted: Thu Oct 08, 2009 10:31 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
satya_jammy wrote: |
Please let me know how i can contact product team on this. |
The product team don't talk to end users (except occassionally through this forum!) so you'll need to raise a PMR via the support desk.
They will almost certainly tell you that v5.3 is out of support so IBM don't provide any support (even emails) on the subject.
The other (somewhat costly) option is to try and buy extended support for their v5.3.7 installation. You'd need to speak to your IBM sales rep to see how costly (or if indeed it's available in this instance). _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Oct 08, 2009 11:06 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
You can see what the supported platforms for MQ v5.3 are.
Mind you, in no way does this mean that v5.3 is supported at all. But when it was, those were the platforms it was supported on.
http://www-01.ibm.com/software/integration/wmq/requirements/index.html#WebSphereMQV53
But that almost certainly only applies to the last FP, 14, of WMQ v5.3 and not to FixPack 7.
No matter what else the client does, they absolutely should update to FP 14 of v5.3. |
|
Back to top |
|
 |
Vitor |
Posted: Thu Oct 08, 2009 11:17 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
mqjeff wrote: |
But that almost certainly only applies to the last FP, 14, of WMQ v5.3 and not to FixPack 7. |
I think I said something similar.
mqjeff wrote: |
No matter what else the client does, they absolutely should update to FP 14 of v5.3. |
 _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
satya_jammy |
Posted: Mon Oct 19, 2009 2:46 am Post subject: |
|
|
Acolyte
Joined: 01 Oct 2009 Posts: 66
|
hi
We are planning to apply fix pack 14 for MQ 5.3. AS i mentioned early curently we are using MQ CSD7 . can i directly apply CSD 14 to it or do i need to install any other previous FP before upgrading to 14 ? |
|
Back to top |
|
 |
exerk |
Posted: Mon Oct 19, 2009 2:51 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
Just apply the FixPack. Check its Readme for further information. _________________ 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 |
|
 |
satya_jammy |
Posted: Mon Nov 09, 2009 7:17 am Post subject: |
|
|
Acolyte
Joined: 01 Oct 2009 Posts: 66
|
hi
as i mentioned earlier We have placed the image of MQ in new physical server with OS SunOS 5.8 Generic_Virtual sun4v sparc SUNW,T5240 (old OSversion SunOS 5.7 Generic_106541-46 sun4u sparc SUNW,Ultra-Enterpri
i am able to use the dspmqm command and can see the qmanagers that are migrated in new physical server
but the Qmanagers are not getting started and i am even unable to create a new Qmanager
when i am trying to start i am getting the following error
AMQ6109: An internal WebSphere MQ error has occurred.
11/09/09 08:07:43
AMQ6090: WebSphere MQ was unable to display an error message 16.
EXPLANATION:
MQ has attempted to display the message associated with return code hexadecimal
'16'. The return code indicates that there is no message text associated with
the message. Associated with the request are inserts 0 : 0 : : : .
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
-------------------------------------------------------------------------------
11/09/09 08:07:43
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 4961.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 713 --------------------------------------------------------
11/09/09 08:07:43
AMQ6109: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the MQ error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 673 --------------------------------------------------------
11/09/09 08:07:43
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 4961.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 713 --------------------------------------------------------
here is the fdc generated
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Monday March 23 07:44:58 MDT 2009 |
| Host Name :- wcdevtst (SunOS 5.7) |
| PIDS :- 5724B4103 |
| LVLS :- 530.7 CSD07 |
| Product Long Name :- WebSphere MQ for Sun Solaris |
| Vendor :- IBM |
| Probe Id :- XY324192 |
| Application Name :- MQM |
| Component :- GetSubpoolsLock |
| Build Date :- May 27 2004 |
| CMVC level :- p530-07-L040527 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000104 (mqm) |
| Program Name :- runmqchl_nd |
| Process :- 00004961 |
| Thread :- 00000001 |
| QueueManager :- MQPROD |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| ('22 - Invalid argument' from semop.) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 22 16 |
| Comment1 :- '22 - Invalid argument' from semop. |
| |
| |
+-----------------------------------------------------------------------------+
And when i am trying to create a QM using crtmam QMNAME i am getting the error AMQ8101: WebSphere MQ error (893) has occurred.
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Monday November 09 08:58:27 MST 2009 |
| Host Name :- wcdevtst (SunOS 5. |
| PIDS :- 5724B4103 |
| LVLS :- 530.7 CSD07 |
| Product Long Name :- WebSphere MQ for Sun Solaris |
| Vendor :- IBM |
| Probe Id :- XC303040 |
| Application Name :- MQM |
| Component :- xlsCreateMutex |
| Build Date :- May 27 2004 |
| CMVC level :- p530-07-L040527 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000104 (mqm) |
| Program Name :- crtmqm |
| Process :- 00015237 |
| Thread :- 00000001 |
| Major Errorcode :- Unknown(16) |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ0016 |
| Probe Severity :- 4 |
| Probe Description :- AMQ6090: WebSphere MQ was unable to display an error |
| message 16. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
xcsCreateSharedSubpool
xclCSCreateMutex
xlsCreateMutex
xcsFFST
Please suggest how i can fix this problem |
|
Back to top |
|
 |
Vitor |
Posted: Mon Nov 09, 2009 8:22 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
satya_jammy wrote: |
Please suggest how i can fix this problem |
- Follow the advice given for those probe ids
- Upgrade to a supported version of WMQ _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
satya_jammy |
Posted: Mon Nov 09, 2009 9:45 am Post subject: |
|
|
Acolyte
Joined: 01 Oct 2009 Posts: 66
|
do you mean the current CD 07 is not supportedeven in solaris 5.8 too ?will apllying fixpack CSD 14 fixes this issue? |
|
Back to top |
|
 |
Vitor |
Posted: Mon Nov 09, 2009 9:54 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
satya_jammy wrote: |
do you mean the current CD 07 is not supportedeven in solaris 5.8 too ? |
No version of WMQv5.3 is supported; not CSD07, not CSD14.
satya_jammy wrote: |
will apllying fixpack CSD 14 fixes this issue? |
I don't know. But if you look back through this thread, CSD14 has been recommended before for many good reasons.
But the best advice remains to upgrade to a supported version. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
exerk |
Posted: Mon Nov 09, 2009 9:54 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
satya_jammy wrote: |
do you mean the current CD 07 is not supportedeven in solaris 5.8 too ?will apllying fixpack CSD 14 fixes this issue? |
No. Vitor means that Version 5.3 is no longer supported - unless your site purchased extended support from IBM, in which case open a PMR. _________________ 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 |
|
 |
|