[no subject]
I will be out of the office starting 02/17/2003 and will not return until 02/20/2003. 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
"SIGNOFF MQSERIES"
Title: Message "SIGNOFF MQSERIES" **Disclaimer** Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited.
Re: Can MQ V5.2 & Websphere MQ V5.3 co-exist?
Does the diff MQ versions run concurrently in the same iSeries box and how to go about setting it up? Thanks. Geok Hoon - Forwarded by Geok Hoon FOO/ISD/HDB/SG on 18/02/2003 09:18 AM - YourTEL Ref Our (Embedded image moved to FAX Reffile: pic26465.pcx) Email Categories Classification : "Yeh, Jeff" cc: Sent by: MQSeries Subject: Re: Can MQ V5.2 & Websphere MQ V5.3 List co-exist? 14/02/2003 07:59 PM Please respond to MQSeries List It works very well to us. We have v52, v521, v53. I really like v53. It's much robust. Jeff -Original Message- From: Geok Hoon FOO [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 13, 2003 8:56 PM To: [EMAIL PROTECTED] Subject: Can MQ V5.2 & Websphere MQ V5.3 co-exist? Hi, We plan to upgrade MQ V5.2 to Websphere MQ V5.3 on iseries. Does anyone know whether MQ V5.2 can co-exist with V5.3? regards. Geok Hoon Warning : Privileged/confidential information may be contained in this message. If you are not the intended addressee, you must not copy, distribute or take any action in reliance thereon. Communication of any information in this email to any unauthorised person is an offence under the Official Secrets Act (Cap 213). If you receive this message in error, please notify the sender immediately and delete the same. Visit the eCitizen Housing Town at Http://www.ecitizen.gov.sg/ 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 Warning : Privileged/confidential information may be contained in this message. If you are not the intended addressee, you must not copy, distribute or take any action in reliance thereon. Communication of any information in this email to any unauthorised person is an offence under the Official Secrets Act (Cap 213). If you receive this message in error, please notify the sender immediately and delete the same. Visit the eCitizen Housing Town at Http://www.ecitizen.gov.sg/ pic26465.pcx Description: Binary data
Re: Messaging query
Lawrie, Background: Simply stated, Java Message Service (JMS) is an abstraction of the underlying messaging provider APIs. Developers may code to an industry standard rather than to the messaging providerâs specific API library. The intent is to standardize the API so that it doesn't matter if you use WMQ or some other queuing mechanism (e.g., MS MQ, MQ Sonic). The link between the JMS code and the JMS provider (e.g., WMQ) is the context factory that is defined in JNDI. An administrator would create the entries in the JNDI bindings (which could be in a file or defined in the Web Application Server such as WebLogic) that would relate a logical JMS queue to the actual provider queue. This is all described in the WebSphere MQ manual, MQSeries Using Java, Ch. 5. Your Application: However, this is all Java-based. So, if are using C or C++, and you are using WMQ, simply use the standard MQI commands described in the programmers guide to write your interface. On listener side of your application, the intent of MDB's is to act as an automatic message consummer. MDB's are listeners that awake (using the onMessage method) on the arrival of a message on a JMS queue (which is just logical name associated with an actual queue name in the JMS JNDI bindings). Now, I could be wrong and I haven't done exactly this yet, but I see no reason why your non-java application using MQI commands couldn't put a message to a queue that is also defined as a JMS queue on which an MDB is listening. Should be no problem. Make sense? Regards, Guy |-+> | | Lawrence Cornell | | | | | | Sent by: MQSeries| | | List | | || | || | || | | 02/09/2003 04:47 | | | AM | | | Please respond to| | | MQSeries List| | || |-+> >-| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Messaging query | | | | | >-| Hi All, I am fairly new to messaging and JMS and was wondering if anyone might be able to help me with a problem... I need to send messages from a *non-Java* application using IBM MQSeries to be consumed by an EJB-based Java application which is running on WebLogic Server (and also need to be able to send messages back). I would like to be able to use JMS and to receive these messages using message-driven EJBs on WebLogic. Is this possible? I suppose my question breaks down further to: 1. Is it possible to send JMS-format messages (using MQSeries) from a non-Java application? (I understand that JMS is just a standardised Java interface for messaging services, I just don't quite understand whether it is possible to mimic the JMS message format so that messages sent from non-Java applications can be consumed as JMS messages and vice versa?) 2. How do I integrate MQSeries and WebLogic so that my WebLogic message-driven EJBs are called as consumers of MQSeries messages? Is this possible? 3. If it is not possible to send/consume JMS-format messages from non-Java applications, then what are my alternatives? 4. Would an alternative be to write an additional non-EJB Java app to act as the non-JMS MQSeries format message consumer which then delegates to the EJBs? - If so what would be involved here? I would be extremely grateful for any help you can offer because, as you can probably tell, I am somewhat in the dark here... Thanks in advance, Lawrie _ Stay in touch with absent friends - get MSN Mes
Re: Log size on MQ Win2000 Server
Wesley, Log type (circular or linear) is set up in windows when you create the queue manager. You cannot switch log type or size after you have created the queue manager. You must recreate it to change these values. If you need to go through this exercise, I suggest you export your object definitions with support pac MS03. The support pac MS0L is for maintaining linear logs (used with rcdmqimg for recording images). You can get the support pac at: http://www-3.ibm.com/software/integration/support/supportpacs/category2.html -Bridgette Beardsley FYI - I believe in UNIX systems log file attributes can be changed in the mqm.ini file. -Original Message- From: Wesley Shaw [mailto:[EMAIL PROTECTED]] Sent: Monday, February 17, 2003 12:51 PM To: [EMAIL PROTECTED] Subject: Log size on MQ Win2000 Server Where do I set the active log size on a win2000 MQ instance ? Also, is there a record_mq_image and cleanmqlogs set of utilities for cleaning up free logs ? Wesley Shaw OJRP 10th Floor Work: 804 771 3589 (736-3589) Pager: 888 436 2805 Mobile 804 512 5260 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
Log size on MQ Win2000 Server
Where do I set the active log size on a win2000 MQ instance ? Also, is there a record_mq_image and cleanmqlogs set of utilities for cleaning up free logs ? Wesley Shaw OJRP 10th Floor Work: 804 771 3589 (736-3589) Pager: 888 436 2805 Mobile 804 512 5260 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: W2K Trigger monitor triggers going to DLQ
Another tip is to run the trigger monitor in the foreground, rather than as an MQSeries service. You start it up with : Usage: runmqtrm [-m QMgrName] [-q InitQ] Remember to disable the MQSeries service trigger monitor to ensure your foreground trigger monitor does the work. This way you see the trigger messages being processed which can assist with debugging. Matt Gurney "Stephan C. Moen" <[EMAIL PROTECTED]> TPSGI.COM Sent by: MQSeries List <[EMAIL PROTECTED]> 17/02/2003 16:14 Please respond to MQSeries List To: [EMAIL PROTECTED] cc: Subject: Re: W2K Trigger monitor triggers going to DLQ What I have done in the past is dump the contents of the message using one of the sample programs provided when you install MQM on the platform in question. On a Windows system, this would be something like Letter>:\Program Files\IBM\MQSeries\Tools\C\Samples\Bin\amqsbcg. This utility will view or browse the message on the DLQ, dumping the contents of that message to your console. It will NOT read the message off the queue. In the body of the message dumped, review the 6th word (11th and 12th bytes). Since the error code is in hexadecimal, if you have a UNIX machine around, simply do the following at the command line: bc ibase=16 07EE CNTRL-D BC is a binary calculator. ibase means BC will read its input in base 16 vs. base 10. All input values need to be in UPPERCASE. The decimal equivalent of 07EE is 2030. Now take that value and look it up either in MQSeries Information Center or use the following command on UNIX systems - grep 2030 /usr/include/cmqc.h. The returned string of the last example will give you why the message got redirected to the DLQ. Other codes you may find in the DLQ are as follows: HEX DECIMAL ERROR DESCRIPTION 07EE 2030 Message Too Big for Queue 07EF 2031 Message Too Big for Queue Manager 0805 2053 Queue Full 0835 2101 MQ Object Damaged 08AA 2218 Message Too Big for Channel Stephan C. Moen [EMAIL PROTECTED] -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Wesley Shaw Sent: Monday, February 17, 2003 7:16 AM To: [EMAIL PROTECTED] Subject: W2K Trigger monitor triggers going to DLQ I have a triggered process where the trigger message is going to the DLQ. Below is the message header. I am trying to figure out the reason code. Anybody decode that for me quicker than I ? (Embedded image moved to file: pic04664.pcx) Wesley Shaw OJRP 10th Floor Work: 804 771 3589 (736-3589) Pager: 888 436 2805 Mobile 804 512 5260 _ For your protection, this e-mail has been scanned for known viruses and damaging content by http://GATEWAYDEFENDER.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
"SIGNOFF MQSERIES"
"SIGNOFF 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: W2K Trigger monitor triggers going to DLQ
What I have done in the past is dump the contents of the message using one of the sample programs provided when you install MQM on the platform in question. On a Windows system, this would be something like :\Program Files\IBM\MQSeries\Tools\C\Samples\Bin\amqsbcg. This utility will view or browse the message on the DLQ, dumping the contents of that message to your console. It will NOT read the message off the queue. In the body of the message dumped, review the 6th word (11th and 12th bytes). Since the error code is in hexadecimal, if you have a UNIX machine around, simply do the following at the command line: bc ibase=16 07EE CNTRL-D BC is a binary calculator. ibase means BC will read its input in base 16 vs. base 10. All input values need to be in UPPERCASE. The decimal equivalent of 07EE is 2030. Now take that value and look it up either in MQSeries Information Center or use the following command on UNIX systems - grep 2030 /usr/include/cmqc.h. The returned string of the last example will give you why the message got redirected to the DLQ. Other codes you may find in the DLQ are as follows: HEXDECIMAL ERROR DESCRIPTION 07EE 2030Message Too Big for Queue 07EF 2031Message Too Big for Queue Manager 0805 2053Queue Full 0835 2101MQ Object Damaged 08AA 2218Message Too Big for Channel Stephan C. Moen [EMAIL PROTECTED] -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Wesley Shaw Sent: Monday, February 17, 2003 7:16 AM To: [EMAIL PROTECTED] Subject: W2K Trigger monitor triggers going to DLQ I have a triggered process where the trigger message is going to the DLQ. Below is the message header. I am trying to figure out the reason code. Anybody decode that for me quicker than I ? (Embedded image moved to file: pic04664.pcx) Wesley Shaw OJRP 10th Floor Work: 804 771 3589 (736-3589) Pager: 888 436 2805 Mobile 804 512 5260 _ For your protection, this e-mail has been scanned for known viruses and damaging content by http://GATEWAYDEFENDER.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
Re: W2K Trigger monitor triggers going to DLQ
Bridgette, Bytes 9-12 of the DLH - which may require reversing for the 'Endianness' of the machine. Peter "Beardsley, Bridgette" To: MQSERIES Sent by: "MQSeries List" <[EMAIL PROTECTED]> cc: Subject: Re: W2K Trigger monitor triggers going to DLQ 17-Feb-2003 14:46 Please respond to "MQSeries List" <[EMAIL PROTECTED]> Mark & Peter, Where are you finding your codes in that screen shot? -Bridgette Beardsley -Original Message- From: Marc Verhiel [mailto:[EMAIL PROTECTED]] Sent: Monday, February 17, 2003 8:32 AM To: [EMAIL PROTECTED] Subject: Re: W2K Trigger monitor triggers going to DLQ >>>I have a triggered process where the trigger message is going to the DLQ. Below is the message header. I am trying to figure out the reason code. Anybody decode that for me quicker than I ?<<< Reason X'109' 265 since it's less than 2000 look it up under MQFB_*...this is MQFB_APPL_CANNOT_BE_STARTED Marc Verhiel Candle Corp. 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: W2K Trigger monitor triggers going to DLQ
Mark & Peter, Where are you finding your codes in that screen shot? -Bridgette Beardsley -Original Message- From: Marc Verhiel [mailto:[EMAIL PROTECTED]] Sent: Monday, February 17, 2003 8:32 AM To: [EMAIL PROTECTED] Subject: Re: W2K Trigger monitor triggers going to DLQ >>>I have a triggered process where the trigger message is going to the DLQ. Below is the message header. I am trying to figure out the reason code. Anybody decode that for me quicker than I ?<<< Reason X'109' 265 since it's less than 2000 look it up under MQFB_*...this is MQFB_APPL_CANNOT_BE_STARTED Marc Verhiel Candle Corp. 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: W2K Trigger monitor triggers going to DLQ
>>>I have a triggered process where the trigger message is going to the DLQ. Below is the message header. I am trying to figure out the reason code. Anybody decode that for me quicker than I ?<<< Reason X'109' 265 since it's less than 2000 look it up under MQFB_*...this is MQFB_APPL_CANNOT_BE_STARTED Marc Verhiel Candle Corp. 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
