ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » AMQ6118 - every time

Post new topic  Reply to topic
 AMQ6118 - every time « View previous topic :: View next topic » 
Author Message
tsobanski
PostPosted: Thu Apr 07, 2005 12:38 pm    Post subject: AMQ6118 - every time Reply with quote

Apprentice

Joined: 27 Sep 2004
Posts: 42
Hi
I have instalation MQ Series on linux and each command f.e. dspmq, strmqm is generating FDC file with AMQ6118 error. Below is egzapmle of such file. Did enyone know what is wrong ??
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- poniedzia3ek kwiecien 04 20:06:42 UTC 2005 |
| Host Name :- tomek (Linux 2.4.19-16mdk) |
| PIDS :- 5724B4104 |
| LVLS :- 530 |
| Product Long Name :- WebSphere MQ for Linux for Intel |
| Vendor :- IBM |
| Probe Id :- XC076001 |
| Application Name :- MQM |
| Component :- xcsGetMessage |
| Build Date :- Oct 12 2002 |
| CMVC level :- p000-L021011 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000502 (mqm) |
| Program Name :- dspmq |
| Thread-Process :- 00002601 |
| Thread :- 00000001 |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- xecX_E_CONV_NOT_SUP |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred |
| (20006047) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 536895559 20006047 |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack
xcsGetMessage
xcsFFST

