Re: MQClient authorization error (2035)
Rebecca may be on the right track. Check that the NIS account is in an authorised group on the server. I would also ensure that the account number (use the command "id" on both servers) and group numbers are the same on both servers. Regards John. -Original Message- From: Sony Varghese [mailto:[EMAIL PROTECTED] Sent: 02 June 2003 15:51 To: [EMAIL PROTECTED] Subject: Re: MQClient authorization error (2035) Hi John, My userid is a NIS userid id .. The MCAUSER is set to blank .. Regards Sony -Original Message- From: John Scott [mailto:[EMAIL PROTECTED] Sent: 02 June 2003 17:18 To: [EMAIL PROTECTED] Subject: Re: MQClient authorization error (2035) Are you logging on using a different user name from the client? What is the MCAUSER set to for the server connection channel the client is using? Regards John. -Original Message- From: Sony Varghese [mailto:[EMAIL PROTECTED] Sent: 02 June 2003 14:58 To: [EMAIL PROTECTED] Subject: MQClient authorization error (2035) Hi , I'm getting a 2035 error when I run amqsputc (MQClient) on a UNIX box. If I log in to the UNIX box where MQSeries is installed and run amqsput (MQServer), the program works fine. If it works fine on the server, shouldn't it also work fine on the client? Any idea why this happens? Do reply Regards Sony 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 ** Click here to visit the Argos home page http://www.argos.co.uk The information contained in this message or any of its attachments may be privileged and confidential, and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you are not the intended addressee, any disclosure, reproduction, distribution, dissemination or use of this communication is not authorised. If you have received this message in error, please advise the sender by using your reply facility in your e-mail software. All messages sent and received by Argos Ltd are monitored for virus, high risk file extensions, and inappropriate content. As a result users should be aware that mail maybe accessed. ** 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 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: MQClient authorization error (2035)
... but that's probably slightly better than the default behaviour, which is that any client is able to connect and run with the authority of any user on your machine, including "mqm" (this is particularly trivial in java code, but it's perfectly possible to do it using MQ client in C or any other language that lets you write client side exits). If someone needs to use client connections, and a requirement to control access to the queue manager, they minimally need some kind of server side security exit to provide some kind of access control (for those not wanting to "roll your own" there are products from Candle, Primeur and doubtless others), or you need to be running WMQ 5.3 and using the SSL support. Off the shelf, the client supplies the user Id and the server assumes the client did the authorisation checking. The "password" is not used on distributed platforms, although it is passed across and could be checked by a server side security exit, if you wrote one to do so. Nigel --- [EMAIL PROTECTED] RIMEUR.COM To: [EMAIL PROTECTED] Sent by: cc: [EMAIL PROTECTED]Subject: Re: MQClient authorization error (2035) .AC.AT 06/03/03 10:14 AM Please respond to MQSERIES Be aware that if you do this, any client will be able to connect and run with the authority of that account. Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Andrew Miller Sent: 03 June 2003 09:30 To: [EMAIL PROTECTED] Subject: Re: MQClient authorization error (2035) Sony, the simple solution is to set the MCAUSER id up on the client svrconn channel to have a valid userid/account ie. one which exists on the box. It cannae be blank. Windy 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 This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries and affiliates. 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: WAS 5.0 Embedded MQ
Jeff The port for the internal JMS provider will be defined in WAS itself under the "JMS Server Properties". Not sure if there is a default port, but in the example I've seen its set to port 5557. But having said that, I don't believe the embedded MQ implementation itself - i.e. the underlying baseMQ queues, can be accessed outside of WAS itself. If you have WAS 5 Enterprise Edition, I believe you get a full MQ implementation. Alternatively you could implement a licenced copy of MQ. In both cases you would then be able to hook up to MMC in the normal way. Also, I would have thought that having an external MQ implementation should improve throughput. It will run in its own address space, rather then the App servers. Note that you can't have full MQ and embedded MQ on the same node - its either or. HTH Neil -Original Message- From: Jeffrey Ross [mailto:[EMAIL PROTECTED] Sent: 02 June 2003 22:11 To: [EMAIL PROTECTED] Subject: WAS 5.0 Embedded MQ Hello, I am hoping somebody in this community can point me in the correct direction. There is an area in my company developing a Java application that uses WAS 5.0, embedded MQ and Savvion on AIX. They experience a real slow down in process time per message when putting multiple messages out there with more than one thread. The time is good one at a time, but obviously, that won't work for production volumes. I believe that the problem is probably Savvion, but I am not familiar with it or WAS 5.0. The application area is also discussing going to full-blown MQ and not using the embedded MQ. Has anybody done this? Have you noticed any improved performance? I can view the queue manager via command line interface. I was hoping to view it in the MMC GUI on my Windows machine. However, either it can't be or it has a different port that I can't find. I created the SYSTEM.ADMIN.SVRCONN channel necessary and there are no exits on it. I looked in the normal places to see what the queue manager port is set to, and there is no entry, leading me to believe it is 1414. However, that did not work. Does WAS 5.0 Embedded MQ have a default port different from 1414? If so, what is the default? Also, any links to manuals for tuning performance would be appreciated. I've done some searches and can't seem to find what I am looking for. Thanks, Jeff Jeffrey D. Ross Senior MQ Administrator Certified WebSphere MQ Specialist & Solutions Expert TransUnion, LLC Tel 312 985 2742 Fax 312 466 7997 Nextel 312 296 0904 [EMAIL PROTECTED] www.transunion.com NOTICE: The information contained in this e-mail is intended only for the use of the recipient named above. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this in error, please notify the sender and return this email (and attachment). Delete the original message or any copy of it from your computer system. Thank you. 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: MQClient authorization error (2035)
Be aware that if you do this, any client will be able to connect and run with the authority of that account. Dave -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Andrew Miller Sent: 03 June 2003 09:30 To: [EMAIL PROTECTED] Subject: Re: MQClient authorization error (2035) Sony, the simple solution is to set the MCAUSER id up on the client svrconn channel to have a valid userid/account ie. one which exists on the box. It cannae be blank. Windy 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
MQSeries and NIS
Hi everyone, Are there any points to keep in mind regarding MQSeries and NIS? Has anyone faced issues in this area? How does MQSeries Client pass the userid under which a client program is run to the server? I have 2 UNIX boxes A and B. On A, i've installed the mqseries client on B, i've installed the MQSeries Server. My userid sova123 is a NIS id and there is no local userid on these boxes. Now, I'm getting a 2035 error when I run amqsputc (MQClient) on a UNIX box A. If I log in B, where MQSeries Server is installed and run amqsput (MQServer), the program works fine. If I set the mcauserid to sova123 on the server connection channel, the MQClient amqsputc works fine. This clearly shows that the when i run the client program, MQSeries is not passing the correct userid sova123 but something else. Is there anyway to find out what userid is being passed? Do reply. Regards Sony 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
Production MQ abends - 2019 / 2195 / 2079 and more.
Hi all, MQ V2.1. OS/390 The last two mornings at exactly the same time we have experienced an issue with the connections between MQSeries and a production CICS region. The errors that are being seen in the CICS log are: +CSQC106D PCCIC CSQCTASK MQGET failure. CKTI will end. MQCC=2 MQRC=2019 (Object Handle) +CSQC110I PCCIC CSQCTASK Queue name = MQPB.INITQ.PB.PCCIC +KAD6500 ERROR ON MQCLOSE QAKE.GET.VALIDATE.CUSTOMER.DETAILS.REQUEST +KAD6500 ERROR ON MQCLOSE REASON = 2019 +CSQC111D PCCIC CSQCTASK CKTI has read a trigger message with an incorrect length of 297 As well as the above we are getting 2195 (Unexpected error) and 2079(Truncated msg) errors. In addition to the above the CICS and MQ logs are showing RACF messages: 06.53.41 STC04301 ICH408I JOB(MVB1MSTR) STEP(MVB1MSTR)---> This should be USER (ZMQMAB1) GROUP ([EMAIL PROTECTED]) MVB1.MQPB.INITQ.PB.PCCIC CL(MQQUEUE ) INSUFFICIENT ACCESS AUTHORITY FROM MVB1.MQPB.INITQ.** (G) ACCESS INTENT(UPDATE ) ACCESS ALLOWED(NONE ) Has anyone experienced any of the above ? Any help would be much appreciated Regards Michelle This email and any attachments are confidential. They may contain privileged information and are intended for the named addressee(s) only. They must not be distributed without our consent. If you are not the intended recipient, please notify us immediately and do not disclose, distribute or retain this email or any part of it. Unless expressly stated, opinions in this email are those of the individual sender and not N Brown Group plc or any of its subsidiaries. You must take full responsibility for virus checking this email and any attachments. Please note that the content of this email or any of its attachments may contain data that falls within the scope of the Data Protection Acts and that you must ensure that any handling or processing of such data by you is fully compliant with the terms and provisions of the Data Protection Act 1984 and 1998. N Brown Group plc. Registered office: 53 Dale Street, Manchester, M60 6ES. Registered in England No.814103. 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: MQClient authorization error (2035)
Sony, the simple solution is to set the MCAUSER id up on the client svrconn channel to have a valid userid/account ie. one which exists on the box. It cannae be blank. Windy On 02/06/2003 15:57:43 MQSeries List wrote: >Hi , > >I'm getting a 2035 error when I run amqsputc (MQClient) on a UNIX box. >If I log in to the UNIX box where MQSeries is installed and run amqsput >(MQServer), the program works fine. > >If it works fine on the server, shouldn't it also work fine on the client? >Any idea why this happens? > >Do reply > >Regards >Sony > >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 For more information on Standard Life, visit our website http://www.standardlife.com/ The Standard Life Assurance Company, Standard Life House, 30 Lothian Road, Edinburgh EH1 2DH, is registered in Scotland (No. SZ4) and regulated by the Financial Services Authority. Tel: 0131 225 2552 - calls may be recorded or monitored. This confidential e-mail is for the addressee only. If received in error, do not retain/copy/disclose it without our consent and please return it to us. We virus scan and monitor all e-mails but are not responsible for any damage caused by a virus or alteration by a third party after it is sent. 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: Client and server configuration
Nae bother. Windy On 02/06/2003 21:56:21 MQSeries List wrote: >Can both have MQSeries client and sever software installed on the >same operating system? I am running Windows 2000 . > >Thanks >TC > > >Do you Yahoo!? >Free online calendar with sync to Outlook(TM). For more information on Standard Life, visit our website http://www.standardlife.com/ The Standard Life Assurance Company, Standard Life House, 30 Lothian Road, Edinburgh EH1 2DH, is registered in Scotland (No. SZ4) and regulated by the Financial Services Authority. Tel: 0131 225 2552 - calls may be recorded or monitored. This confidential e-mail is for the addressee only. If received in error, do not retain/copy/disclose it without our consent and please return it to us. We virus scan and monitor all e-mails but are not responsible for any damage caused by a virus or alteration by a third party after it is sent. 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: XML in MQ messaging
Hi, I have a C++ application that passes XML data from remote locations back to the MQ Server for a triggered application to process, there are no issuesas the data is transparent to the server. Sid -Original Message-From: Teresa Cheung [mailto:[EMAIL PROTECTED]Sent: Tuesday, 3 June 2003 3:53 AMTo: [EMAIL PROTECTED]Subject: XML in MQ messaging Is there anyone using MQSeries to pass XML data? I have a project that involve parsing the XML data received via MQ message. Just wonder if there is any know issue in using MQ to pass XML data. Thanks, TC Do you Yahoo!?Free online calendar with sync to Outlook(TM).
Re: MQClient thread-safe?
To all, My apologies I had read about shared connections in V5.3 and promptly forgot them again so yes you now can coordinate units of work across multiple threads. Regards TIm A Paul Clarke <[EMAIL PROTECTED]To: [EMAIL PROTECTED] IBM.COM> cc: Sent by: MQSeriesSubject: Re: MQClient thread-safe? List <[EMAIL PROTECTED] N.AC.AT> 02/06/2003 19:34 Please respond to MQSeries List >"The MQ Client interface is not thread-safe. You cannot safely use MQ Client >connections to the same queue manager from multiple threads within the same >process (for example, a Workflow Web Client Servlet) ..." Stefan, I don't agree that the client is not thread-safe. Thread safe implies that you can 'safely' use the MQI from multiple threads, which you can. What you can't do (until recently) was use a connection that was created on one thread, in an MQI call in another thread. This, I would say, is thread unfriendly, but not thread unsafe. This limitation was an architectural one, defned in the MQI specification, not a feature of the client. In 5.3 a new type of connection can be made, which is a shared connection. A shared connection *can* be used by any thread. This is available both on the server and the client. Cheers, P. Paul G Clarke WebSphere MQ Development IBM Hursley 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: Client and server configuration
Yes. Teresa Cheung <[EMAIL PROTECTED]> Sent by: MQSeries List <[EMAIL PROTECTED]> 06/02/2003 03:56 PM Please respond to MQSeries List To: [EMAIL PROTECTED] cc: Subject: Client and server configuration Can both have MQSeries client and sever software installed on the same operating system? I am running Windows 2000 . Thanks TC Do you Yahoo!? Free online calendar with sync to Outlook(TM).
Re: WAS 5.0 Embedded MQ
I've found some tuning information at: http://publib7b.boulder.ibm.com/wasinfo1/en/info/aes/ae/rprf_tuneindex.html Hope it helps, Ron --- Jeffrey Ross <[EMAIL PROTECTED]> wrote: > Hello, > > I am hoping somebody in this community can point me > in the correct > direction. > > There is an area in my company developing a Java > application that uses > WAS 5.0, embedded MQ and Savvion on AIX. They > experience a real slow > down in process time per message when putting > multiple messages out > there with more than one thread. The time is good > one at a time, but > obviously, that won't work for production volumes. > I believe that the > problem is probably Savvion, but I am not familiar > with it or WAS 5.0. > The application area is also discussing going to > full-blown MQ and not > using the embedded MQ. Has anybody done this? Have > you noticed any > improved performance? > > I can view the queue manager via command line > interface. I was hoping > to view it in the MMC GUI on my Windows machine. > However, either it > can't be or it has a different port that I can't > find. I created the > SYSTEM.ADMIN.SVRCONN channel necessary and there are > no exits on it. I > looked in the normal places to see what the queue > manager port is set > to, and there is no entry, leading me to believe it > is 1414. However, > that did not work. Does WAS 5.0 Embedded MQ have a > default port > different from 1414? If so, what is the default? > > Also, any links to manuals for tuning performance > would be appreciated. > I've done some searches and can't seem to find what > I am looking for. > > Thanks, > Jeff > > Jeffrey D. Ross > Senior MQ Administrator > Certified WebSphere MQ Specialist & Solutions Expert > TransUnion, LLC > Tel 312 985 2742 > Fax 312 466 7997 > Nextel 312 296 0904 > [EMAIL PROTECTED] > www.transunion.com > > NOTICE: > The information contained in this e-mail is intended > only for the use > of the recipient named above. If you are not the > intended recipient, > you are hereby notified that any dissemination, > distribution or copying > of this e-mail is strictly prohibited. If you have > received this in > error, please notify the sender and return this > email (and attachment). > Delete the original message or any copy of it from > your computer system. > Thank you. > > 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 __ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com 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
WAS 5.0 Embedded MQ
Hello, I am hoping somebody in this community can point me in the correct direction. There is an area in my company developing a Java application that uses WAS 5.0, embedded MQ and Savvion on AIX. They experience a real slow down in process time per message when putting multiple messages out there with more than one thread. The time is good one at a time, but obviously, that won't work for production volumes. I believe that the problem is probably Savvion, but I am not familiar with it or WAS 5.0. The application area is also discussing going to full-blown MQ and not using the embedded MQ. Has anybody done this? Have you noticed any improved performance? I can view the queue manager via command line interface. I was hoping to view it in the MMC GUI on my Windows machine. However, either it can't be or it has a different port that I can't find. I created the SYSTEM.ADMIN.SVRCONN channel necessary and there are no exits on it. I looked in the normal places to see what the queue manager port is set to, and there is no entry, leading me to believe it is 1414. However, that did not work. Does WAS 5.0 Embedded MQ have a default port different from 1414? If so, what is the default? Also, any links to manuals for tuning performance would be appreciated. I've done some searches and can't seem to find what I am looking for. Thanks, Jeff Jeffrey D. Ross Senior MQ Administrator Certified WebSphere MQ Specialist & Solutions Expert TransUnion, LLC Tel 312 985 2742 Fax 312 466 7997 Nextel 312 296 0904 [EMAIL PROTECTED] www.transunion.com NOTICE: The information contained in this e-mail is intended only for the use of the recipient named above. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this in error, please notify the sender and return this email (and attachment). Delete the original message or any copy of it from your computer system. Thank you. 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
Client and server configuration
Can both have MQSeries client and sever software installed on the same operating system? I am running Windows 2000 . Thanks TC Do you Yahoo!? Free online calendar with sync to Outlook(TM).
Win Client to AIX CCSID Problem
hi everyone -- I ahve just started looking at a problem that occurs when a custom MQClient program on Windows is trying to connect to MQServer on AIX ... I get a 2059 , but amqsputc seems to work fine, and I get this message in the log: 06/02/03 14:27:05 AMQ9541: CCSID supplied for data conversion not supported. EXPLANATION: The program ended because, either the source CCSID '1208' or the target CCSID '437' is not valid, or is not currently supported. ACTION: Correct the CCSID that is not valid, or ensure that the requested CCSID can be supported. -- all helpful suggestions would be truly welcome, 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: XML in MQ messaging
Yes you are alone, and no; no one reads the standards like that ;-) Actually, depending on the task and project you are perfectly correct in looking that deep into standards. I find that performing conversions that an application created via XML should be handled by XML, unless there is a faster means to do it. So, you either put the load on the client or the server, but usually it is better to put it on the client. Again, it all comes down to a design issue. Chris -Original Message- From: Pavel Tolkachev [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2003 3:25 PM To: [EMAIL PROTECTED] Subject: Re: XML in MQ messaging Am I the only one who considers XML documents opaque byte arrays (correspondingly bravely feeling the format field with MQFMT_NONE)? Encoding specification is a part of an XML document. Moreover, one of the relatively latests erratas to the specification explicitly tells: "Unless an encoding is determined by a higher-level protocol, it is also a fatal error if an XML entity contains no encoding declaration and its content is not legal UTF-8 or UTF-16" (see http://www.w3.org/XML/xml-V10-2e-errata, E23). So, just for the notes: if you convert characters by MQ means using MQSTR format and this is not from UTF8 to UTF16 or vice versa (why would you want to do this?), the content of your message may not be a legal XML document anymore (because MQ will not change or add in your entities -- at least not for MQSTR format and MQ is (IMHO, of course) not a "higher-level protocol" in terms of the standard). Sorry for raisng a potentially controversial issue (I think I did it before in this list), what I actually want to know is in the beginning of the letter: am I alone, who reads the standard in this way? My another question is: technically, what are the advantages of using MQ instead of client side XML parser to convert characters? Doesn't it create an additional CPU load on the server side, therefore hurting the scalability? Pavel Roger Lacroix <[EMAIL PROTECTED]To: [EMAIL PROTECTED] ALWARE.BIZ> cc: Sent by: MQSeries Subject: Re: XML in MQ messaging List <[EMAIL PROTECTED] C.AT> 06/02/2003 02:09 PM Please respond to MQSeries List Hi, I have worked on many projects over the last 3 years that have transmitted XML via WMQ. i.e. Windows (XML) -> Solaris (COPYBOOK) -> OS/390 (and back) AIX (XML) -> OS/390 (XML) (and back) Just set the MQMD.Format to be 'MQSTR' and have the receiving application do a get with convert and everything will be fine. The hard part is the transformation of message types: ie. XML to COPYBOOK or XML (style A) to XML (style B). Use a tool like WMQI or Mercator for the transformation part. It will make your life easier. :) later Roger... At 01:52 PM 6/2/2003, you wrote: Is there anyone using MQSeries to pass XML data? I have a project that involve parsing the XML data received via MQ message. Just wonder if there is any know issue in using MQ to pass XML data. Thanks, TC Do you Yahoo!? Free online calendar with sync to Outlook(TM). -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. 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: MQClient authorization error (2035)
Sony, I'm not familiar with NIS userids, but from the context, I'd guess they're like a single signon or a Windows domain signon? Is the userid you are using the same in both cases? MQ security on Unix is based on the user's group; does using NIS have any effect on the group assignment? One thing you could do is turn on Authority Events (I think the4 syntax is "ALTER QMGR AUTHOREV(ENABLED)", but that's from memory and should be checked. Then when you get the 2035, an event message should be written to the SYSTEM.ADMIN.QMGR.EVENT (wouldn't sear that's the right name, either). This should tell you in more detail where the problem lies. -Original Message- From: Sony Varghese [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2003 11:50 AM To: [EMAIL PROTECTED] Subject: Re: MQClient authorization error (2035) Hi Rebecca, The scenario you have described is correct. My userid is a NIS userid id .. There's no seperate security set up for the queue manager Regards Sony -Original Message- From: Bullock, Rebecca (CSC) [mailto:[EMAIL PROTECTED] Sent: 02 June 2003 16:20 To: [EMAIL PROTECTED] Subject: Re: MQClient authorization error (2035) Sony, it's unclear from your question exactly what your issue is. Here's what I think you're asking: On Unix box A, you set up the MQSERVER variable (or a client channel table) which connects you to Unix box B. Then when you try to use amqsputc on A, you get a 2035 error. If, however, you log in on Unix box B and use amqsput, it runs fine. If this correct, then: Is the userid you are using on A defined on B and if it is, have you set up security to allow that userid to connect and to write to the queue? Just a thought, based on what I think you're asking -- Rebecca Rebecca Bullock Computer Sciences Corporation MFCoE/Newark CS Team Educational Testing Service Account Princeton, NJ 08541 email: [EMAIL PROTECTED] or [EMAIL PROTECTED] -Original Message- From: Sony Varghese [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2003 10:58 AM To: [EMAIL PROTECTED] Subject: MQClient authorization error (2035) Hi , I'm getting a 2035 error when I run amqsputc (MQClient) on a UNIX box. If I log in to the UNIX box where MQSeries is installed and run amqsput (MQServer), the program works fine. If it works fine on the server, shouldn't it also work fine on the client? Any idea why this happens? Do reply Regards Sony 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 ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. 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 ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. 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: XML in MQ messaging
Am I the only one who considers XML documents opaque byte arrays (correspondingly bravely feeling the format field with MQFMT_NONE)? Encoding specification is a part of an XML document. Moreover, one of the relatively latests erratas to the specification explicitly tells: "Unless an encoding is determined by a higher-level protocol, it is also a fatal error if an XML entity contains no encoding declaration and its content is not legal UTF-8 or UTF-16" (see http://www.w3.org/XML/xml-V10-2e-errata, E23). So, just for the notes: if you convert characters by MQ means using MQSTR format and this is not from UTF8 to UTF16 or vice versa (why would you want to do this?), the content of your message may not be a legal XML document anymore (because MQ will not change or add in your entities -- at least not for MQSTR format and MQ is (IMHO, of course) not a "higher-level protocol" in terms of the standard). Sorry for raisng a potentially controversial issue (I think I did it before in this list), what I actually want to know is in the beginning of the letter: am I alone, who reads the standard in this way? My another question is: technically, what are the advantages of using MQ instead of client side XML parser to convert characters? Doesn't it create an additional CPU load on the server side, therefore hurting the scalability? Pavel Roger Lacroix <[EMAIL PROTECTED]To: [EMAIL PROTECTED] ALWARE.BIZ> cc: Sent by: MQSeries Subject: Re: XML in MQ messaging List <[EMAIL PROTECTED] C.AT> 06/02/2003 02:09 PM Please respond to MQSeries List Hi, I have worked on many projects over the last 3 years that have transmitted XML via WMQ. i.e. Windows (XML) -> Solaris (COPYBOOK) -> OS/390 (and back) AIX (XML) -> OS/390 (XML) (and back) Just set the MQMD.Format to be 'MQSTR' and have the receiving application do a get with convert and everything will be fine. The hard part is the transformation of message types: ie. XML to COPYBOOK or XML (style A) to XML (style B). Use a tool like WMQI or Mercator for the transformation part. It will make your life easier. :) later Roger... At 01:52 PM 6/2/2003, you wrote: Is there anyone using MQSeries to pass XML data? I have a project that involve parsing the XML data received via MQ message. Just wonder if there is any know issue in using MQ to pass XML data. Thanks, TC Do you Yahoo!? Free online calendar with sync to Outlook(TM). -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. 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: tcp/ip responder program
I've seen that message with SSL Channels when there was a problem with the SSL Setup. "Anderson, Lizette T. (RyTull)" To: [EMAIL PROTECTED] <[EMAIL PROTECTED]cc: ONTULL.COM>Subject: tcp/ip responder program Sent by: MQSeries List <[EMAIL PROTECTED] T> 06/02/2003 02:21 PM Please respond to MQSeries List Has anyone ever received this message on an Windows NT server running MQseries 5.1: The TCP/IP responder program could not be started. I received the above message and then the Queue manager went down. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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 This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries and affiliates. 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
tcp/ip responder program
Has anyone ever received this message on an Windows NT server running MQseries 5.1: The TCP/IP responder program could not be started. I received the above message and then the Queue manager went down. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- 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: XML in MQ messaging
Hi, I have worked on many projects over the last 3 years that have transmitted XML via WMQ. i.e. Windows (XML) -> Solaris (COPYBOOK) -> OS/390 (and back) AIX (XML) -> OS/390 (XML) (and back) Just set the MQMD.Format to be 'MQSTR' and have the receiving application do a get with convert and everything will be fine. The hard part is the transformation of message types: ie. XML to COPYBOOK or XML (style A) to XML (style B). Use a tool like WMQI or Mercator for the transformation part. It will make your life easier. :) later Roger... At 01:52 PM 6/2/2003, you wrote: Is there anyone using MQSeries to pass XML data? I have a project that involve parsing the XML data received via MQ message. Just wonder if there is any know issue in using MQ to pass XML data. Thanks, TC Do you Yahoo!? Free online calendar with sync to Outlook(TM).
Re: XML in MQ messaging
Title: Message There is no issue, as it is text. However, this is often the first time that the CCSID on the mainframe is discovered to be set to something that can't translate every character.. Peter Heggie (315) 428 - 3193 -Original Message-From: Teresa Cheung [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2003 1:53 PMTo: [EMAIL PROTECTED]Subject: XML in MQ messaging Is there anyone using MQSeries to pass XML data? I have a project that involve parsing the XML data received via MQ message. Just wonder if there is any know issue in using MQ to pass XML data. Thanks, TC Do you Yahoo!?Free online calendar with sync to Outlook(TM). This e-mail and any files transmitted with it, are confidential to National Grid and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please contact the National Grid USA Enterprise Support Center on 508-389-3375 or 315-428-6360.
XML in MQ messaging
Is there anyone using MQSeries to pass XML data? I have a project that involve parsing the XML data received via MQ message. Just wonder if there is any know issue in using MQ to pass XML data. Thanks, TC Do you Yahoo!? Free online calendar with sync to Outlook(TM).
MQ Visual Edit v0.4.3
All: I have released the next beta v0.4.3 of MQ Visual Edit. I created a new help system for beta v0.4.2 for MQ Visual Edit but it required Java v1.4 to do the printing. Since a lot of people are still using Java v1.3, I decided to remove that feature. Instead I went with launching the HTML help pages in a browser window. (Hopefully everyone has a browser on their machine!!) This solution should work on any platform that has a browser installed (Windows, Linux, Unix, etc...). The following enhancements / fixes have been made: - Dropped the new Help menu system - now open a browser window to view the help pages. - New 'EBCDIC Data' tab on Simple Message Edit panel. This feature will attempt to convert the data from EBCDIC to ASCII. This is useful when the MQMD.Format is NOT set to 'MQSTR'. - Added Read Only, Convert on Get and Context settings on the Open Queue Dialog box. - Added a 'Mask' field on the Open Queue Dialog box for filtering the list of queues. - Added Context selection on the Open Queue Dialog box (you cannot correctly edit the MQMD without setting the context). - Main menu Import / Export functions now remembers last used directory. - Simple Message menu Load / Save functions now remembers last used directory. - Updated docs (English only) You can download MQ Visual Edit at: http://www.capitalware.biz/beta.html Note: This is an on-going project, so please send comments and / or complaints to me. later Roger Lacroix Enterprise Architect Capitalware Inc. http://www.capitalware.biz IBM Certified Specialist - MQSeries IBM Certified Developer - MQSeries IBM Certified Solutions Expert - MQSeries 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: MQClient authorization error (2035)
Hi John, My userid is a NIS userid id .. The MCAUSER is set to blank .. Regards Sony -Original Message- From: John Scott [mailto:[EMAIL PROTECTED] Sent: 02 June 2003 17:18 To: [EMAIL PROTECTED] Subject: Re: MQClient authorization error (2035) Are you logging on using a different user name from the client? What is the MCAUSER set to for the server connection channel the client is using? Regards John. -Original Message- From: Sony Varghese [mailto:[EMAIL PROTECTED] Sent: 02 June 2003 14:58 To: [EMAIL PROTECTED] Subject: MQClient authorization error (2035) Hi , I'm getting a 2035 error when I run amqsputc (MQClient) on a UNIX box. If I log in to the UNIX box where MQSeries is installed and run amqsput (MQServer), the program works fine. If it works fine on the server, shouldn't it also work fine on the client? Any idea why this happens? Do reply Regards Sony 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 ** Click here to visit the Argos home page http://www.argos.co.uk The information contained in this message or any of its attachments may be privileged and confidential, and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you are not the intended addressee, any disclosure, reproduction, distribution, dissemination or use of this communication is not authorised. If you have received this message in error, please advise the sender by using your reply facility in your e-mail software. All messages sent and received by Argos Ltd are monitored for virus, high risk file extensions, and inappropriate content. As a result users should be aware that mail maybe accessed. ** 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: MQClient authorization error (2035)
Hi Rebecca, The scenario you have described is correct. My userid is a NIS userid id .. There's no seperate security set up for the queue manager Regards Sony -Original Message- From: Bullock, Rebecca (CSC) [mailto:[EMAIL PROTECTED] Sent: 02 June 2003 16:20 To: [EMAIL PROTECTED] Subject: Re: MQClient authorization error (2035) Sony, it's unclear from your question exactly what your issue is. Here's what I think you're asking: On Unix box A, you set up the MQSERVER variable (or a client channel table) which connects you to Unix box B. Then when you try to use amqsputc on A, you get a 2035 error. If, however, you log in on Unix box B and use amqsput, it runs fine. If this correct, then: Is the userid you are using on A defined on B and if it is, have you set up security to allow that userid to connect and to write to the queue? Just a thought, based on what I think you're asking -- Rebecca Rebecca Bullock Computer Sciences Corporation MFCoE/Newark CS Team Educational Testing Service Account Princeton, NJ 08541 email: [EMAIL PROTECTED] or [EMAIL PROTECTED] -Original Message- From: Sony Varghese [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2003 10:58 AM To: [EMAIL PROTECTED] Subject: MQClient authorization error (2035) Hi , I'm getting a 2035 error when I run amqsputc (MQClient) on a UNIX box. If I log in to the UNIX box where MQSeries is installed and run amqsput (MQServer), the program works fine. If it works fine on the server, shouldn't it also work fine on the client? Any idea why this happens? Do reply Regards Sony 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 ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. 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
mqm group member can't create qmgr on Solaris
Title: mqm group member can't create qmgr on Solaris Hi, we setup MQ on Solaris. V5.2, csd04. login as mqm, I can do anything successfully. But whenever login as [mqm] group member, other than mqm, crtmqm command would fail with return code 893. Specifically, we trace a problem back to this after a failure running MQSI's mqsicreatebroker command, which needs access to an existing or create qmgr. has anyone encountered this problem? any feedback would be greatly appreciated. Benjamin Zhou
Re: MQClient authorization error (2035)
Sony, it's unclear from your question exactly what your issue is. Here's what I think you're asking: On Unix box A, you set up the MQSERVER variable (or a client channel table) which connects you to Unix box B. Then when you try to use amqsputc on A, you get a 2035 error. If, however, you log in on Unix box B and use amqsput, it runs fine. If this correct, then: Is the userid you are using on A defined on B and if it is, have you set up security to allow that userid to connect and to write to the queue? Just a thought, based on what I think you're asking -- Rebecca Rebecca Bullock Computer Sciences Corporation MFCoE/Newark CS Team Educational Testing Service Account Princeton, NJ 08541 email: [EMAIL PROTECTED] or [EMAIL PROTECTED] -Original Message- From: Sony Varghese [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2003 10:58 AM To: [EMAIL PROTECTED] Subject: MQClient authorization error (2035) Hi , I'm getting a 2035 error when I run amqsputc (MQClient) on a UNIX box. If I log in to the UNIX box where MQSeries is installed and run amqsput (MQServer), the program works fine. If it works fine on the server, shouldn't it also work fine on the client? Any idea why this happens? Do reply Regards Sony 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 ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. 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: MQClient authorization error (2035)
Are you logging on using a different user name from the client? What is the MCAUSER set to for the server connection channel the client is using? Regards John. -Original Message- From: Sony Varghese [mailto:[EMAIL PROTECTED] Sent: 02 June 2003 14:58 To: [EMAIL PROTECTED] Subject: MQClient authorization error (2035) Hi , I'm getting a 2035 error when I run amqsputc (MQClient) on a UNIX box. If I log in to the UNIX box where MQSeries is installed and run amqsput (MQServer), the program works fine. If it works fine on the server, shouldn't it also work fine on the client? Any idea why this happens? Do reply Regards Sony 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 ** Click here to visit the Argos home page http://www.argos.co.uk The information contained in this message or any of its attachments may be privileged and confidential, and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you are not the intended addressee, any disclosure, reproduction, distribution, dissemination or use of this communication is not authorised. If you have received this message in error, please advise the sender by using your reply facility in your e-mail software. All messages sent and received by Argos Ltd are monitored for virus, high risk file extensions, and inappropriate content. As a result users should be aware that mail maybe accessed. ** 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: MQClient authorization error (2035)
When you run as the client, you are connecting to the QM via a SVRCONN channel. On that SVRCONN channel, there is an attribute called MCAUSERIDENTIFIER. If there is a value specified there, that is the ID that MQ is authenticating against. If it is blank, then the ID that you are logged onto your client machine is used. Or you may have a security exit setting the ID. Regardless of where the ID is being actually set, if that ID is not authorized, you will get a 2035. -Original Message- From: Sony Varghese [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2003 10:58 AM To: [EMAIL PROTECTED] Subject: MQClient authorization error (2035) Hi , I'm getting a 2035 error when I run amqsputc (MQClient) on a UNIX box. If I log in to the UNIX box where MQSeries is installed and run amqsput (MQServer), the program works fine. If it works fine on the server, shouldn't it also work fine on the client? Any idea why this happens? Do reply Regards Sony 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 This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. 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: WebSphere Application Server / JMS / MQSeries
Hi Jeff There are two mechanisms for using JMS in WAS. I assume you are using the link to MQSeries JMS method, rather than the internal WAS method. I am just about to test this link myself. There is a WAS Tutorial from IBM about writing Message Driven Beans which may be of use - I can point you to these if interested. Also, I have some Java code, modified from the IBM Samples that will allow you to put and get messages from/to the command line, similar to amqsput/get. These do however assume the use of a repository to hold your connection factory and other objects. Let me know if these may be of use and I'll send them directly to you. Regards Neil -Original Message- From: Jeff A Tressler [mailto:[EMAIL PROTECTED] Sent: 30 May 2003 20:34 To: [EMAIL PROTECTED] Subject: WebSphere Application Server / JMS / MQSeries Hi Normal programming tasks use the MQI (MQSeries API) to access MQSeries. Our company is beginning to experiment with WebSphere Application Server and its use of the JMS to access MQSeries. Our Infrastructure Group has set up and configured the system but this group has little or no actual knowledge of MQSeries, WebSphere, or JMS. They basically followed instructions on how to install and configure the components. I have been asked to verify the JMS implementation and test its connectivity to MQSeries. While I know quite a bit about MQSeries my exposure to JMS is limited. How do you verify the installation and configuration of the JMS in WebSphere Application Server? I hope it is as simple as using an equivalent to amqsput. It would be nice to run something like a jmsput and jmsget program to verify the connectivity exists. Thank for your time. Jeff Tressler 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
MQClient authorization error (2035)
Hi , I'm getting a 2035 error when I run amqsputc (MQClient) on a UNIX box. If I log in to the UNIX box where MQSeries is installed and run amqsput (MQServer), the program works fine. If it works fine on the server, shouldn't it also work fine on the client? Any idea why this happens? Do reply Regards Sony 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: Channel State - Retrying
Hi Hubert, Thanks for your reply. Its working fine now ... i think it had something to do with the file system relocation ... Regards Sony -Original Message- From: Kleinmanns, Hubert [mailto:[EMAIL PROTECTED] Sent: 02 June 2003 12:13 To: [EMAIL PROTECTED] Subject: AW: Channel State - Retrying Hi Sony, the MQSeries software may be installed once (on a shared disk) or twice (on local disks). These files are installed in /opt/mqm or /usr/mqm. Both scenarios have advantages and both work fine. What you need on a shared disk are the DATA files. These are normally stored in /var/mqm and it does not matter, wheather the software is shared or not. Regards Hubert Kleinmanns -Ursprüngliche Nachricht- Von: Sony Varghese [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 28. Mai 2003 17:21 An: [EMAIL PROTECTED] Betreff: Re: Channel State - Retrying Thanks Hubert .. Would this matter even if MQSeries is installed on a shared disk that is visible to both the members ? Regards Sony -Original Message- From: Kleinmanns, Hubert [mailto:[EMAIL PROTECTED] Sent: 28 May 2003 12:43 To: [EMAIL PROTECTED] Subject: AW: Channel State - Retrying Hi Sony, the data and status informations are stored in files in /var/mqm. You must take over theses files, to run your queue manager on another node. Otherwise you do not have the same queue manager running, but only a different queue manager with the same name. Values like "sequence number" then differ. NPMSPEED stands for NonPersistentMessageSPEED. If this value is set to FAST, you may loose (and problably have lost) non-persistent messages. Regards Hubert Kleinmanns -Ursprüngliche Nachricht- Von: Sony Varghese [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 28. Mai 2003 11:55 An: [EMAIL PROTECTED] Betreff: Re: Channel State - Retrying Hi Hubert, Here is my present test scenario: I'm presently using TruCluster V5.1 (Cluster software for Compaq Tru64 Unix) During relocation, I am not taking over the filesystem /var/mqm . Will this cause a problem? My test messages presently are not persistent . Channel attribute NPMSPEED is set to Fast. Awaiting your reply, Warm Regards, VJ. -Original Message- From: Kleinmanns, Hubert [mailto:[EMAIL PROTECTED] Sent: 28 May 2003 10:23 To: [EMAIL PROTECTED] Subject: AW: Channel State - Retrying Hi Sony, some questions: What cluster do you use (HACMP, SunHA, Veritas ...) ? Do you take over the file system /var/mqm ? Are your messages persistent ? What is the value of the channel attribut NPMSPEED ? Regards Hubert Kleinmanns -Ursprüngliche Nachricht- Von: Sony Varghese [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 28. Mai 2003 10:48 An: [EMAIL PROTECTED] Betreff: Channel State - Retrying Hi everyone, When does a channel go into the retry state? I have a scenario where 2 qmgrs QM1 and QM2 communicate with each other. I've defined sender channel QM1.QM2 on QM1 and a corresponding receiver channel on QM2 QM2 is on a clustered node consisting of 2 members M1 and M2. As a part of my test, I initially put 200 messages on a remote definition queue on QM1 and all the 200 messages are transferred to the corresponding queue on QM2. No problems here !! Both the sender and receiver channel are in the running state at this point. While the channels are in the running state i switch/relocate QM2 from member M1 to M2. During relocation, QM2 is ended in the following way: - endmqm -i : If this takes more than a specified time, - endmqm -p If this takes more than a specified time, - manually stopping the queue manager Once QM2 comes back up again, the receiver channel is inactive but the sender is still running .. I thought that at this point the sender channel would go to retrying state but it still remains in the running state? I put another 200 messages but the messages are not delivered to the queue on QM2. However, the transmission queue on QM1 is empty and the sender channel status shows me a message count of 400. Has anyone faced this before? Do reply, Thanks, VJ 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 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 Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http:
