Re: Workload Balancing is not working with some cluster queues
Hello, thank you all for your answers.I checked everything you recommended but did not find anything wrong. I was able to send messages from QMGR5 to cluster queues defined only in QMGR3 but it was impossible to make the load balance to work with QMGR3 and QMGR1.I checked channels, qmgrs, queues, and finally decided to rebuild the entire cluster.That solved the problem, now I have load balance with the exact same configuration for all the objects but with a new cluster. Thank you all again, Yonny. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Workload Balancing is not working with some cluster queues
WMQ 5.3 for AIX and HP. QY and QZ are local queues shared in the cluster. AIX BOX1 QMGR1 --> QY QMGR2 --> QZ AIX BOX2 QMGR3 --> QY QMGR4 --> QZ HP Box QMGR5 I am trying to put messages using amqsput to queues QY and QZ: Using: amqsput QY QMGR5 the workload balancing DO NOT work, all messages are sent to QMGR1. Using. amqsput QZ QMGR5 the workload balancing DOES work. The four definitions of the queues have DefBind = NotFixed. The worload balancing is not working for any cluster queue defined in both QMGR1 and QMGR3. The comunication between QMGR5 and QMGR3 is perfect cause I am able to send messages from QMGR5 to cluster queues defined only in QMGR3. What can i do?TIA, Yonny Serrano Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Backup and restore of qmgr over iSeries
The process described in the Sys Admin MQ 5.3 manual for iSeries "Restoring a complete queue manager (data and journals)" allows me to restore a complete qmgr even in a different machine (tha's what I need). But, because of the CRTMQM command involved in the process the QMID of the source qmgr is not the same in the target qmgr. Is it posible to make a restore of one qmgr in another machine that include the QMID? If yes, how? If not, why? Thank you in advance Yonny R. Serrano Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Same question in other words
Production as/400 Box1QMGR01 running Contingency as/400 Box2 QMGRx stand by Within an mq cluster I have QMGR01 running over AS/400. In the event of a fatal failure other qmgr, in a separate box, should replace the as/400 qmgr. Both qmgrs have the same queues. How can I make the cluster to recognize the backup qmgr? I am confused because the contingency as/400 box will take the ip address of the production box. Is it posible to use the same name for both qmgrs? Any ideas will be apreciated. Yonny R. Serrano GBM Dominicana Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Contingency enviroment question for AS/400 qmgr
Hello everyone. I need your help giving me suggestions about a contingency enviroment. I have a queue manager (QM1) running over an IBM iSeries, the qmgr belongs to a mq cluster whose repositories are running on aix boxes. I need to duplicate QM1 in a separate contingency iSeries box. I tried creating a new qmgr with the same name but the cluster does not recognize it because of the QMID. The contingency box takes is configured to take the ip address of the production box in a several failure event. Please let me know if you need other details of the enviroment. I will apreciate any comments. Yonny R. Serrano GBM Dominicana Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
WMQI and Microsoft SQL Stored Procedures
Hello, I need to connect a message flow to a database (SQL Server) to run a stored procedure. The broker is running over AIX. I found information about connections to DB2 and Oracle but anything about MS SQL. How can I do that? Is it necessary to build a program that connects MQ with SQL Server (getting a message from MQ and calling the stored procedure)? Any help will be apreciated. Regards, Yonny R. Serrano. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Error adding Element to Workspace: Trace
Yes, they are at the same maintenance level, both are running in the same box, the broker is on AIX, and is also at the latest CSD level. Any idea? Yonny. Yonny Serrano/GBM 13/09/2003 02:10 To p.m. MQSeries List <[EMAIL PROTECTED]> cc Subject Error adding Element to Workspace: Trace Hello, This is the trace of the Control Center that I get when trying to add an Element to the workspace. If someone has any idea on how to solve this problem, please let me know. The file is the last part of the trace. Enviroment: Configuration manager over Windows 2K, DB2 7.1, wmqi 2.1 Regards, Yonny. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Error adding Element to Workspace: Trace
Hello,This is the trace of the Control Center that I get when trying to add an Element to the workspace. If someone has any idea on how to solve this problem, please let me know. The file is the last part of the trace. Enviroment:Configuration manager over Windows 2K, DB2 7.1, wmqi 2.1 Regards, Yonny. traceCC.txt Description: Binary data
MQ for OS/400: Security Question
Hello, We are implementing a group profile for MQSeries users. The group
profile has *CONNECT permission to the qmgr (QM), PREROUTING is a cluster
shared queue in a remote qmgr. The group profile is not part of QMQMADM.
The sample program works fine if we use an mq admin.
QMQMADM and QMQM have *USE auth for the CRTLIB command.
This is the job log that AMQSPUT0 generates (QM is a local qmgr in the
AS/400):
>> CALL PGM(QMQM/AMQSPUT0) PARM('PREROUTING' 'QM')
An internal MQSeries error has occurred ('3401 - Permission denied.'
from xcsFtok.)
Data length or data offset not valid.
Problem log updated.
Not authorized to command CRTLIB in library *LIBL.
Error found on CRTLIB command.
APAR library QSC4536804 not created
An internal MQSeries error has occurred.
Data length or data offset not valid.
Problem log updated.
Not authorized to command CRTLIB in library *LIBL.
Error found on CRTLIB
command.
APAR library QSC4536804 not
created
Pointer not set for location
referenced.
Data length or data offset not
valid.
Problem log
updated.
Not authorized to command CRTLIB in library
*LIBL.
Error found on CRTLIB
command.
APAR library QSC4765581 not
created
Application error. MCH3601 unmonitored by LIBMQMCS at
statement
19, instruction
X''.
Application error. CEE9901 unmonitored by AMQSPUT0 at
statement
08, instruction
X''.
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
WMQI Urgent help: Error when adding Element to workspace
I posted this error last week but did not get any answer. The Configuration Manager is running with WMQI is 2.1 with CSD05, the broker is running on AIX with WMQI 2.1 CSD05. Hello, Im getting this error when trying to add an element to the workspace. The error appeared for a message set that we import into a new config mgr. BIP0062E Cannot read the XML data stream for a resource. This is an internal error. The following error occurred when parsing an XML data stream. Processing MRM/84fdbd91-ed00--0080-81ece6f8b901/MRElement, at line 2 before column 8124, "" expected. Processing MRM/84fdbd91-ed00--0080-81ece6f8b901/MRElement, at line 2 before column 8124, Invalid document structure. Turn on Control Center tracing to capture details of the error. Retry the operation and contact your IBM support center. Thank you and regards, Yonny R. Serrano Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Error when adding Element to workspace
Hello, Im getting this error when Im trying to add an element to the workspace. The error appeared for a message set that we import into a new config mgr. BIP0062E Cannot read the XML data stream for a resource.This is an internal error.The following error occurred when parsing an XML data stream.Processing MRM/84fdbd91-ed00--0080-81ece6f8b901/MRElement, at line 2 before column 8124, "" expected.Processing MRM/84fdbd91-ed00--0080-81ece6f8b901/MRElement, at line 2 before column 8124, Invalid document structure. Turn on Control Center tracing to capture details of the error.Retry the operation and contact your IBM support center. Thank you and regards, Yonny R. Serrano Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Simple flow exception
Thank you Christopher As you said it was a problem with the RFH2, so we put it in the right place and everything is working fine. Regards, Yonny. Yonny Serrano/GBM 11/07/2003 11:52 To a.m. MQSeries List <[EMAIL PROTECTED]> cc Subject Simple flow exception Hello, I seem to have a problem with one of my flows, it's processing all the Compute Nodes and everything else just fine, but it's failing when it's outputting the message to it's OutputNode. The flow has one MQInput node going into a trycatch node which has 2 compute nodes that in turn go to the output node. I'm using a DestinationList Destination Mode which I'm setting in ESQL with using this properties: SET OutputLocalEnvironment.Destination.MQDestinationList.DestinationData.queueName ='CF.MODBCUSTREQ'; SET OutputLocalEnvironment.Destination.MQDestinationList.DestinationData.queueManagerName= 'CD.MQ.CF.DEV'; When it's about to put the message in the output Q it fails with this exception: ( (0x100)RecoverableException = ( (0x300)File= 'build/S210_P/src/DataFlowEngine/ImbMqOutputNode.cpp' (0x300)Line= 715 (0x300)Function= 'mbMqOutputNode::evaluate' (0x300)Type= 'ComIbmMQOutputNode' (0x300)Name= 'f82ff151-f600--0080-9a5867fb3d77' (0x300)Label = 'ModifyBusinessRequest_new_debug_.MQOutput1' (0x300)Text= 'aught exception and rethrowing' (0x300)Catalog = 'WMQIv210' (0x300)Severity= 3 (0x300)Number = 2230 (0x100)ParserException = ( (0x300)File = '/build/S210_P/src/DataFlowEngine/ImbRootParser.cpp' (0x300)Line = 261 (0x300)Function = 'ImbRootParser::refreshBitStreamFromElements' (0x300)Type = 'ComIbmMQInputNode' (0x300)Name = '3594f051-f600--0080-9a5867fb3d77' (0x300)Label= 'ModifyBusinessRequest_new_debug_.MQInput1' (0x300)Text = 'Invalid parser sequence' (0x300)Catalog = 'WMQIv210' (0x300)Severity = 2 (0x300)Number = 6062 (0x100)Insert = ( (0x300)Type = 5 (0x300)Text = 'MQHRF2' ) (0x100)Insert = ( (0x300)Type = 5 (0x300)Text = 'xml' ) ) ) ) If I dont use the trycatch node the error message goes to the error log of mqsi but still cannot complete the message flow. I am ataching a file with an xml sample message. The enviroment is AIX 4.3.3, MQSI 2.1 CSD05, MQSeries 5.3 with latest CSD. Thank you, Yonny Serrano. (See attached file: test.xml) test.xml Description: Binary data
Simple flow exception
Hello, I seem to have a problem with one of my flows, it's processing all the Compute Nodes and everything else just fine, but it's failing when it's outputting the message to it's OutputNode. The flow has one MQInput node going into a trycatch node which has 2 compute nodes that in turn go to the output node. I'm using a DestinationList Destination Mode which I'm setting in ESQL with using this properties: SET OutputLocalEnvironment.Destination.MQDestinationList.DestinationData.queueName ='CF.MODBCUSTREQ'; SET OutputLocalEnvironment.Destination.MQDestinationList.DestinationData.queueManagerName= 'CD.MQ.CF.DEV'; When it's about to put the message in the output Q it fails with this exception: ( (0x100)RecoverableException = ( (0x300)File= 'build/S210_P/src/DataFlowEngine/ImbMqOutputNode.cpp' (0x300)Line= 715 (0x300)Function= 'mbMqOutputNode::evaluate' (0x300)Type= 'ComIbmMQOutputNode' (0x300)Name= 'f82ff151-f600--0080-9a5867fb3d77' (0x300)Label = 'ModifyBusinessRequest_new_debug_.MQOutput1' (0x300)Text= 'aught exception and rethrowing' (0x300)Catalog = 'WMQIv210' (0x300)Severity= 3 (0x300)Number = 2230 (0x100)ParserException = ( (0x300)File = '/build/S210_P/src/DataFlowEngine/ImbRootParser.cpp' (0x300)Line = 261 (0x300)Function = 'ImbRootParser::refreshBitStreamFromElements' (0x300)Type = 'ComIbmMQInputNode' (0x300)Name = '3594f051-f600--0080-9a5867fb3d77' (0x300)Label= 'ModifyBusinessRequest_new_debug_.MQInput1' (0x300)Text = 'Invalid parser sequence' (0x300)Catalog = 'WMQIv210' (0x300)Severity = 2 (0x300)Number = 6062 (0x100)Insert = ( (0x300)Type = 5 (0x300)Text = 'MQHRF2' ) (0x100)Insert = ( (0x300)Type = 5 (0x300)Text = 'xml' ) ) ) ) If I dont use the trycatch node the error message goes to the error log of mqsi but still cannot complete the message flow. I am ataching a file with an xml sample message. The enviroment is AIX 4.3.3, MQSI 2.1 CSD05, MQSeries 5.3 with latest CSD. Thank you, Yonny Serrano. (See attached file: test.xml) test.xml Description: Binary data
Re: OpenCursosrLimit
Problem solved, we are using passthru instead of eval. Yonny. Yonny Serrano/GBM 24/06/2003 12:41 To p.m. MQSeries List <[EMAIL PROTECTED]> cc Subject OpenCursosrLimit Hello, is there any known issue about reaching de OpenCursorsLimit of an oracle database with the Merant driver that comes with MQSI 2.1? The only solution that we have right now is to eliminate the database nodes of the flow and use an adapter (something like a C program) to make the updates on the database. Is there any other option. Thanks Yonny Serrano Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
MQSI 2.1 Exception
Hello, I'm catching this exception in an Input Node:It might be something simple, but Im a little lost. Any ideas will be apreciated. ( (0x100)RecoverableException = ( (0x300)File = '/build/S210_P/src/DataFlowEngine/ImbMqOutputNo de.cpp' (0x300)Line = 714 (0x300)Function = 'ImbMqOutputNode::evaluate' (0x300)Type = 'ComIbmMQOutputNode' (0x300)Name = 'b05bca72-f400--0080-9a5867fb3d77' (0x300)Label = 'ModifyBusinessRequest.MQOutput' (0x300)Text = 'Caught exception and rethrowing' (0x300)Catalog = 'WMQIv210' (0x300)Severity = 3 (0x300)Number = 2230 (0x100)ParserException = ( (0x300)File = '/build/S210_P/src/DataFlowEngine/ImbRootParser.cpp'wilserramirez1: (0x300)Line = 261 (0x300)Function = 'ImbRootParser::refreshBitStreamFromElements' (0x300)Type = 'ComIbmMQInputNode' (0x300)Name = 'd864ca72-f400--0080-9a5867fb3d77' (0x300)Label = 'ModifyBusinessRequest.MQInput' (0x300)Text = 'Invalid parser sequence' (0x300)Catalog = 'WMQIv210' (0x300)Severity = 2 (0x300)Number = 6062 (0x100)Insert = ( (0x300)Type = 5 (0x300)Text = 'MQHRF2' ) (0x100)Insert = ( (0x300)Type = 5 (0x300)Text = 'xml' ) ) ) ) Yonny.'²ÚîrبÇè®f§j§*.®f¢)à+-²æìr¸©¶*'j·©®âuçbØ^.+-±êïéÞ©T±êìèy«ÚVæÛiÿü0Â[(~×( Ü+ÞÛiÿûæjHpéÚq«1®'¬j·!÷
OpenCursosrLimit
Hello, is there any known issue about reaching de OpenCursorsLimit of an oracle database with the Merant driver that comes with MQSI 2.1? The only solution that we have right now is to eliminate the database nodes of the flow and use an adapter (something like a C program) to make the updates on the database. Is there any other option.ThanksYonny Serrano '²ÚîrبÇè®f§j§*.®f¢)à+-²æìr¸©¶*'j·©®âuçbØ^.+-±êïéÞ©T±êìèy«ÚVæÛiÿü0Â[(~×( Ü+ÞÛiÿûæjHpéÚq«1®'¬j·!÷
Open cursors limit with database node when connecting to Oracle
An MQSI flow that is using database nodes to update an Oracle table. It exceeds the open cursors limit defined in the actual parameters of the database. The limit is 600 and we reach that with about 450 messages. We are using MQSI 2.1 for AIX and DB2 ML U485544AIX 4.3.3, MQSeries 5.3The odbc driver in the AIX box is /usr/opt/wmqi/merant/lib/UKor816.s date Jul 30 2002.Oracle 8.1.6 running over HP-UX B11.00open_cursors 600cursor_sharing EXACTcursor_space_for_time FALSE The flow does two SELECT and one UPDATE and one INSERT.If you need the ESQL code I could post it.Any ideas will be apreciated.Thank You, Yonny."{-®ç-ì~æjv x2¢êæj)b b²Û.nÇ+b¢v«zè¾'^v)í
ââ²Û ®ñêÚK ®Á®×½¨¥i¹^jØm¶ÿà %²írÈb½èm¶ÿ¾f¤§·óIêâzÆ«r¯
StackOverflowError using JMS
Hi, I posted this problem in other forums but havenet got an answer yet. We are getting following error from Java Virtual Machine on AIX box. java.lang.StackOverflowError at java.lang.Throwable.toString(Throwable.java:151) at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java(Compiled Code)) at java.lang.Thread.run(Thread.java:512) Although this error doesn't seem to distrupt any processing or kill java Virtual machine, but it is very annoying and keeps repeating every now and then. Here is brief context about the problem. We are implementing Java MQ JMS adapter which spawns four QueueReceiver ( JMS) for four transaction and processes messages in separate worker threads. Initailly in main Adapter Java class , we create these QueueReceiver and assign MessageListener to them. We have tested 100 transactions for each receiver ( 4* 100 = 400 transactions) successfully. But we get the above error. We are running MQ 5.3 with the second CSD and ma88 over AIX. Any insight in this problem will be greatly appreciated Yonny Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: coredump when trying mqsicreatebroker
Thank you Derrick, the problem was solved with your recomendation. Regards, Yonny Serrano Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
coredump when trying mqsicreatebroker
Hi, I'm getting this error when I tried to create a new brokerwith NEW DB2 database and a NEW queue managerThe queue manager is created. However, the necessary tables are notcreated.[EMAIL PROTECTED]> mqsicreatebroker CUST_REQ_BRK -i db2inst1 _;-a db2 -qCUST_REQ_QM -n MQSICDBR -u db2inst>WebSphere MQ queue manager created.Creating or replacing default objects for CUST_REQ_QM.Default objects statistics : 31 created. 0 replaced. 0 failed.Completing setup.Setup completed.WebSphere MQ queue manager 'CUST_REQ_QM' started.The setmqaut command completed successfully.The setmqaut command completed successfully.The setmqaut command completed successfully.The setmqaut command completed successfully.The setmqaut command completed successfully.The setmqaut command completed successfully.The setmqaut command completed successfully.The setmqaut command completed successfully.IOT/Abort trap(coredump) The system is: AIX 4.3.3, ML 9, MQSI 2.1, DB2 for AIX 7.2.Thank you,Yonny Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Setting user aut for a client-Server-Cluster configuration
Yes, mquser is defined there. And I gave him permissions (in that box) with: setmqaut -m QMGR3 -t qmgr -p mquser +allmqi setmqaut -m QMGR3 -t q -n Q2 -p mquser +allmq Yonny Serrano To: MQSeries List <[EMAIL PROTECTED]> 06/03/2003 cc: 07:44 p.m. Subject: Setting user aut for a client-Server-Cluster configuration Hi, I have the following configuration: Win 2K MQ Client Win2K MQ Server 2 AIX MQ Servers (Cluster Full Repositories) QMGR1 QMGR2 & QMGR3 The qmgrs belongs to a cluster. I have a server connecton channel between the Win 2K boxes (the MCAUSER in the svrconn channel is blank). In the client box I have an application running with a userid "mquser". I have one queue (Q1) defined in QMGR1 (shared in a cluster), I set the permissions to allow mquser to get messages from that queue, I also granted mquser to connect to the QMGR1. This configuration worked fine and my application is able to get messages from Q1. There are two more queues: Q2 that is defined twice (once for each qmgr QMGR2 and QMGR3) and they shared in a cluster. I want to know wich permissions do i have to set to allow the client application to put messages in each instance of Q2. The user "mquser" is defined in the 3 server boxes (Win and AIX), the I tried with the following commands: AIX BOX 1: setmqaut -m QMGR2 -t qmgr -p mquser +allmqi setmqaut -m QMGR2 -t q -n Q2 -p mquser +allmqi AIX BOX 2: setmqaut -m QMGR3 -t qmgr -p mquser +allmqi setmqaut -m QMGR3 -t q -n Q2 -p mquser +allmq WIN 2K MQ Server: setmqaut -m QMGR1 -t qmgr -p mquser +connect However, Im still not able to put messages from the client application to Q2. Thank you for any help, Yonny. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Setting user aut for a client-Server-Cluster configuration
Hi, I have the following configuration: Win 2K MQ Client Win2K MQ Server 2 AIX MQ Servers (Cluster Full Repositories) QMGR1 QMGR2 & QMGR3 The qmgrs belongs to a cluster. I have a server connecton channel between the Win 2K boxes (the MCAUSER in the svrconn channel is blank). In the client box I have an application running with a userid "mquser". I have one queue (Q1) defined in QMGR1 (shared in a cluster), I set the permissions to allow mquser to get messages from that queue, I also granted mquser to connect to the QMGR1. This configuration worked fine and my application is able to get messages from Q1. There are two more queues: Q2 that is defined twice (once for each qmgr QMGR2 and QMGR3) and they shared in a cluster. I want to know wich permissions do i have to set to allow the client application to put messages in each instance of Q2. The user "mquser" is defined in the 3 server boxes (Win and AIX), the I tried with the following commands: AIX BOX 1: setmqaut -m QMGR2 -t qmgr -p mquser +allmqi setmqaut -m QMGR2 -t q -n Q2 -p mquser +allmqi AIX BOX 2: setmqaut -m QMGR3 -t qmgr -p mquser +allmqi setmqaut -m QMGR3 -t q -n Q2 -p mquser +allmq WIN 2K MQ Server: setmqaut -m QMGR1 -t qmgr -p mquser +connect However, Im still not able to put messages from the client application to Q2. Thank you for any help, Yonny. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: MS0G, against a 5.1 QMGR
I'm getting 2195 when I run dumprepos against my remote repo qmgr. dumprepos MYQM -h x.x.x.x -p 1416 -C 850 I know that dumprepos is well conected to the qmgr because if I change the qmgr name, the port numbre or the ip address I get 2058. -C 850 is because without it I get Unssuported Encoding Exception Cp850. The CCSID of the repo qmgr is 819. Any ideas will be apreciated. Another doubt: Is there any document that explains the output of amqrfdm? Yonny R. Serrano Tony_Devitt@CG U.COM.AU To: [EMAIL PROTECTED] Sent by: cc: MQSERIES@AKH-W Subject: Re: MS0G, against a 5.1 QMGR ien.AC.AT 16/10/2002 08:42 p.m. Please respond to MQSERIES ** Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ** : Yonny, You should not have any problems working with MS0G in the environment you have describedits just a matter of downloading and installing. I would recommend that you experiment with 2-3 test QMs in a cluster to see how you can use the utilities and what they do. You might also find the 'amqrfdm' utility useful (usage: amqrfdm -m qmgrname). : The information transmitted in this message and attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of CGU Insurance. This message has been scanned for viruses and cleared by MailMarshal. : Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: AW: AW: AW: QMGR cannot join a cluster, SYSTEM.TEMPQMGR[conname] inst ead of Rep QMGR
Stefan, Follows an explanation about QMPROENG and QMTRACE. I have normal sender and reciever channels between MQSI2 and QMPROENG, in fact I had to define remote queues and xmit queues to implement a temporary solution that allow applications to return to production. I had not done any more changes on QMPROENG since monday. The two repositories of the cluster are MQSI1 and MQSI2. IBM asked me for a trace (of the join cluster procedure) so I didnt try to rejoin QMPROENG and created a new (test) qmgr QMTRACE, generated the trace and sent it to IBM. There are no clues in the log files, and we dont have security exits. Yonny R. Serrano Stefan.Raabe@D REGIS.COMTo: [EMAIL PROTECTED] Sent by: cc: MQSERIES@AKH-W Subject: AW: AW: AW: QMGR cannot join a cluster, ien.AC.AT SYSTEM.TEMPQMGR[conname] inst ead of Rep QMGR 17/10/2002 04:23 a.m. Please respond to MQSERIES mhhh, i do not find any configuration mistakes or typing-errors... so... what now. what i would do is to define normal sender / receiver channel between MQTRACE and MQSI2 (both directions) to make sure that the connection itself is working. it still looks like a communication problem to me. do you use any security exits? what about the QMPROENG QMGR? i do not find any reference to that one in the definitions. you said, that QMPROENG is twice within the cluster. an "old" and a "new" one, is that correct? the log you posted below showing the 2059 errors related to QMPROENG, is this log from MQTRACE? is QMPROENG a repository queuemanager? if so, maybe MQTRACE also tries to connect to QMPROENG but finds an old definition and can not connect... but this is only a guess if the 2059 errors occur on MQTRACE and QMPROENG is a cluster qmgr, try to define the TO.QMPROENG cluster sender channel on MQTRACE explicit. are there messages in the system.cluster.transmit.queue on MQTRACE? do a refresh cluster(MQENG1) on MQTRACE, do the messagenumber increase or does the TO.MQSI2 channel starts and the messages get transmitted? is there another repository queuemanager except MQSI2 (and except of QMPROENG in case this one is a repository qmgr)? if so, define a clustersender TO.XXX to this one and retry to connect to the cluster. this is all fiddeling around with mq, no clue what it may be right now. i am running out of hints :D, maybe you should check all the amq logs on all participating queuemanagers again for error messages. you should also consider to update the repository to a higher level of mqseries. good luck stefan -Ursprungliche Nachricht- Von: Yonny Serrano [mailto:YSerrano@;GBM.NET] Gesendet: Mittwoch, 16. Oktober 2002 21:06 An: [EMAIL PROTECTED] Betreff: Re: AW: AW: QMGR cannot join a cluster, SYSTEM.TEMPQMGR[conname] inst ead of Rep QMGR Stefan, the information that you ask for INETD.CONF QM_MQSI2 stream tcp nowait mqm /usr/lpp/mqm/bin/amqcrsta amqcrsta -m MQSI2 QM_QMAS2 stream tcp nowait mqm /usr/lpp/mqm/bin/amqcrsta amqcrsta -m QMAS2 SERVICES QM_MQSI2 1416/tcp QM_QMAS2 1417/tcp This information above is only for one of the repositories. Notice that there are two queue managers on that box, the repo qmgr and a qmgr that we use for some MQSI rulengines. The information below is for the Repo qmgr and the Win Qmgr that Im trying to add. The repo qmgr is working and the channel initiator too, the cluster ENG1 is also working with about 8 qmgrs (including the repo qmgrs). I tail the system objects information and the information about some qmgrs that are working in the cluster. Thanks again. 1 : display qmgr all AMQ8408: Display Queue Manager details. DESCR( )DEADQ(SYSTEM.DEAD.LETTER.QUEUE) DEFXMITQ( ) CHADEXIT( ) CLWLEXIT( ) CLWLDATA( ) REPOS(ENG1) REPOSNL( ) COMMANDQ(SYSTEM.ADMIN.COMMAND.QUEUE)QMNAME(MQSI2) CRDATE(2001-08-01) CRTIME(17.51.39) ALTDATE(2001-08-02) ALTTIME(12.40.47) QMID(MQSI2_2001-08-01_17.51.39) TRIGINT(9) MAXHANDS(256) MAXUMSGS(1) AUTHOREV(DISABLED) INHIBTEV(DISABLED) LOCALEV(DISABLED) REMOTEEV(DISABLED) PERFMEV(DISABLED) STRSTPEV(ENABLED) CHAD(DISABLED) CHADEV(DISABLED) CLWLLEN(100)MAXMSGL(4194304) CCSID(819) MAXPRTY(9) CMDLEVEL(510) PLATFORM(UNIX) SYNCPT DISTL(YES) 2 : display clusqmgr(*) all AMQ8441: Display Cluster Queue Manager details. CLUSQMGR(MQSI1)
MS0G, against a 5.1 QMGR
Is it posible to use the support pack MS0G (running over Win 2K) to get a dump of a full repository qmgr running MQSeries for AIX 5.1 (CSD 04) ? Can I use the last version of ma88 to do it? If YES, are there any recomendations to do it? if NO, how can I manipulate the information in a full repository?, is there any other tool that I can use? Thank you, Yonny Serrano Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: AW: AW: QMGR cannot join a cluster, SYSTEM.TEMPQMGR[conname] inst ead of Rep QMGR
) CONVERT(NO) SCYDATA( ) MCATYPE(THREAD) CONNAME(130.1.14.189(1414)) MREXIT( ) MRDATA( ) MRRTY(10) MRTMR(1000) HBINT(300) BATCHINT(0) NPMSPEED(FAST) MCAUSER( ) CLUSTER(ENG1) CLUSNL( ) NETPRTY(0) ALTDATE(2002-10-15) ALTTIME(20.12.06) MSGEXIT( ) SENDEXIT( ) RCVEXIT( ) MSGDATA( ) SENDDATA( ) RCVDATA( ) 4 MQSC commands read. No commands have a syntax error. One valid MQSC command could not be processed. Stefan.Raabe@D REGIS.COMTo: [EMAIL PROTECTED] Sent by: cc: MQSERIES@AKH-W Subject: AW: AW: QMGR cannot join a cluster, ien.AC.AT SYSTEM.TEMPQMGR[conname] inst ead of Rep QMGR 16/10/2002 03:03 a.m. Please respond to MQSERIES Hi, clustering works by queuemanager-id not by queuemanager-name. if a qmgr is created it will be given a qmgr-id (qmgrname, date, time) which is used to identify the queuemanager within the mqseries cluster. if you purge that queuemanager (or if it is gone because of machine failures, disk crashes,) and create a new one with the same name the qmgr-id will differ. in that case you will see the queuemanager twice in the repository, and you will also see the cluster queues twice. but this should not prevent the new (or any other) queuemanager to join the cluster. you can force the "old" queuemanager out of the cluster before the new one joins, because with version 5.2 or lower you can only force by qmgrname, not by id (this hase been changed with version 5.3). before you do all that work collecting display-outputs make sure that you can ping the explicit defined cluster sender channel from the joining qmgr to the repository qmgr and that you can ping the implicit defined cluster sender channel from the repository qmgr to the joining qmgr. make also sure you did not miss any error messages in the various amqerrxx.log files (var/mqm/errors var/mqm/qmgrs/@system/errors var/mqm/qmgrs/yourqmgrname/errors) or fdc files that may indicate an error. make sure the repository manager is working on the aix box (i do not know the process name right now, but you can check whether the system.cluster.command queue is open for input). check that the channel initiator is running on the aix box (dont know the process name too, but check if system.channel.initq is open for input) at least, it still can be a software bug. mq 5.1 for the aix machine is somehow outdated. I would recommend to use at least 5.2 because there have been a lot of changes and bugfixes to clustering. good luck.. regards stefan -Ursprungliche Nachricht- Von: Yonny Serrano [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 15. Oktober 2002 18:33 An: [EMAIL PROTECTED] Betreff: Re: AW: QMGR cannot join a cluster, SYSTEM.TEMPQMGR[conname] instead of Rep QMGR Sorry, my previous note was incomplete. The two full repositories qmgrs are running on separate aix boxes. The qmgr that Im trying to join is on a Win2K machine. That is the QMPROENG qmgr that you saw in the log files. QMPROENG was previously attached to the cluster but the customer had to reinstall everything on the Win2K machine (even the operating system) because of a low performance issue of some applications. The problem started when we redefined the qmgr QMPROENG and tried to rejoin it to the cluster. It seems that the repositories qmgrs have information about the original QMPROENG qmgr and do not recognize the new QMPROENG. But, there is a weird behaviour of the cluster: I am unable to add any other queue manager to the cluser, even with a completly different name in a different machine. I always see (on the new qmgrs) the repositories as SYSTEM.TEMPQMGR[conname] with the suspend attribute on YES. Because there was a production application down, I had to set up mqseries communication with sender and reciever channels, remote queues and transmition queues as a temporary solution. I need now to found a better solution for the problem. I'll try, today's afternoon, to join a new qmgr to the cluster. I'll send you then the information that you required (inet.conf, services, qmgrs, channels, clusqmgrs, etc). Any ideas will be apreciated, thank you, Yonny R. Serrano Stefan.Raabe@D REGIS.COMTo: [EMAIL PROTECTED] Sent by: cc: MQSERIES@AKH-W Subject: AW: QMGR cannot join a cluster, SYSTEM.TEMPQMGR[conname] ien.AC.AT instead of Rep QMGR
Re: AW: QMGR cannot join a cluster, SYSTEM.TEMPQMGR[conname] instead of Rep QMGR
Hello, The two full repositories qmgrs are running on separate aix boxes. The qmgr that Im trying to join is on a Win2K machine. This is the QMPROENG qmgr that you saw in the log files. QMPROENG was previously attached to the cluster but the customer had to reinstall everything on the Win2K machine (even the operating system) because of a low performance issue of some applications. The problem started when we redefined the qmgr QMPROENG and tried to rejoin it to the cluster. It seems that the repositories qmgrs have information about the original QMPROENG qmgr and do not recognize the new QMPROENG. But, there is a Stefan.Raabe@D REGIS.COMTo: [EMAIL PROTECTED] Sent by: cc: MQSERIES@AKH-W Subject: AW: QMGR cannot join a cluster, SYSTEM.TEMPQMGR[conname] ien.AC.AT instead of Rep QMGR 15/10/2002 03:18 a.m. Please respond to MQSERIES Hello, from my experience, the system.tempqmgr occured when - the queuemanager that tried to join the cluster was not able to connect to the repository queuemanager or - the repository queuemanager is not able to send an answer to the connecting queuemanager to resolve that name. this may be because of network issues or because of a mismatch in the definitions. use a ping channel for both directions to make sure its not the communication itself make sure that you specified the correct ip addresses and ports in the proper channel definitions one guess do you use the inetd to handle incoming regests? maybe you got the wrong queuemanagername in the inetd.conf, so the inetd starts the mca but the mca can not connect to the queuemanager because the name is not correct (this may be the 2059 error you showed us in the log). if all that seems to be okay, please show for every machine: - ip address and qmgr name - /etc/services and /etc/inetd.conf (mqseries entries only, i do not want to spy on your machine) :-) - display qmgr all - display clusqmgr(*) all - display channel all hth stefan -Ursprungliche Nachricht- Von: Yonny Serrano [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 14. Oktober 2002 22:04 An: [EMAIL PROTECTED] Betreff: Re: QMGR cannot join a cluster, SYSTEM.TEMPQMGR[conname] instead of Rep QMGR The error log that I sent you is from de local installation (@system/errors) where the queue manager QMPROENG is defined. QMPROENG is the local queue manager. I displayed the atributes for the SYSTEM.TEMPQMGR, it appears as a suspend queue manager. The following command was execute in the local queue manager QMPROENG, the one that I cannot join to the cluster. You could see also that the channel is running. Let me know what you think about it, thank you again. YS. dis clusqmgr(system*) all 2 : dis clusqmgr(system*) all AMQ8441: Display Cluster Queue Manager details. CLUSQMGR(SYSTEM.TEMPQMGR.130.1.9.205(1416)) CLUSTER(ENG1) CHANNEL(TO.MQSI2) CONNAME(130.1.9.205(1416)) QMID(SYSTEM.TEMPUUID.130.1.9.205(1416)) DESCR( )CLUSTIME(15.39.59) CLUSDATE(2002-10-14)ALTTIME(15.39.59) ALTDATE(2002-10-14) TRPTYPE(TCP) DEFTYPE(CLUSSDR)QMTYPE(REPOS) MCANAME( ) MODENAME( ) TPNAME( ) BATCHSZ(50) DISCINT(6000) SHORTRTY(10) SHORTTMR(60)LONGRTY(9) LONGTMR(1200) SCYEXIT( ) SCYDATA( ) SEQWRAP(9) MAXMSGL(4194304)CONVERT(NO) USERID( ) PASSWORD( ) MCAUSER( ) MCATYPE(THREAD) HBINT(300) BATCHINT(0) NPMSPEED(FAST) NETPRTY(0) SUSPEND(YES)STATUS(RUNNING) SSLCIPH( ) SSLCAUTH(REQUIRED) BATCHHB(0) LOCLADDR( ) ALTTIME( ) ALTDATE( ) SSLPEER() SENDEXIT( ) SENDDATA( ) MSGEXIT( ) MSGDATA( ) RCVEXIT( ) RCVDATA( ) adiraju.s.rao@ AEXP.COM To: [EMAIL PROTECTED] Sent by: cc: MQSERIES@AKH-W Subject: Re: QMGR cannot join a cluster, SYSTEM.TEMPQMGR[conname] ien.AC.AT instead of Rep QMGR 14/10/2002 01:59 p.m. Please respond to MQSERIES Hi Yonny, >From the error logs i can see that the remote queue manager is not started for some reason. Make sure that the Queue mana
Re: QMGR cannot join a cluster, SYSTEM.TEMPQMGR[conname] instead of Rep QMGR
The error log that I sent you is from de local installation (@system/errors) where the queue manager QMPROENG is defined. QMPROENG is the local queue manager. I displayed the atributes for the SYSTEM.TEMPQMGR, it appears as a suspend queue manager. The following command was execute in the local queue manager QMPROENG, the one that I cannot join to the cluster. You could see also that the channel is running. Let me know what you think about it, thank you again. YS. dis clusqmgr(system*) all 2 : dis clusqmgr(system*) all AMQ8441: Display Cluster Queue Manager details. CLUSQMGR(SYSTEM.TEMPQMGR.130.1.9.205(1416)) CLUSTER(ENG1) CHANNEL(TO.MQSI2) CONNAME(130.1.9.205(1416)) QMID(SYSTEM.TEMPUUID.130.1.9.205(1416)) DESCR( )CLUSTIME(15.39.59) CLUSDATE(2002-10-14)ALTTIME(15.39.59) ALTDATE(2002-10-14) TRPTYPE(TCP) DEFTYPE(CLUSSDR)QMTYPE(REPOS) MCANAME( ) MODENAME( ) TPNAME( ) BATCHSZ(50) DISCINT(6000) SHORTRTY(10) SHORTTMR(60)LONGRTY(9) LONGTMR(1200) SCYEXIT( ) SCYDATA( ) SEQWRAP(9) MAXMSGL(4194304)CONVERT(NO) USERID( ) PASSWORD( ) MCAUSER( ) MCATYPE(THREAD) HBINT(300) BATCHINT(0) NPMSPEED(FAST) NETPRTY(0) SUSPEND(YES)STATUS(RUNNING) SSLCIPH( ) SSLCAUTH(REQUIRED) BATCHHB(0) LOCLADDR( ) ALTTIME( ) ALTDATE( ) SSLPEER() SENDEXIT( ) SENDDATA( ) MSGEXIT( ) MSGDATA( ) RCVEXIT( ) RCVDATA( ) adiraju.s.rao@ AEXP.COM To: [EMAIL PROTECTED] Sent by: cc: MQSERIES@AKH-W Subject: Re: QMGR cannot join a cluster, SYSTEM.TEMPQMGR[conname] ien.AC.AT instead of Rep QMGR 14/10/2002 01:59 p.m. Please respond to MQSERIES Hi Yonny, >From the error logs i can see that the remote queue manager is not started for some reason. Make sure that the Queue manager QMPROENG is available or not. One more way to test is by pinging the channel. First stop the channel TO.QMPROENG channel and try to ping and note the errors, you will get some kinda message basically the result of the ping channel command. This should give you a closest reason for why its failing. If it fails due to tcp/ip error make sure that remote queue manager is running on the right port and if is says remote queue manager is unavailable, try starting the QM. Let me know how it goes. Adi From: "Yonny Serrano" <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on 10/14/2002 01:22 PM AST Please respond to "MQSeries List" <[EMAIL PROTECTED]> Sent by:"MQSeries List" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject:Re: QMGR cannot join a cluster, SYSTEM.TEMPQMGR[conname] instead of Rep QMGR Hello Adi, thanks for your response, Attached is a fragment of the file \@SYSTEM\errors\AMQERR01.LOG. I am able to start the cluster sender channels on both ends (Repo qmgr and new qmgr), and I see them running. What else do I have to check about the network configuration? Could it be caused for corrupt data in the repositories queues of the repo qmgrs? I did (yesterday) a reset cluster for the new queue manager and I also tried to Refresh the cluster on both sides. Yonny R. Serrano 10/13/2002 21:32:28 AMQ9508: Program cannot connect to the queue manager. EXPLANATION: The connection attempt to queue manager 'QMPROENG' failed with reason code 2059. ACTION: Ensure that the queue manager is available and operational. --- 10/13/2002 21:32:28 AMQ: Channel program ended abnormally. EXPLANATION: Channel program 'TO.QMPROENG1' ended abnormally. ACTION: Look at previous error messages for channel program 'TO.QMPROENG1' in the error files to determine the cause of the failure. --- 10/13/2002 21:32:54 AMQ9508: Program cannot connect to the queue manager. EXPLANATION: The connection attempt to queue manager 'QMPROENG' failed with reason code 2059. ACTION: Ensure that the queue manager is available and operational. --- 10/13/2002 21:32:54 AMQ: Channel program ended abnormally. EXPLANA
Re: QMGR cannot join a cluster, SYSTEM.TEMPQMGR[conname] instead of Rep QMGR
Hello Adi, thanks for your response, Attached is a fragment of the file \@SYSTEM\errors\AMQERR01.LOG. I am able to start the cluster sender channels on both ends (Repo qmgr and new qmgr), and I see them running. What else do I have to check about the network configuration? Could it be caused for corrupt data in the repositories queues of the repo qmgrs? I did (yesterday) a reset cluster for the new queue manager and I also tried to Refresh the cluster on both sides. Yonny R. Serrano 10/13/2002 21:32:28 AMQ9508: Program cannot connect to the queue manager. EXPLANATION: The connection attempt to queue manager 'QMPROENG' failed with reason code 2059. ACTION: Ensure that the queue manager is available and operational. --- 10/13/2002 21:32:28 AMQ: Channel program ended abnormally. EXPLANATION: Channel program 'TO.QMPROENG1' ended abnormally. ACTION: Look at previous error messages for channel program 'TO.QMPROENG1' in the error files to determine the cause of the failure. --- 10/13/2002 21:32:54 AMQ9508: Program cannot connect to the queue manager. EXPLANATION: The connection attempt to queue manager 'QMPROENG' failed with reason code 2059. ACTION: Ensure that the queue manager is available and operational. --- 10/13/2002 21:32:54 AMQ: Channel program ended abnormally. EXPLANATION: Channel program 'TO.QMPROENG1' ended abnormally. ACTION: Look at previous error messages for channel program 'TO.QMPROENG1' in the error files to determine the cause of the failure. --- 10/13/2002 21:33:29 AMQ9508: Program cannot connect to the queue manager. EXPLANATION: The connection attempt to queue manager 'QMPROENG' failed with reason code 2059. ACTION: Ensure that the queue manager is available and operational. --- 10/13/2002 21:33:29 AMQ: Channel program ended abnormally. EXPLANATION: Channel program 'TO.QMPROENG1' ended abnormally. ACTION: Look at previous error messages for channel program 'TO.QMPROENG1' in the error files to determine the cause of the failure. --- adiraju.s.rao@ AEXP.COM To: [EMAIL PROTECTED] Sent by: cc: MQSERIES@AKH-W Subject: Re: QMGR cannot join a cluster, SYSTEM.TEMPQMGR[conname] ien.AC.AT instead of Rep QMGR 14/10/2002 11:45 a.m. Please respond to MQSERIES Hi Yonny, Couple of things to check here. Check the log files of the queue manager where you are seeing the SYSTEM.TEMPQMGR and also see the system log files i.e qmgrs\@SYSTEM\errors\AMQERR01.LOG file. You might get some clue. This TEMPQMGR appears when there is some problem in clustering, mostly a network issue. Make sure you have communication is open both from and to the queue manager where you are getting the errors. Hope this helps. Adi From: "Yonny Serrano" <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on 10/14/2002 09:30 AM AST Please respond to "MQSeries List" <[EMAIL PROTECTED]> Sent by:"MQSeries List" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject:QMGR cannot join a cluster, SYSTEM.TEMPQMGR[conname] instead of Rep QMGR Hello, I have a cluster where the repositories queue managers are MQSeries 5.1 for AIX with the last CSD. When tried to join a QM (MQSeries for Win2K 5.2.1 with last CSD) I found that the repositories queue managers appear as SYSTEM.TEMPQMGR[connaname]. I am unable to put messages on remote cluster queues from the new queue manager, mq returns 2085, I also got this reason code when trying to put messages from the Repo qmgrs to cluster queues on the new queue manager. The cluster is working fine with other qmgrs but don't accept new ones. Refresh cluster did not work, Reset the new queue manager from the repositories and trying to reconnect it again did not work either. The following are error messages found on the new qmgr log. Thanks a lot for your help. Yonny R. Serrano 10/13/2002 20:54:47 AMQ9419: No cluster-receiver channels for cluster 'ENG1' EXPLANATION: The repository manager has received information about a cluster for which no cluster-receiver channels are known. ACTION: Define cluster-receiver channels for the cluster on the local queue manager. ---
Re: QMGR cannot join a cluster, SYSTEM.TEMPQMGR[conname] instead of Rep QMGR
The channel definitions are ok. In fact the channels are running, to and from the repository qmgr. I also tried to define a second cluster reciever in the new qmgr, cause I read that someone solved a similiar problem doing that. It didnt work for me. Yonny R. Serrano jvkemenade@CRE SSIDA.INFO To: [EMAIL PROTECTED] Sent by: cc: MQSERIES@AKH-W Subject: Re: QMGR cannot join a cluster, SYSTEM.TEMPQMGR[conname] ien.AC.AT instead of Rep QMGR 14/10/2002 11:09 a.m. Please respond to MQSERIES Hi, You better verify if your cluster receiver and cluster sender channels are defined correctly. Perhaps there's a typo somewhere I have seen the TEMPQMGR appear when there was a mismatch in definitions. Cheers, Jan. > Hello, I have a cluster where the repositories queue managers are MQSeries > 5.1 for AIX with the last CSD. When tried to join a QM (MQSeries for Win2K > 5.2.1 with last CSD) I found that the repositories queue managers appear as > SYSTEM.TEMPQMGR[connaname]. I am unable to put messages on remote cluster > queues from the new queue manager, mq returns 2085, I also got this reason > code when trying to put messages from the Repo qmgrs to cluster queues on > the new queue manager. > > The cluster is working fine with other qmgrs but don't accept new ones. > > Refresh cluster did not work, Reset the new queue manager from the > repositories and trying to reconnect it again did not work either. > > The following are error messages found on the new qmgr log. Thanks a lot > for your help. > > Yonny R. Serrano > > > > 10/13/2002 20:54:47 > AMQ9419: No cluster-receiver channels for cluster 'ENG1' > > EXPLANATION: > The repository manager has received information about a cluster for which > no > cluster-receiver channels are known. > ACTION: > Define cluster-receiver channels for the cluster on the local queue > manager. > -- - > 10/13/2002 20:54:47 > AMQ9419: No cluster-receiver channels for cluster 'ENG1' > > EXPLANATION: > The repository manager has received information about a cluster for which > no > cluster-receiver channels are known. > ACTION: > Define cluster-receiver channels for the cluster on the local queue > manager. > -- - > 10/13/2002 20:54:47 > AMQ9442: Refresh Cluster command processed. > > EXPLANATION: > The Refresh Cluster(ENG1) command caused 11 objects to be refreshed and 2 > objects to be republished. > ACTION: > None. > > ... > > -- - > 10/13/2002 21:40:56 > AMQ9519: Channel 'TO.QMPROENG1' not found. > > EXPLANATION: > The requested operation failed because the program could not find a > definition > of channel 'TO.QMPROENG1'. > ACTION: > Check that the name is specified correctly and the channel definition is > available. > -- - > 10/13/2002 21:40:56 > AMQ: Channel program ended abnormally. > > EXPLANATION: > Channel program 'TO.QMPROENG1' ended abnormally. > ACTION: > Look at previous error messages for channel program 'TO.QMPROENG1' in the > error > files to determine the cause of the failure. > -- - > 10/13/2002 21:41:47 > AMQ9420: No repositories for cluster ENG1. > > EXPLANATION: > The queue manager has received information about a cluster for which no > repositories are known. > ACTION: > Alter the REPOS or REPOSNL attribute of the queue manager, that is to have > a > full repository for the cluster, to specify the cluster name. > -- - > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > > -/ /&Jan van Kemenade \&www.cressida.info -\ Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
QMGR cannot join a cluster, SYSTEM.TEMPQMGR[conname] instead of Rep QMGR
Hello, I have a cluster where the repositories queue managers are MQSeries 5.1 for AIX with the last CSD. When tried to join a QM (MQSeries for Win2K 5.2.1 with last CSD) I found that the repositories queue managers appear as SYSTEM.TEMPQMGR[connaname]. I am unable to put messages on remote cluster queues from the new queue manager, mq returns 2085, I also got this reason code when trying to put messages from the Repo qmgrs to cluster queues on the new queue manager. The cluster is working fine with other qmgrs but don't accept new ones. Refresh cluster did not work, Reset the new queue manager from the repositories and trying to reconnect it again did not work either. The following are error messages found on the new qmgr log. Thanks a lot for your help. Yonny R. Serrano 10/13/2002 20:54:47 AMQ9419: No cluster-receiver channels for cluster 'ENG1' EXPLANATION: The repository manager has received information about a cluster for which no cluster-receiver channels are known. ACTION: Define cluster-receiver channels for the cluster on the local queue manager. --- 10/13/2002 20:54:47 AMQ9419: No cluster-receiver channels for cluster 'ENG1' EXPLANATION: The repository manager has received information about a cluster for which no cluster-receiver channels are known. ACTION: Define cluster-receiver channels for the cluster on the local queue manager. --- 10/13/2002 20:54:47 AMQ9442: Refresh Cluster command processed. EXPLANATION: The Refresh Cluster(ENG1) command caused 11 objects to be refreshed and 2 objects to be republished. ACTION: None. ... --- 10/13/2002 21:40:56 AMQ9519: Channel 'TO.QMPROENG1' not found. EXPLANATION: The requested operation failed because the program could not find a definition of channel 'TO.QMPROENG1'. ACTION: Check that the name is specified correctly and the channel definition is available. --- 10/13/2002 21:40:56 AMQ: Channel program ended abnormally. EXPLANATION: Channel program 'TO.QMPROENG1' ended abnormally. ACTION: Look at previous error messages for channel program 'TO.QMPROENG1' in the error files to determine the cause of the failure. --- 10/13/2002 21:41:47 AMQ9420: No repositories for cluster ENG1. EXPLANATION: The queue manager has received information about a cluster for which no repositories are known. ACTION: Alter the REPOS or REPOSNL attribute of the queue manager, that is to have a full repository for the cluster, to specify the cluster name. --- Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Incomprehensible reason value in dead letter queue messages
Hello, this is the last message () in the dead.letter.queue of an AIX cluster queue manager. I really dont understand the meaning of the reason code X'0001. I spent yesterday's afternoon trying to solve why these messages are going to the dead letter queue. I hope that you could give some help. Regards, Yonny R. Serrano MQGET of message number 48 Message descriptor StrucId : 'MD ' Version : 2 Report : 0 MsgType : 8 Expiry : -1 Feedback : 0 Encoding : 273 CodedCharSetId : 819 Format : 'MQDEAD ' Priority : 0 Persistence : 0 MsgId : X'C1D4D840D8D44BC2E3C3C1E2F0F0F2403D85AC9C004A7012' CorrelId : X'' BackoutCount : 0 ReplyToQ : '' ReplyToQMgr: 'QM.BTCAS002 ' ** Identity Context UserIdentifier : 'jcarlos ' AccountingToken : X'0F404040404040404040404040404048' ApplIdentityData : '' ** Origin Context PutApplType: '8' PutApplName: 'MQS_01JCARLOS 278037 ' PutDate : '20020919'PutTime : '18410538' ApplOriginData : '' GroupId : X'' MsgSeqNumber : '1' Offset : '0' MsgFlags : '0' OriginalLength : '-1' Message length - 1351 bytes : 444C 4820 0001 0001 5143 2E42 'DLH QC.B' 0010: 4E43 4149 3030 312E 3031 3020 2020 2020 'NCAI001.010 ' 0020: 2020 2020 2020 2020 2020 2020 2020 2020 '' 0030: 2020 2020 2020 2020 2020 2020 514D 2E42 'QM.B' 0040: 4E43 4149 3030 3220 2020 2020 2020 2020 'NCAI002 ' 0050: 2020 2020 2020 2020 2020 2020 2020 2020 '' 0060: 2020 2020 2020 2020 2020 2020 0111 '' 0070: 0333 4D51 5354 5220 2020 0006 '...3MQSTR ' 0080: 5765 6253 7068 6572 654D 5149 6E74 6567 'WebSphereMQInteg' 0090: 7261 746F 7232 2020 2020 2020 3230 3032 'rator2 2002' 00A0: 3039 3139 3232 3337 3431 3030 504D 4130 '091922374100PMA0' 00B0: 3030 3030 3031 3138 3439 3420 2020 2020 '0118494 ' 00C0: 2020 2020 2030 3031 514C 4254 4330 3031 ' 001QLBTC001' 00D0: 2020 2020 2020 2051 4C50 5338 3030 3120 ' QLPS8001 ' 00E0: 2020 2020 2020 4243 4353 4F46 3131 2020 ' BCCSOF11 ' 00F0: 2020 3230 3032 3039 3139 3138 3431 3035 ' 20020919184105' 0100: 4E41 2020 2020 2020 2020 2020 3435 3630 'NA 4560' 0110: 3434 3132 3035 3130 3138 3237 2020 2020 '441205101827' 0120: 2030 3032 3337 4341 5445 4D50 3230 3031 ' 00237CATEMP2001' 0130: 3033 3239 3230 3032 3039 3138 3230 3032 '0329200209182002' 0140: 3039 3138 2020 2020 2020 2031 3530 302E '0918 1500.' 0150: 3030 2020 2020 2020 2020 2020 202E 3030 '00 .00' 0160: 3531 3031 2053 5453 4354 4530 3120 5354 '5101 STSCTE01 ST' 0170: 5343 5445 4531 3033 3035 2020 2020 2030 'SCTEE10305 0' 0180: 3030 3735 3030 2020 2020 2020 3030 3030 '007500 ' 0190: 3030 2020 2020 2020 2039 3536 392E 3134 '00 9569.14' 01A0: 2020 2020 2020 2020 2020 202E 3030 2020 ' .00 ' 01B0: 2020 2020 2D32 3036 392E 3134 2020 2020 '-2069.14' 01C0: 2020 2020 2020 202E 3030 2020 2030 3030 ' .00 000' 01D0: 3030 3231 3638 3030 3020 2020 2020 2031 '002168000 1' 01E0: 3036 3232 2E32 3920 2020 2020 2020 2020 '0622.29 ' 01F0: 2020 2E30 3020 2020 2020 2020 3935 3639 ' .00 9569' 0200: 2E31 3420 2020 2020 2020 2020 2020 2E30 '.14 .0' 0210: 3020 2020 2020 2031 3039 3934 2E31 3420 '0 10994.14 ' 0220: 2020 2020 2020 2020 2020 2E30 3020 2020 ' .00 ' 0230: 2020 2020 3236 3735 2E36 3820 2020 2020 '2675.68 ' 0240: 2020 2020 2020 2E30 3020 2020 2020 2020 ' .00 ' 0250: 3436 3339 2E39 3220 2020 2020 2020 3436 '4639.92 46' ... Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
