Re: MQ53 and SSL
Do I understand the following correctly, I have to apply for Personal Certificate at a Certification Authority and then assign this to my QMGR? Emile Kearns Software Futures -Original Message- From: Ruud van Zundert [mailto:[EMAIL PROTECTED]] Sent: 05 June 2002 05:05 To: [EMAIL PROTECTED] Subject: Re: MQ53 and SSL Emile - have a look at the Beta download site for MQ V5.3. I've just looked, and there's a new manual entitled 'WebSphere MQ Security Version 5.3'. Regards ... Ruud -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Emile Kearns Sent: 05 June 2002 13:34 To: [EMAIL PROTECTED] Subject: MQ53 and SSL Hi all, Which manual describes how to implement SSL on Windows 2000? Emile Kearns Software Futures
Dan Jones/EIC/ING-FSI-NA is out of the office.
I will be out of the office starting 06/05/2002 and will not return until 06/17/2002. I will be out of the office on vacation from June 5 through June14. I will be unavailable during this period. All problem issues should be routed through your appropriate HelpDesk infrastructure. General inquiries can be directed to Dale Hultgren at 612.342.7314. 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: Terminal Service and MQSeries
Folkes, In case you do have to manage a Queue Manager node on a citrix or Terminal Server remotely (other than using the remote MMC and Command Server setup or writing a client compiled admin tool) is to use VNC. Make sure that the Server is installed and working on the Citrix server and connect via the VNC client. You will have complete access to the Citrix/Terminal Servers Desktop. It might not be supported but it does work. VNC Developers are obviously doing something different compared with other tools that are out there. Useful FAQ URL for this and other topics. http://www-3.ibm.com/software/ts/mqseries/support/faqs/v5_tech.html Hope this helps, John --- Rick Tsujimoto <[EMAIL PROTECTED]> wrote: > MQers, > > fyi > - Forwarded by Richard > Tsujimoto/NewYork/CanonUSA on 06/05/2002 02:59 > PM - > > "mqseries" > [EMAIL PROTECTED] > ibm.com> cc: > Sent by: Subject: > dick 12689,7TD > "Dick > Hamilton" > <[EMAIL PROTECTED] > .com> > > > 06/05/2002 > 01:31 PM > > > > > > Richard, > > Here is the item that we discussed. > > Dick Hamilton > > 153.PRB > Abstract > Microsoft Terminal Server/Services does NOT work > with MQSeries. > > MQSeries and Windows Terminal Server should co-exist > on the same machine > and each > should function correctly. However, the use or > management of MQSeries > Server through a > terminal session is known not to work, and as such > is not supported. > > > > MQSeries Level 2 Support - Distributed Platforms > Email: [EMAIL PROTECTED] > Need online help? Go to http://www.ibm.com/support/ > Need publications? Go to > http://www.ibm.com/shop/publications/order > > When sending mail to MQSERIES, please add the Level > 2 rep's name and the > Problem Number in the Subject line. > ** In addition please call the support center and > update your problem > record. (or electronically update your problem > record) ** > > 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! - Official partner of 2002 FIFA World Cup http://fifaworldcup.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
Re: Backup and Recovery of MQSeries for OS390
Actually, I think it all depends... Here, the vast majority of messages are transient, used to send inquiries and answers back and forth between web servers and the backend (OS/390) databases (mostly IDMS, but also some VSAM). So, we made a conscious decision to NOT do the full blown backup stuff. Basically, once a week, a CSQUTIL runs on OS/390 and takes a snapshot of the definitions, using MAKEDEF. These are stored in sequential datasets. When we have a disaster (Thank God, only in testing so far), we delete and redefine the LOGs and BSDSes from scratch, then reload the definitions from the MAKEDEFs. Then take it from there on an empty queue manager. All other data is recoverable using either database recovery mechanisms or, in a few cases, application logs that redrive transactions. Some applications maintain database flags that say "Hey -- the backend (or the frontend) isn't updated" and these flags are left in place until a positive confirmation is received from the other end that the update is in place, at which point the flag is changed; for these applications, if a double update were to occur, there would be no problem since the data would simply replace itself with identical data. As I said, it all depends on what your applications are doing and how they were designed. And, as I said, the vast majority of our traffic is transient. I will admit that I dread the day that an application comes along that has to use the full blown recovery scenario :-) Best regards, Rebecca Rebecca Bullock Computer Sciences Corporation Educational Testing Service Account Princeton, NJ 08541 e-mail: [EMAIL PROTECTED][EMAIL PROTECTED] -Original Message- From: Robert Sloper [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 12:49 PM To: [EMAIL PROTECTED] Subject: Re: Backup and Recovery of MQSeries for OS390 I have often wondered about the value of taking comprehensive backups of MQSeries files. Most commonly, MQSeries is used as a transient data store and as such does not contain much 'data at rest'. If a backup is taken of all the components, i.e. pagesets, logs and bootstraps, every Sunday at 1pm, what value will this backup be at 1am on a Monday if in the interim many of the messages that would be returned to the queues on a recovery have already been processed and the data is now 'at rest' in say a DB2 database and will potentially be processed again after a restore. To achieve a comprehensive 'backup' you would have to not only snapshot the MQ components, but also ALL other sub-system datasets that could be affected if any one of the sub-systems have a problem. This would include potentially, MQ and at least the mainframe database, if not also databases on the other locations where the message data was generated in the first place. What would be needed is 'simultaneous, synchronous recovery' of all components which would be very difficult to achieve. Curt Dolny To: [EMAIL PROTECTED] Subject:Re: Backup and Recovery of MQSeries for OS390 Sent by: MQSeries List <[EMAIL PROTECTED] AT> 06/05/02 10:26 AM Please respond to MQSeries List We bring down the OS/390 queue managers at 1:00 AM on Sundays. Then we FDR Dump the disks that contain the page datasets, logs and bootstrap datasets. Then restart the queue managers. Total down time for the queue managers is averaging around 15 minutes. It's not 24x7 availability, but our clients are okay with this. Regards, Curt -Original Message- From: PJose [SMTP:[EMAIL PROTECTED]] Sent: Tuesday, June 04, 2002 1:26 PM To: MQSERIES Cc: PJose Subject:Backup and Recovery of MQSeries for OS390 Hello, I spent some time reading the red book MQSeries backup and Recovery And was interested in knowing how most shops handle backup and recovery for MQSeries for OS390. Do you backup pagesets? And how often? Do you take a fuzzy backup or back it up while qmgr is down? Or do you just backup the object definitions and let qmgr restart from the scratch. I know the backup plan will be differing from shop to shop but i was trying to get a general idea. Thanks in advance for all inputs. Prince ** People are just about as happy as they make up their minds to be. Abraham Lincoln ** 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
Re: Design ???
William There are two main reasons 1. The client attachment feature costs extra on OS/390 - I dont know how much but I am sure that it is unreasonable - ie more than the cost of the hub server 2. Misbehaving clients cause problems on the QM boxes so it is easier to handle problems on a client concentrator which is just routing messages than on a server that is doing the work Brian S. Crabtree EAI Consultant - Original Message - From: Lindsay, William (USPC.PCT.Hopewell) To: [EMAIL PROTECTED] Sent: Wednesday, June 05, 2002 9:04 PM Subject: Design ??? Is it customary (beneficial ??) to have OS/390 processes write to a locally managed queue and to have that queue pushed by the server to a remote managed queue (hub) in a non OS/390 environment. Why not let clients (Linux/VM in my case) connect directly to the OS/390 managed queue ? I'm sure there's a logical reason why OS/390 support is refusing to allow this. Seems we will have to pay double the charges to utilize 2 queues. Bill Lindsay Retirement Group Technology 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
Design ???
Is it customary (beneficial ??) to have OS/390 processes write to a locally managed queue and to have that queue pushed by the server to a remote managed queue (hub) in a non OS/390 environment. Why not let clients (Linux/VM in my case) connect directly to the OS/390 managed queue ? I'm sure there's a logical reason why OS/390 support is refusing to allow this. Seems we will have to pay double the charges to utilize 2 queues. Bill Lindsay Retirement Group Technology
Re: COD delivery problem on AIX
Title: COD delivery problem on AIX How you doing Brant? I think the problem is the COD is being put to the xmitq but under the userid that's in the MQMD. You have to grant that userid put access to the xmitq. - Original Message - From: Gutekunst, Brant To: [EMAIL PROTECTED] Sent: Wednesday, June 05, 2002 12:09 PM Subject: COD delivery problem on AIX I am having a problem with report messages on AIX 4.3 MQ 5.2. I receive messages from QM1 with MQMD.Feedback set to MQFB_COA+MQFB_COD, MQMD.ReplyToQueue = DESTQ and MQMD.ReplyToQMgr = QM2 Initially, the report messages were hitting my Dead Letter Queue. I created a QMgr Alias with QREMOTE(QM2) and RQMNAME(QM1). My intention was to force messages destined for QM2 to QM1 where they would be forwarded properly. COA messages are now being delivered, but the COD messages are still ending up on my DLQ with MQRC = 2035 (MQRC_NOT_AUTHORIZED). I also get an Event message at this time with MQ_OPEN_NOT_AUTHORIZED. If I run runmqdlq with a retry rule, the messages are transmitted successfully. How can I figure out what I'm failing to open and which process is failing to open it? Any hints will be appreciated. This one is starting to drive me crazy.
Re: COD delivery problem on AIX
Additionally, if you want to know the object for which the 2035 message was issued, look on the appropriate error log for the qmgr and there should be a corresponding 8077 message which specifies the object name. -Original Message-From: Alessandro Brezzi [mailto:[EMAIL PROTECTED]]Sent: Wednesday, June 05, 2002 2:37 PMTo: [EMAIL PROTECTED]Subject: Re: COD delivery problem on AIXHi,do you put a valid userId in the message header before MQPut in QM1? Do you put the message with PASS_IDENTITY?HTHAlessandroAt 12:09 PM 6/5/2002 -0400, you wrote: I am having a problem with report messages on AIX 4.3 MQ 5.2. I receive messages from QM1 with MQMD.Feedback set to MQFB_COA+MQFB_COD, MQMD.ReplyToQueue = DESTQ and MQMD.ReplyToQMgr = QM2Initially, the report messages were hitting my Dead Letter Queue. I created a QMgr Alias with QREMOTE(QM2) and RQMNAME(QM1). My intention was to force messages destined for QM2 to QM1 where they would be forwarded properly.COA messages are now being delivered, but the COD messages are still ending up on my DLQ with MQRC = 2035 (MQRC_NOT_AUTHORIZED). I also get an Event message at this time with MQ_OPEN_NOT_AUTHORIZED.If I run runmqdlq with a retry rule, the messages are transmitted successfully. How can I figure out what I'm failing to open and which process is failing to open it? Any hints will be appreciated. This one is starting to drive me crazy. 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: COD delivery problem on AIX
Brant, the difference between the two reports is a subtle one. COA's are generated by the queue manager itself, (usually) using the mqm userId to put them to the replyToQueue. COD's, however, are generated by the agent process that is started on behalf of each application that issues an MQCONN call. As soon as you MQGET the application message (and commit, if syncpointed), ie. you perform a destructive get, the agent process will produce the delivery report message, at this time using the userId that the application runs with. Now, this userId needs to have permission to open and put to the replyToQueue (and the transmission queue, if it leaves your QMgr). I would suspect that your application doesn't run with the mqm userId. Hope this makes some sense, Stefan >From: "Gutekunst, Brant" <[EMAIL PROTECTED]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: COD delivery problem on AIX >Date: Wed, 5 Jun 2002 12:09:50 -0400 > >I am having a problem with report messages on AIX 4.3 MQ 5.2. > >I receive messages from QM1 with MQMD.Feedback set to MQFB_COA+MQFB_COD, >MQMD.ReplyToQueue = DESTQ and MQMD.ReplyToQMgr = QM2 > >Initially, the report messages were hitting my Dead Letter Queue. I >created >a QMgr Alias with QREMOTE(QM2) and RQMNAME(QM1). My intention was to force >messages destined for QM2 to QM1 where they would be forwarded properly. > >COA messages are now being delivered, but the COD messages are still ending >up on my DLQ with MQRC = 2035 (MQRC_NOT_AUTHORIZED). I also get an Event >message at this time with MQ_OPEN_NOT_AUTHORIZED. > >If I run runmqdlq with a retry rule, the messages are transmitted >successfully. > >How can I figure out what I'm failing to open and which process is failing >to open it? >Any hints will be appreciated. This one is starting to drive me crazy. _ Send and receive Hotmail on your mobile device: http://mobile.msn.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: COD delivery problem on AIX
Hello Brant, The event message tells you what failed and why. You should easily see the qmgr/queue it was tring to open and the userid it was using. The somewhat tricky part is the MQIACF_OPEN_OPTIONS (0x03FE) parameter which is immediately followed by the open options passed to the failed MQOPEN() call. In this particular case I think you'll see that the failed open is using the original msg's id to open the return xmitq using MQOO_OUTPUT | MQOO_PASS_IDENTITY_CONTEXT (0x0110). i.e. you should see 03FE 0110 about 3/4 the way into the event msg while browsing it. To make it work as expected I think you'll need to give that id (from original msg) put and pass_id rights to the xmitq. Regards, Marty Frasier Middleware Architect - GWA Project Office home office: t/l 470.9828 voice mail: tie-line 722.4775; external 804.327.4775 e-mail: [EMAIL PROTECTED] "Gutekunst, Brant" <[EMAIL PROTECTED]> Sent by: MQSeries List <[EMAIL PROTECTED]> 06/05/2002 12:09 PM Please respond to MQSeries List To: [EMAIL PROTECTED] cc: Subject:COD delivery problem on AIX I am having a problem with report messages on AIX 4.3 MQ 5.2. I receive messages from QM1 with MQMD.Feedback set to MQFB_COA+MQFB_COD, MQMD.ReplyToQueue = DESTQ and MQMD.ReplyToQMgr = QM2 Initially, the report messages were hitting my Dead Letter Queue. I created a QMgr Alias with QREMOTE(QM2) and RQMNAME(QM1). My intention was to force messages destined for QM2 to QM1 where they would be forwarded properly. COA messages are now being delivered, but the COD messages are still ending up on my DLQ with MQRC = 2035 (MQRC_NOT_AUTHORIZED). I also get an Event message at this time with MQ_OPEN_NOT_AUTHORIZED. If I run runmqdlq with a retry rule, the messages are transmitted successfully. How can I figure out what I'm failing to open and which process is failing to open it? Any hints will be appreciated. This one is starting to drive me crazy. 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: Backup and Recovery of MQSeries for OS390
I have often wondered about the value of taking comprehensive backups of MQSeries files. Most commonly, MQSeries is used as a transient data store and as such does not contain much 'data at rest'. If a backup is taken of all the components, i.e. pagesets, logs and bootstraps, every Sunday at 1pm, what value will this backup be at 1am on a Monday if in the interim many of the messages that would be returned to the queues on a recovery have already been processed and the data is now 'at rest' in say a DB2 database and will potentially be processed again after a restore. To achieve a comprehensive 'backup' you would have to not only snapshot the MQ components, but also ALL other sub-system datasets that could be affected if any one of the sub-systems have a problem. This would include potentially, MQ and at least the mainframe database, if not also databases on the other locations where the message data was generated in the first place. What would be needed is 'simultaneous, synchronous recovery' of all components which would be very difficult to achieve. Curt Dolny To:[EMAIL PROTECTED] Subject:Re: Backup and Recovery of MQSeries for OS390 Sent by: MQSeries List <[EMAIL PROTECTED] AT> 06/05/02 10:26 AM Please respond to MQSeries List We bring down the OS/390 queue managers at 1:00 AM on Sundays. Then we FDR Dump the disks that contain the page datasets, logs and bootstrap datasets. Then restart the queue managers. Total down time for the queue managers is averaging around 15 minutes. It's not 24x7 availability, but our clients are okay with this. Regards, Curt -Original Message- From: PJose [SMTP:[EMAIL PROTECTED]] Sent: Tuesday, June 04, 2002 1:26 PM To: MQSERIES Cc: PJose Subject:Backup and Recovery of MQSeries for OS390 Hello, I spent some time reading the red book MQSeries backup and Recovery And was interested in knowing how most shops handle backup and recovery for MQSeries for OS390. Do you backup pagesets? And how often? Do you take a fuzzy backup or back it up while qmgr is down? Or do you just backup the object definitions and let qmgr restart from the scratch. I know the backup plan will be differing from shop to shop but i was trying to get a general idea. Thanks in advance for all inputs. Prince ** People are just about as happy as they make up their minds to be. Abraham Lincoln BDY.RTF Description: RTF file
Re: COD delivery problem on AIX
Hi, do you put a valid userId in the message header before MQPut in QM1? Do you put the message with PASS_IDENTITY? HTH Alessandro At 12:09 PM 6/5/2002 -0400, you wrote: I am having a problem with report messages on AIX 4.3 MQ 5.2. I receive messages from QM1 with MQMD.Feedback set to MQFB_COA+MQFB_COD, MQMD.ReplyToQueue = DESTQ and MQMD.ReplyToQMgr = QM2 Initially, the report messages were hitting my Dead Letter Queue. I created a QMgr Alias with QREMOTE(QM2) and RQMNAME(QM1). My intention was to force messages destined for QM2 to QM1 where they would be forwarded properly. COA messages are now being delivered, but the COD messages are still ending up on my DLQ with MQRC = 2035 (MQRC_NOT_AUTHORIZED). I also get an Event message at this time with MQ_OPEN_NOT_AUTHORIZED. If I run runmqdlq with a retry rule, the messages are transmitted successfully. How can I figure out what I'm failing to open and which process is failing to open it? Any hints will be appreciated. This one is starting to drive me crazy. 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: Win/2K QMGR problem
I believe this is a security issue. What I did was to completely unstall MQSeries and clean up registry and then reinstall MQSeries with Domain Administrator Special User ID (password never expired). It should work. Jeff -Original Message- From: Rick Tsujimoto [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 11:35 AM To: [EMAIL PROTECTED] Subject: Win/2K QMGR problem I have a strange one here. Installed MQ/Win2K V5.2.1 with CSD4. I can create a qmgr via MQ Explorer and it starts up, turns green, and all the other services, e.g. listener, also start. But, the status of the qmgr is "not connected" as per the properties report. A normal qmgr would have additional levels to navigate under the qmgr icon, e.g. a plus sign, but not in my case. Any attempt to issue a "connect" for the qmgr results in message AMQ4043 - MQ Explorer thinks the qmgr is not running. There are no unusal messages in the event viewer, or the MQ error logs. I can create the qmgr via the command line and access it. But, MQ Explorer has a strange view of it, e.g. instead of the green icon, it shows a hatch-like icon and is basically not accessible. I've installed the same software on another Win2K box without any problems. Anyone see anything like this? 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: Win/2K QMGR problem
How does runmqsc react? >From: Rick Tsujimoto <[EMAIL PROTECTED]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Win/2K QMGR problem >Date: Wed, 5 Jun 2002 11:35:11 -0400 > >I have a strange one here. Installed MQ/Win2K V5.2.1 with CSD4. I can >create a qmgr via MQ Explorer and it starts up, turns green, and all the >other services, e.g. listener, also start. But, the status of the qmgr is >"not connected" as per the properties report. A normal qmgr would have >additional levels to navigate under the qmgr icon, e.g. a plus sign, but >not in my case. Any attempt to issue a "connect" for the qmgr results in >message AMQ4043 - MQ Explorer thinks the qmgr is not running. There are no >unusal messages in the event viewer, or the MQ error logs. > >I can create the qmgr via the command line and access it. But, MQ Explorer >has a strange view of it, e.g. instead of the green icon, it shows a >hatch-like icon and is basically not accessible. > >I've installed the same software on another Win2K box without any problems. >Anyone see anything like this? > >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 _ Send and receive Hotmail on your mobile device: http://mobile.msn.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: Win/2K QMGR problem
Rick - It sounds like you are logged onto your Win2K server via Terminal Services. When you do this, you can use the MQ Services MMC as normal, but to use the MQ Explorer MMC you must connect to the queue manager as a client. (Right click Queue Managers, select Show Queue Manager ..., select the Show a remote queue manager option and fill in the appropriate values. Also, when you create the queue manager you need to indicate that you want the ability to administer it remotely. - Steve Gies -Original Message- From: Rick Tsujimoto [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 8:35 AM To: [EMAIL PROTECTED] Subject: Win/2K QMGR problem I have a strange one here. Installed MQ/Win2K V5.2.1 with CSD4. I can create a qmgr via MQ Explorer and it starts up, turns green, and all the other services, e.g. listener, also start. But, the status of the qmgr is "not connected" as per the properties report. A normal qmgr would have additional levels to navigate under the qmgr icon, e.g. a plus sign, but not in my case. Any attempt to issue a "connect" for the qmgr results in message AMQ4043 - MQ Explorer thinks the qmgr is not running. There are no unusal messages in the event viewer, or the MQ error logs. I can create the qmgr via the command line and access it. But, MQ Explorer has a strange view of it, e.g. instead of the green icon, it shows a hatch-like icon and is basically not accessible. I've installed the same software on another Win2K box without any problems. Anyone see anything like this? 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
COD delivery problem on AIX
Title: COD delivery problem on AIX I am having a problem with report messages on AIX 4.3 MQ 5.2. I receive messages from QM1 with MQMD.Feedback set to MQFB_COA+MQFB_COD, MQMD.ReplyToQueue = DESTQ and MQMD.ReplyToQMgr = QM2 Initially, the report messages were hitting my Dead Letter Queue. I created a QMgr Alias with QREMOTE(QM2) and RQMNAME(QM1). My intention was to force messages destined for QM2 to QM1 where they would be forwarded properly. COA messages are now being delivered, but the COD messages are still ending up on my DLQ with MQRC = 2035 (MQRC_NOT_AUTHORIZED). I also get an Event message at this time with MQ_OPEN_NOT_AUTHORIZED. If I run runmqdlq with a retry rule, the messages are transmitted successfully. How can I figure out what I'm failing to open and which process is failing to open it? Any hints will be appreciated. This one is starting to drive me crazy.
Re: Communication between Non-cluster Q-Managers and a Cluster
John - the fact that you've got a queue manager outside of the cluster immediately implies that you cannot make full use of its benefits. In fact, the same 'problem' exists when an application tries to connect to queue manager, say, QM1 whose WLM is then in charge of distributing the messages to cluster queues on queue managers QM2 and QM3. Here, QM1 is a single point of failure, and if it's down, then MQSeries clustering does not help at all - eventhough all 3 queue managers are in the cluster. The application might need to have some additional application logic to try another queue manager, say, QM1B. Similarly, one way to avoid a single point of failure in your scenario would be to have a second queue manager in the cluster to act as a possible gateway. The trouble is, how does the application know whether the MQPUT to the first gateway actually worked - remembering that this is an asynchronous link. You could use COD/COA but I personally don't like using these. So, once you've figured out that the first MQPUT didn't work, then you could send it to the second gateway. Once you've set up the second gateway, the return route to the 'outside' queue manager is automatically managed (provided you've got all the channels set up). In other words, an application connected to a clustered queue manager doing a put to a clustered object defined in both gateways should then be forwarded to the outside queue manager. Your other query regarding how to manage a local copy of a cluster queue: use clustered alias queues as described in Xephon's MQ Update magazine issue number 27, Sep 2001. (I did hear a rumour at the Clustering SIG that there may be a 'fix' to allow a local cluster queue to be WLM'ed. Best to ask IBM). HTH ... regards ... Ruud -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of John Basevi Sent: 05 June 2002 14:39 To: [EMAIL PROTECTED] Subject: Communication between Non-cluster Q-Managers and a Cluster How do I configure a non-cluster Q-Manager to send messages to a cluster of queue managers in a fault tolerant manner aside from creating an overlapping cluster? The way I understand it the sender channel configured on the external Q-Manager explicitly references a particular machine in the cluster as a getway via its connection name. Isnt this a single point of failure? How can we get some fault tolerance into this. Also if the Gateway QM has a local copy of the Queue on it then all the messages will end up on this QM, how can we get the default WLM to assign these across the QMs in the rest of the cluster. Many Tx JB http://www.rac.co.uk http://www.racbusiness.co.uk http://www.bsm.co.uk Any opinions expressed in this e-mail are those of the individual and not necessarily the company. This e-mail and any attachments are confidential to RAC and/or BSM and are solely for use by the intended recipient. If you are not the intended recipient you must not disclose, copy or distribute its contents to any other person nor use its contents in any way. If you have received this e-mail in error please forward a copy of this e-mail to "[EMAIL PROTECTED]". RAC Motoring Services: Registered England 1424399 VAT Reg No. GB 238640945 British School of Motoring: Registered England 291902 VAT Reg No. GB 239505847 Registered Office(s): 1 Forest Road, Feltham, TW 13 7RR This e-mail and any attachments has been scanned for the presence of computer viruses. RAC/BSM accept no responsibility for computer viruses once this e-mail has been transmitted. 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
Win/2K QMGR problem
I have a strange one here. Installed MQ/Win2K V5.2.1 with CSD4. I can create a qmgr via MQ Explorer and it starts up, turns green, and all the other services, e.g. listener, also start. But, the status of the qmgr is "not connected" as per the properties report. A normal qmgr would have additional levels to navigate under the qmgr icon, e.g. a plus sign, but not in my case. Any attempt to issue a "connect" for the qmgr results in message AMQ4043 - MQ Explorer thinks the qmgr is not running. There are no unusal messages in the event viewer, or the MQ error logs. I can create the qmgr via the command line and access it. But, MQ Explorer has a strange view of it, e.g. instead of the green icon, it shows a hatch-like icon and is basically not accessible. I've installed the same software on another Win2K box without any problems. Anyone see anything like this? 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: MQ53 and SSL
Emile - have a look at the Beta download site for MQ V5.3. I've just looked, and there's a new manual entitled 'WebSphere MQ Security Version 5.3'. Regards ... Ruud -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Emile KearnsSent: 05 June 2002 13:34To: [EMAIL PROTECTED]Subject: MQ53 and SSL Hi all, Which manual describes how to implement SSL on Windows 2000? Emile Kearns Software Futures
Re: Backup and Recovery of MQSeries for OS390
BDY.RTF Description: RTF file
Re: MQSI 2.1 - NNSY Formater GUI - Jump to Rules gets MMC Cannot open selected file error
Got the solution from IBM... Hi Paul, Investigating further, I found this to be a known problem that occurs due to an incorrect registry entry. The problem can easily be solved by using regedit to examine HK_LOCAL_MACHINE\SOFTWARE\New Era of Networks\nnsycomps and making sure that "ncompsrootshort" uses the 8.3 filename syntax ie. it should be set to something like - C:\PROGRA~1\IBM\MQSERI~1.2\nnsy rather than the expanded names. . Please let me know if this helps. I tested this and it now works... Paul Dix Northwestern Mutual I.S.-Middleware Tech Support -Original Message- From: DIX, PAUL Sent: Monday, June 03, 2002 2:57 PM To: ViennaListServPost Subject:MQSI 2.1 - NNSY Formater GUI - Jump to Rules gets MMC Cannot open selected file error I'm running MQSI 2.1 CSD#1 on Win 2000 and HP-UX 11.0. In the Neon Formatter GUI, Output Control Panel, I recieve the following message box - Microsoft Management Console - "Cannot open selected file" when I press the "Jump to Rules" button. Any ideas on why I would get this? Thanks in advance for your help... Paul Dix Northwestern Mutual I.S.-Middleware Tech Support 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: MQ53 and SSL
Emile, There is a section covering this in the WebSphere MQ Security manual. Regards, Tim Crossland http://www.cclDesign.com >Emile Kearns <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on >05/06/2002 13:34:21 > >Please respond to MQSeries List <[EMAIL PROTECTED]> > > > >Sent by: MQSeries List <[EMAIL PROTECTED]> > > >To: [EMAIL PROTECTED] >cc: >Subject: MQ53 and SSL > > > > >Hi all, > >Which manual describes how to implement SSL on Windows 2000? > > > >Emile Kearns > >Software Futures _ Join the world s largest e-mail service with MSN Hotmail. http://www.hotmail.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
FW: doorzenden
-Original Message- From: RAVEN, Laurens Sent: mercredi 5 juin 2002 15:57 To: PUFFET, Olivier Subject:doorzenden Dear all, I try to implement a message bean to run under Websphere AE 4.0 My problem is when I configure the application server to handle the custom Service (the extended messaging service) websphere does not find the class com.ibm.cmm.listener.JMSListenerStub. (JMS works fine, the same application server can create jms client beans thus as faras the JMS JARS are concerned they are in the claspath) Any ideas ? Kind regards Laurens Raven C.O.S. Tel (+32) 2 728 32 39 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: Hot/Cold Server and MQAX
Ryan Though I haven't used this particular interface, I'm guessing that like all other interfaces that I can think of, the queue manager name does not have to be specified when identifying a queue on the queue manager that you are connected to. From the documentation queue name is mandatory. Queue manager name is not. If your intent is to use the queue on the queue manager that you connected to, just don't specify queue manager name. If you do I believe it is going to use it literally as the queue manager name as it would if you where using a direct call to MQOPEN. It will not be resolving that name through the channel table the way the connect did. Rick |-+---> | | Ryan Parmenter | | | <[EMAIL PROTECTED]> | | | | | | Sent by: MQSeries List | | | <[EMAIL PROTECTED]> | | | | | | | | | | | | Wednesday June 5, 2002 07:39 AM | | | Please respond to MQSeries List | | | | |-+---> >| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Hot/Cold Server and MQAX | >| We have a hot/cold server set up with a queue manager set up on each box (call the first queue manager HDQ1 and the second queue manager HDQ2). The idea is that if one box goes down, we can use the other box fairly seamlessly. For our VB application using the MQAX dll, this is all fine and good for GETs. We connect to the queue manager using a type of alias like *HDQ. So, it will connect to the queue manager that is currently active (either HDQ1 or HDQ2) and we don't have to change code depending on which box is up. The issue is that when we do PUTs and try to put using *HDQ as the queue manager name, I get error 2086 (MQRC_UNKNOWN_OBJECT_Q_MGR). I can connect just fine using *HDQ, however we are using the distribution list class as we are putting the message into multiple queues. I supply *HDQ as the queue manager name when adding queues to the distribution list and I get the error when I try to call the Open method of the distribution list class. Any insight would be great. Ryan 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
Communication between Non-cluster Q-Managers and a Cluster
How do I configure a non-cluster Q-Manager to send messages to a cluster of queue managers in a fault tolerant manner aside from creating an overlapping cluster? The way I understand it the sender channel configured on the external Q-Manager explicitly references a particular machine in the cluster as a getway via its connection name. Isnt this a single point of failure? How can we get some fault tolerance into this. Also if the Gateway QM has a local copy of the Queue on it then all the messages will end up on this QM, how can we get the default WLM to assign these across the QMs in the rest of the cluster. Many Tx JB http://www.rac.co.uk http://www.racbusiness.co.uk http://www.bsm.co.uk Any opinions expressed in this e-mail are those of the individual and not necessarily the company. This e-mail and any attachments are confidential to RAC and/or BSM and are solely for use by the intended recipient. If you are not the intended recipient you must not disclose, copy or distribute its contents to any other person nor use its contents in any way. If you have received this e-mail in error please forward a copy of this e-mail to "[EMAIL PROTECTED]". RAC Motoring Services: Registered England 1424399 VAT Reg No. GB 238640945 British School of Motoring: Registered England 291902 VAT Reg No. GB 239505847 Registered Office(s): 1 Forest Road, Feltham, TW 13 7RR This e-mail and any attachments has been scanned for the presence of computer viruses. RAC/BSM accept no responsibility for computer viruses once this e-mail has been transmitted. 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
MQ53 and SSL
Hi all, Which manual describes how to implement SSL on Windows 2000? Emile Kearns Software Futures
Re: not able to login to buildtime
Hi Ripu Thanx a lot. I had actually forgotten it. Now I remember my trainer telling us when we attended the MQWorkflow training. Rgds vinodh Ripudaman Singh <[EMAIL PROTECTED]To: [EMAIL PROTECTED] M.COM> cc: Sent by: Subject: Re: not able to login to buildtime MQSeries List 06/05/02 03:20 PM Please respond to MQSeries List Vinod, Login to buildtime as ADMIN with password as 'password' (without the quotes that is) Regards.. Ripu -- Ripudaman Singh Solution Architect, AIM Asia Pacific TET/WIC IBM Certified Solutions Expert - WebSphere MQ, Integrator IBM Software Group, e-business Software Center DLF Plaza Tower, DLF City I, Gurgaon, Haryana 122001 Ph: + 91-124-6540467, Fax: +91-124-6540477 N Vinodh cc: Sent by: MQSeriesSubject: not able to login to buildtime List 05/06/2002 14:52 Please respond to MQSeries List Hi We have installed MQworkflow on win/NT. The installation is fine. But we are not able to login to bulidtime. It is not accepting userid & password as db2admin. plz help us in solving this. Rgds thanx in advance. vinodh 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
Hot/Cold Server and MQAX
We have a hot/cold server set up with a queue manager set up on each box (call the first queue manager HDQ1 and the second queue manager HDQ2). The idea is that if one box goes down, we can use the other box fairly seamlessly. For our VB application using the MQAX dll, this is all fine and good for GETs. We connect to the queue manager using a type of alias like *HDQ. So, it will connect to the queue manager that is currently active (either HDQ1 or HDQ2) and we don't have to change code depending on which box is up. The issue is that when we do PUTs and try to put using *HDQ as the queue manager name, I get error 2086 (MQRC_UNKNOWN_OBJECT_Q_MGR). I can connect just fine using *HDQ, however we are using the distribution list class as we are putting the message into multiple queues. I supply *HDQ as the queue manager name when adding queues to the distribution list and I get the error when I try to call the Open method of the distribution list class. Any insight would be great. Ryan 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: not able to login to buildtime
Vinodh, When you are logging on to the buildtime for the first time, use ADMIN/password as userid/password as that is the default user created in the workflow domain. WindowsNT also provides a facility of Unified Logon which can be activated by defining the corresponding winNT userid as workflow user also. Regards, Rajkumar B THBS, Bangalore - Original Message - From: "N Vinodh" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, June 05, 2002 2:52 PM Subject: not able to login to buildtime > Hi > > We have installed MQworkflow on win/NT. The installation is fine. But we > are not able to login to bulidtime. It is not accepting userid & password > as db2admin. > > plz help us in solving this. > > Rgds > thanx in advance. > > vinodh > > 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
AMI Installation for Windows 95
Dear Friends: We have downloaded Application Messaging Interface (AMI) Support Pacs from IBM website. We have successfully installed this AMI support on Win NT, Win 2000, Win Xp operating system. However, while trying to install AMI on a Windows 95 system, the setup program gives a "SEVERE" message which says that the product can only be installed on Windows 95, 98, ME, NT or 2000 and then exits. Please note that we had installed MQSeries Client 95 on the machine before AMI installation. We shall appreciate if anyone can help us with solving this problem so that we can successfully install the AMI on Windows 95 system. Thanks and Regards, Dr. Prakash G. Bendale Executive Manager - eBusiness eServices Division Rolta India Limited Mumbai, India Tel: 91-22-832, extn. 3724 email: [EMAIL PROTECTED] 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: not able to login to buildtime
Vinod, Login to buildtime as ADMIN with password as 'password' (without the quotes that is) Regards.. Ripu -- Ripudaman Singh Solution Architect, AIM Asia Pacific TET/WIC IBM Certified Solutions Expert - WebSphere MQ, Integrator IBM Software Group, e-business Software Center DLF Plaza Tower, DLF City I, Gurgaon, Haryana 122001 Ph: + 91-124-6540467, Fax: +91-124-6540477 N Vinodh cc: Sent by: MQSeriesSubject: not able to login to buildtime List 05/06/2002 14:52 Please respond to MQSeries List Hi We have installed MQworkflow on win/NT. The installation is fine. But we are not able to login to bulidtime. It is not accepting userid & password as db2admin. plz help us in solving this. Rgds thanx in advance. vinodh 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: not able to login to buildtime
try "ADMIN" "password"! - Original Message - From: "N Vinodh" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, June 05, 2002 10:22 AM Subject: not able to login to buildtime > > Hi > > We have installed MQworkflow on win/NT. The installation is fine. But we > are not able to login to bulidtime. It is not accepting userid & password > as db2admin. > > plz help us in solving this. > > Rgds > thanx in advance. > > vinodh > > 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
not able to login to buildtime
Hi We have installed MQworkflow on win/NT. The installation is fine. But we are not able to login to bulidtime. It is not accepting userid & password as db2admin. plz help us in solving this. Rgds thanx in advance. vinodh 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
Putting message segments as a group
Hello. I am putting a set of message segments which also constitute a Message Group. Every message except the final message is Put with both MQMF_SEGMENT and MQMF_MSG_IN_GROUP. When I put the final message ( i.e. with both MQMF_LAST_SEGMENT and MQMF_LAST_IN_GROUP) I get a reason code of MQRC_INCOMPLETE_MSG. The problem seems to be that the MsgSequenceNumber property of the MQMD is not being incremented when the MsgFlags include MQMF_MSG_IN_GROUP. In fact, the MsgSequenceNumber appears to be reset during each Put - if I manually set the MsgSequenceNumber to an incremented value prior to a Put then, if I subsequently browse the message, the MsgSequenceNumber has been reset to 1. The Offset property of the MQMD is not automatically set either (when grouping and segmenting at the same time), but I can programatically increment this value for each Put successfully. This occurs with both the C and the C++ API. MQSeries 5.2.1 on Win2000, CSD04. What am I doing wrong? thanks Tony P.S. I can successfully Put messages either as a group or as a set of segments. _ Chat with friends online, try MSN Messenger: http://messenger.msn.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
[no subject]
set nodigest set shorthdr info mqseries
Re: File: "LISTSERV REFCARD"
lists