MQM Trace History
--{ xcsFreeMem
--} xcsFreeMem rc=OK
-} xusDelStanzaLineList rc=OK
-{ xusDelStanzaLineList
--{ xcsFreeMem
--} xcsFreeMem rc=OK
-} xusDelStanzaLineList rc=OK
-{ xusReadSingleStanza
--{ xcsSetlocale
--} xcsSetlocale rc=OK
--{ xusGetLineType
--} xusGetLineType rc=OK
--{ xusAddStanzaLineList
---{ xcsGetMem
---} xcsGetMem rc=OK
--} xusAddStanzaLineList rc=OK
--{ xusGetLineType
--} xusGetLineType rc=Unknown(1)
--{ xusAddStanzaLineList
---{ xcsGetMem
---} xcsGetMem rc=OK
--} xusAddStanzaLineList rc=OK
--{ xusGetLineType
--} xusGetLineType rc=Unknown(1)
--{ xusAddStanzaLineList
---{ xcsGetMem
---} xcsGetMem rc=OK
--} xusAddStanzaLineList rc=OK
--{ xusGetLineType
--} xusGetLineType rc=Unknown(1)
--{ xusAddStanzaLineList
---{ xcsGetMem
---} xcsGetMem rc=OK
---} xcsGetMem rc=OK
--} xusAddStanzaLineList rc=OK
--{ xusGetLineType
--} xusGetLineType rc=OK
-} xusReadSingleStanza rc=OK
-{ xusDelStanzaLineList
--{ xcsFreeMem
--} xcsFreeMem rc=OK
-} xusDelStanzaLineList rc=OK
-{ xusDelStanzaLineList
--{ xcsFreeMem
--} xcsFreeMem rc=OK
-} xusDelStanzaLineList rc=OK
-{ xusDelStanzaLineList
--{ xcsFreeMem
--} xcsFreeMem rc=OK
-} xusDelStanzaLineList rc=OK
-{ xusDelStanzaLineList
--{ xcsFreeMem
--} xcsFreeMem rc=OK
-} xusDelStanzaLineList rc=OK
-{ xusReadSingleStanza
--{ xcsSetlocale
--} xcsSetlocale rc=OK
--} xcsSetlocale rc=OK
--{ xusGetLineType
--} xusGetLineType rc=OK
--{ xusAddStanzaLineList
---{ xcsGetMem
---} xcsGetMem rc=OK
--} xusAddStanzaLineList rc=OK
--{ xusGetLineType
--} xusGetLineType rc=Unknown(1)
--{ xusAddStanzaLineList
---{ xcsGetMem
---} xcsGetMem rc=OK
--} xusAddStanzaLineList rc=OK
--{ xusGetLineType
--} xusGetLineType rc=Unknown(1)
--{ xusAddStanzaLineList
---{ xcsGetMem
---} xcsGetMem rc=OK
--} xusAddStanzaLineList rc=OK
--{ xusGetLineType
--} xusGetLineType rc=Unknown(1)
--{ xusAddStanzaLineList
---{ xcsGetMem
---} xcsGetMem rc=OK
--} xusAddStanzaLineList rc=OK
-} xusReadSingleStanza rc=Unknown(2)
-{ xusDelStanzaLineList
--{ xcsFreeMem
--} xcsFreeMem rc=OK
-} xusDelStanzaLineList rc=OK
-{ xusDelStanzaLineList
--{ xcsFreeMem
--} xcsFreeMem rc=OK
-} xusDelStanzaLineList rc=OK
-{ xusDelStanzaLineList
--{ xcsFreeMem
--} xcsFreeMem rc=OK
-} xusDelStanzaLineList rc=OK
-{ xusDelStanzaLineList
--{ xcsFreeMem
--} xcsFreeMem rc=OK
-} xusDelStanzaLineList rc=OK
-{ xufCloseIniRead
-} xufCloseIniRead rc=OK
} xcsBrowseIniCallback rc=OK
{ lpiSPIQueryQMStatus
-{ xcsInitialize
--{ xcsRequestThreadMutexSem
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsConnectSharedSubpool
---{ xcsAttachSharedSubpool
----{ xcsGetMem
----} xcsGetMem rc=OK
----{ xcsCreateThreadMutexSem
----} xcsCreateThreadMutexSem rc=OK
----{ xcsCreateThreadMutexSem
----} xcsCreateThreadMutexSem rc=OK
----{ xcsGetMem
----} xcsGetMem rc=OK
----{ xcsConnectSharedMemSet
-----{ xcsRequestThreadMutexSem
-----} xcsRequestThreadMutexSem rc=OK
-----{ xcsRequestThreadMutexSem
-----} xcsRequestThreadMutexSem rc=OK
-----{ xcsReleaseThreadMutexSem
-----} xcsReleaseThreadMutexSem rc=OK
-----{ xstAttachSharedMemSet
------{ xstConnectExtent
-------{ xcsRequestThreadMutexSem
-------} xcsRequestThreadMutexSem rc=OK
-------{ xstGetShmIdFromFile
-------{ xstGetShmIdFromFile
-------} xstGetShmIdFromFile rc=xecX_E_NO_SUCH_EXTENT
-------{ xcsReleaseThreadMutexSem
-------} xcsReleaseThreadMutexSem rc=OK
------} xstConnectExtent rc=xecX_E_NO_SUCH_EXTENT
-----} xstAttachSharedMemSet rc=xecX_E_NO_SUCH_EXTENT
-----{ xcsReleaseThreadMutexSem
-----} xcsReleaseThreadMutexSem rc=OK
----} xcsConnectSharedMemSet rc=xecX_E_NO_SUCH_EXTENT
----{ xcsFreeMem
----} xcsFreeMem rc=OK
----{ xcsDestroyThreadMutexSem
----} xcsDestroyThreadMutexSem rc=OK
----{ xcsDestroyThreadMutexSem
----} xcsDestroyThreadMutexSem rc=OK
----{ xcsFreeMem
----} xcsFreeMem rc=OK
---} xcsAttachSharedSubpool rc=xecX_E_NO_SUCH_EXTENT
--} xcsConnectSharedSubpool rc=xecI_E_NO_SUCH_SUBPOOL
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} xcsInitialize rc=xecI_S_FAIL
-{ xcsBrowseIniCallback
--{ xufOpenIniRead
--{ xufOpenIniRead
---{ xufHasAccessToStanzaFile
---} xufHasAccessToStanzaFile rc=Unknown(1)
--} xufOpenIniRead rc=OK
--{ xusReadSingleStanza
---{ xcsSetlocale
---} xcsSetlocale rc=OK
---{ xusGetLineType
---} xusGetLineType rc=OK
---{ xusAddStanzaLineList
----{ xcsGetMem
----} xcsGetMem rc=OK
---} xusAddStanzaLineList rc=OK
---{ xusGetLineType
---} xusGetLineType rc=Unknown(1)
---{ xusAddStanzaLineList
----{ xcsGetMem
----} xcsGetMem rc=OK
---} xusAddStanzaLineList rc=OK
---{ xusGetLineType
---} xusGetLineType rc=OK
--} xusReadSingleStanza rc=OK
--{ xusDelStanzaLineList
---{ xcsFreeMem
---{ xcsFreeMem
---} xcsFreeMem rc=OK
--} xusDelStanzaLineList rc=OK
--{ xusDelStanzaLineList
---{ xcsFreeMem
---} xcsFreeMem rc=OK
--} xusDelStanzaLineList rc=OK
--{ xusReadSingleStanza
---{ xcsSetlocale
---} xcsSetlocale rc=OK
---{ xusGetLineType
---} xusGetLineType rc=OK
---{ xusAddStanzaLineList
----{ xcsGetMem
----} xcsGetMem rc=OK
---} xusAddStanzaLineList rc=OK
---{ xusGetLineType
---} xusGetLineType rc=Unknown(1)
---{ xusAddStanzaLineList
----{ xcsGetMem
----} xcsGetMem rc=OK
---} xusAddStanzaLineList rc=OK
---{ xusGetLineType
---} xusGetLineType rc=Unknown(1)
---} xusGetLineType rc=Unknown(1)
---{ xusAddStanzaLineList
----{ xcsGetMem
----} xcsGetMem rc=OK
---} xusAddStanzaLineList rc=OK
---{ xusGetLineType
---} xusGetLineType rc=OK
--} xusReadSingleStanza rc=OK
--{ zutQMStatusCallback
---{ xcsAddNewIniAttribute
----{ xcsGetMem
----} xcsGetMem rc=OK
---} xcsAddNewIniAttribute rc=OK
--} zutQMStatusCallback rc=Unknown(9)
--{ xusDelStanzaLineList
---{ xcsFreeMem
---} xcsFreeMem rc=OK
--} xusDelStanzaLineList rc=OK
--{ xusDelStanzaLineList
---{ xcsFreeMem
---} xcsFreeMem rc=OK
--} xusDelStanzaLineList rc=OK
--{ xusDelStanzaLineList
---{ xcsFreeMem
---{ xcsFreeMem
---} xcsFreeMem rc=OK
--} xusDelStanzaLineList rc=OK
--{ xusDelStanzaLineList
---{ xcsFreeMem
---} xcsFreeMem rc=OK
--} xusDelStanzaLineList rc=OK
--{ xufCloseIniRead
--} xufCloseIniRead rc=OK
-} xcsBrowseIniCallback rc=OK
} lpiSPIQueryQMStatus rc=OK
{ xcsGetMessage
-{ xcsQueryCCSIDType
-} xcsQueryCCSIDType rc=OK
-{ xcsConvertString
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
--{ xcsRequestThreadMutexSem
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} xcsConvertString rc=xecX_E_CONV_NOT_SUP
-{ xcsBuildDumpPtr
--{ xcsGetMem
--} xcsGetMem rc=OK
-} xcsBuildDumpPtr rc=OK
Back to top
View user's profile Send private message
Anirud
PostPosted: Thu Apr 07, 2005 12:46 pm    Post subject: Reply with quote

Master

Joined: 12 Feb 2004
Posts: 285
Location: Vermont
Looks like you did not install any Fix Pack (CSD) on top of the base MQ install.
Install the latest Fix Pack (CSD09) and hopefully that will take care of the error.

You can download the Fix Pack from the following link.
http://www-306.ibm.com/software/integration/mqfamily/support/summary/
Back to top
View user's profile Send private message Visit poster's website
vennela
PostPosted: Thu Apr 07, 2005 12:49 pm    Post subject: Reply with quote

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
Also:
Export the variable LD_ASSUME_KERNEL

Code:
export LD_ASSUME_KERNEL=2.4.19
Back to top
View user's profile Send private message Send e-mail Visit poster's website
archit_agarwal
PostPosted: Wed Jul 12, 2006 11:37 pm    Post subject: Reply with quote

Novice

Joined: 14 Jan 2006
Posts: 16
I knew the reply came very late.. but its for future use..
I faced the same kind of problem..
Please try to check that where exactly the MQ libraries have been picked.
set the LD_LIBRARY_PATH {for unix-AIX/SOlaris/Linux env}.
properly to indicate the <mqm top>/lib before any other product code..

I hope this will help in finding the resolution
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger MSN Messenger
hkhan12
PostPosted: Mon Aug 11, 2008 12:15 am    Post subject: Reply with quote

Voyager

Joined: 08 Aug 2002
Posts: 98
Hi There,

Currently I'm facing similar issue. I have installed WMQ5.3 on a Windows 2003 server. When I run dspmq and other commands, it is generating FDCs. Through MQExplorer I'm able to start queue managers and even able to create new queue managers.

When I tried to apply FixPack 12, it is complaing about other MQ files are in use. I have checked no MQ files are in use. In fact, I tried to install from the command prompt using following command pattern:
ABCXYZ.exe MQPINUSEOK=1

Hence, I could not apply fixpack.

Here is some part of the FDC which is complaining about RUNMQLSR below. I put it in red.

All your help would be highly appreciated.

+-----------------------------------------------------------------------------+

| |

| WebSphere MQ First Failure Symptom Report |

| ========================================= |

| |

| Date/Time :- Sun August 10 13:25:40 Arab Standard Time 2008 |

| Host Name :- RUH-002-MNE-001 (Windows Ver 5.2 Build 3790: Service |

| Pack 1) |

| PIDS :- 5724B4100 |

| LVLS :- 530 |

| Product Long Name :- WebSphere MQ for Windows |

| Vendor :- IBM |

| Probe Id :- XC076001 |

| Application Name :- MQM |

| Component :- xcsGetMessage |

| Build Date :- Oct 12 2002 |

| CMVC level :- p000-L021011 |

| Build Type :- IKAP - (Production) |

| UserID :- MUSR_MQADMIN |

| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\RUNMQLSR.exe |
| Process :- 00000280 |

| Thread :- 00000001 |

| Major Errorcode :- xecF_E_UNEXPECTED_RC |

| Minor Errorcode :- xecX_E_CONV_NOT_SUP |

| Probe Type :- MSGAMQ6118 |

| Probe Severity :- 2 |

| Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred |

| (20006047) |

| FDCSequenceNumber :- 0 |

| Arith1 :- 536895559 20006047 |

| |

+-----------------------------------------------------------------------------+
Back to top
View user's profile Send private message
Gaya3
PostPosted: Mon Aug 11, 2008 12:29 am    Post subject: Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
go through this link

http://www-1.ibm.com/support/docview.wss?uid=swg21226154
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
hkhan12
PostPosted: Mon Aug 11, 2008 12:41 am    Post subject: Reply with quote

Voyager

Joined: 08 Aug 2002
Posts: 98
Hi GAYA3,

Thanks a lot for your quick response. I have seen this link but don't know how to display locale details or what command I should run on command prompt. Of course, I'm talking about Windows Platform.

I have tried run Locale and LANG commands but nothing works.

Any input would be great help. Again, thanks a lot.

Regards,
Back to top
View user's profile Send private message
exerk
PostPosted: Mon Aug 11, 2008 1:04 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339
hkhan12 wrote:
...Of course, I'm talking about Windows Platform.

I have tried run Locale and LANG commands but nothing works.

Any input would be great help. Again, thanks a lot.

Regards,


Try Control Panel -> Regional and Language Options. That should give you what option has been set at your location.

As regards your issue with RUNMQLSR, did you check processes in Task Manager to see that everything was down?
_________________
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
View user's profile Send private message
David.Partridge
PostPosted: Mon Aug 11, 2008 1:05 am    Post subject: Reply with quote

Master

Joined: 28 Jun 2001
Posts: 249
The error is probably occurring because the CCSID for your queue manager is set to a value such that there is no conversion table for the MQ headers coming from the queue manager at the other end of the channel.

If your queue manager CCSID is set to the value your really need it to be (and there isn't another CCSID which would work well and for which conversion tables do exist for data from the remote QM), then you may need to enable default data conversion

This allows MQ to handle the case where there isn't a conversion table available to do the conversion requested. Here's a copy/paste from the relevant part of the docs.

Default data conversion:

If you set up channels between two machines on which data conversion is not normally supported, you must enable default data conversion for the channels to work.

To enable default data conversion, edit the ccsid.tbl file to specify a default EBCDIC CCSID and a default ASCII CCSID. Instructions on how to do this are included in the file. You must do this on all machines that will be connected using the channels. Restart the queue manager for the change to take effect.

The default data-conversion process is as follows:

If conversion between the source and target CCSIDs is not supported, but the CCSIDs of the source and target environments are either both EBCDIC or both ASCII, the character data is passed to the target application without conversion.

If one CCSID represents an ASCII coded character set, and the other represents an EBCDIC coded character set, WebSphere MQ converts the data using the default data-conversion CCSIDs defined in ccsid.tbl.

Note:
Try to restrict the characters being converted to those that have the same code values in the coded character set specified for the message and in the default coded character set. If you use only the set of characters that is valid for WebSphere MQ object names (as defined in Names of WebSphere MQ objects) you will, in general, satisfy this requirement. Exceptions occur with EBCDIC CCSIDs 290, 930, 1279, and 5026 used in Japan, where the lowercase characters have different codes from those used in other EBCDIC CCSIDs.
_________________
Cheers,
David C. Partridge
Back to top
View user's profile Send private message
David.Partridge
PostPosted: Mon Aug 11, 2008 1:07 am    Post subject: Reply with quote

Master

Joined: 28 Jun 2001
Posts: 249
You could try setting the QMGR code page (CCSID) to 1208 which is UTF8.

This would allow ANY character to be represented in data or MQ headers, and because of the nature of MQ headers and data contained within them you won't have any problem with any data in the headers translating to code points that require more than 1 byte in UTF8.
_________________
Cheers,
David C. Partridge
Back to top
View user's profile Send private message
hkhan12
PostPosted: Tue Aug 12, 2008 12:02 am    Post subject: Reply with quote

Voyager

Joined: 08 Aug 2002
Posts: 98
Hi Guys,

Thank you so much to all of you for responding to my post.

Actually, I have reboot the machine and every thing in place. It is wierd, isn't it?

Anyway, it is working fine without any issues.

Again, you guys are genious and always try to help people here on this forum. Keep it up guys.

Regards,
Back to top
View user's profile Send private message
dk27
PostPosted: Wed Feb 25, 2009 10:11 am    Post subject: Reply with quote

Acolyte

Joined: 28 Apr 2008
Posts: 51
David.Partridge wrote:

Default data conversion:

If you set up channels between two machines on which data conversion is not normally supported, you must enable default data conversion for the channels to work.


Does this means that I have to set convert as yes on the sender side of the channel?
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » AMQ6118 - every time
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.