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
Re: Backup and Recovery of MQSeries for OS390
One question to ask is What do I do if you go into DR? Can you bring your entire environment back to the point where it went down. If your databases are on other servers (which is where they may should be) your concern may not have to link the Databases to the MQSeries backup. You have to think about your business transaction. THIS CAN GET VERY TRICKIE!! Also...What happens if you have to fail back to your MQSeries back up from Saturday on Tuesday afternoon. Where did Sun, Mon and half of Tuesday go. Where do you get your log from to do forward recovery. food for thought bobbee in boston From: Robert Sloper [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Backup and Recovery of MQSeries for OS390 Date: Wed, 5 Jun 2002 11:49:18 -0500 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] curtdolny@NORTHWESTER cc: NMUTUAL.COMSubject: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 _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. 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
websphere/MQ Best Practice
Can anyone point me to some documentation regarding best practices around the use of MQ and WAS? Clients versus server connections (java bindings)? I believe I read somewhere that it was recommended to run MQ locally on a WAS server as opposed to client channel connections to a remote server, but it might have come to me in a dream. Other than IBM being able to sell more MQ capacity units, are there other advantages/disadvantages? Mark This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. 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: Communication between Non-cluster Q-Managers and a Cluster
Ruud, Thanks again, I think you've told me all I need to know for now, you summed it up in your first paragraph about weighing the cost/effort against the risk. Unfortunately Iam in a support role and cannot influence the configuration to a great degree but I believe our conversation has exposed a reality gap in the expectations of the application development team and what is possible (Our organisation is new to MQ). Armed with this information I am about to drop a big oine on them and sit back and enjoy the fun. Tx again... Keep an eye on the forum if all I suspect is true, it will fall to me to sort out and that will generate more questions 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
Re: Win/2K QMGR problem
I am currently struggling with this now. I did install MQ locally but not with a admin id and I can only access the queue manager via MMC Explorer, this is still not satisfactory I like to run my scripts via runmqsc on the box. When I connect to the queue manager via terminal server I still get the queue manager not available. Rick are you saying that buy me reinstalling using an Admin id that this will run the queue manager in a global namespace and it will work through terminal server ? Greg Mabrito IMS and MQ Software Support (210)913-3985 D-03-E IBM Certified Specialist - Websphere MQ The opinions herein are solely Greg's and are not necessarily the opinion of USAA. -Original Message- From: Rick Tiedemann/Ontario/IBM [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 8:42 AM To: [EMAIL PROTECTED] Subject: Re: Win/2K QMGR problem Did you install MQ and MMC under an administrator id, did you use Microsoft Terminal Server ?. I originally installed MQSeries using Terminal Server and experienced the same problems. IBM does not support Terminal server so once I re-installed MQ Series from a administrator id everything was fine. Rick Tiedemann IBM Global Services [EMAIL PROTECTED] (519) 747-7000 x37301 Rick Tsujimoto rtsujimoto_consultant@CUSATo: [EMAIL PROTECTED] .CANON.COMcc: Sent by: MQSeries List Subject: Win/2K QMGR problem [EMAIL PROTECTED] 06/05/2002 11:35 AM Please respond to MQSeries List 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 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: Pub/Sub in MQSI topology
Kulbir, If you have multiple brokers already, you simply need to group those brokers into a collective (done on the Topology tab of the Control Center) and the brokers will share subscriptions and publications. What actually happens is that when a subscription request is received by one broker (say broker1), that broker will register itself as subscriber on the same topic/filter with all the other brokers in the collective. With that in place, if a message is published on that topic/filter to any broker, the broker (broker1) will get the message (since it's subscribed) and pass it along to any client registered with it. This helps optimize network traffic. You just need to understand that publications aren't really passed around to all brokers but are passed around based on who's subscribed. The Planning and Install guide has some additional information on Broker networks and collectives. Hope this helps. Lanny Lanny Heidenfelder MQSeries/WMQI Instructor and Developer IBM Learning Services [EMAIL PROTECTED] Kulbir S. Thind [EMAIL PROTECTED]@AKH-WIEN.AC.AT on 06/06/2002 09:25:57 AM Please respond to MQSeries List [EMAIL PROTECTED] Sent by:MQSeries List [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Pub/Sub in MQSI topology Hi, Although I have been using MQSI for some time I have never used the Publish/Subscribe features yet and therefore have a design question. If we had a topology of MQSI brokers inter-connected and we wanted to implement pub/sub on them would we be able to configure MQSI to replicate publications and subscriptions automatically between the MQSI brokers or would we have to design and develop our system to do that? Regards, Kulbir. 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
Greg, You're going to have to uninstall MQ, then reinstall it via the console, PC Anywhere, VNC or set it up for remote admin. Terminal Services cannot be used for direct administration. Also, the userid you use for installation will have to have admin rights. Mabrito, Greg Greg.Mabrito@UTo: [EMAIL PROTECTED] SAA.COM cc: Sent by: Subject: Re: Win/2K QMGR problem MQSeries List MQSERIES@AKH-W ien.AC.AT 06/06/2002 10:11 AM Please respond to MQSeries List I am currently struggling with this now. I did install MQ locally but not with a admin id and I can only access the queue manager via MMC Explorer, this is still not satisfactory I like to run my scripts via runmqsc on the box. When I connect to the queue manager via terminal server I still get the queue manager not available. Rick are you saying that buy me reinstalling using an Admin id that this will run the queue manager in a global namespace and it will work through terminal server ? Greg Mabrito IMS and MQ Software Support (210)913-3985 D-03-E IBM Certified Specialist - Websphere MQ The opinions herein are solely Greg's and are not necessarily the opinion of USAA. -Original Message- From: Rick Tiedemann/Ontario/IBM [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 8:42 AM To: [EMAIL PROTECTED] Subject: Re: Win/2K QMGR problem Did you install MQ and MMC under an administrator id, did you use Microsoft Terminal Server ?. I originally installed MQSeries using Terminal Server and experienced the same problems. IBM does not support Terminal server so once I re-installed MQ Series from a administrator id everything was fine. Rick Tiedemann IBM Global Services [EMAIL PROTECTED] (519) 747-7000 x37301 Rick Tsujimoto rtsujimoto_consultant@CUSATo: [EMAIL PROTECTED] .CANON.COMcc: Sent by: MQSeries List Subject: Win/2K QMGR problem [EMAIL PROTECTED] 06/05/2002 11:35 AM Please respond to MQSeries List 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 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
Reinstalling via an admin id will definitely let you use traditional commands and also use MQ Explorer. I am not sure what results you will have via Terminal Server. I guess you will have to try it out and see. I use PC Anywhere to access these servers remotely but terminal server would be much better if it works. I also use MMC fro my PC and remotely administer queue managers on these servers (e.g. starting stopping channels and administering queues) but you cannot stop and start queue managers in this way. Rick Tiedemann IBM Global Services [EMAIL PROTECTED] (519) 747-7000 x37301 Mabrito, Greg Greg.Mabrito@USATo: [EMAIL PROTECTED] A.COM cc: Sent by: MQSeriesSubject: Re: Win/2K QMGR problem List MQSERIES@AKH-WIE N.AC.AT 06/06/2002 10:11 AM Please respond to MQSeries List I am currently struggling with this now. I did install MQ locally but not with a admin id and I can only access the queue manager via MMC Explorer, this is still not satisfactory I like to run my scripts via runmqsc on the box. When I connect to the queue manager via terminal server I still get the queue manager not available. Rick are you saying that buy me reinstalling using an Admin id that this will run the queue manager in a global namespace and it will work through terminal server ? Greg Mabrito IMS and MQ Software Support (210)913-3985 D-03-E IBM Certified Specialist - Websphere MQ The opinions herein are solely Greg's and are not necessarily the opinion of USAA. -Original Message- From: Rick Tiedemann/Ontario/IBM [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 8:42 AM To: [EMAIL PROTECTED] Subject: Re: Win/2K QMGR problem Did you install MQ and MMC under an administrator id, did you use Microsoft Terminal Server ?. I originally installed MQSeries using Terminal Server and experienced the same problems. IBM does not support Terminal server so once I re-installed MQ Series from a administrator id everything was fine. Rick Tiedemann IBM Global Services [EMAIL PROTECTED] (519) 747-7000 x37301 Rick Tsujimoto rtsujimoto_consultant@CUSATo: [EMAIL PROTECTED] .CANON.COMcc: Sent by: MQSeries List Subject: Win/2K QMGR problem [EMAIL PROTECTED] 06/05/2002 11:35 AM Please respond to MQSeries List 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 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: Supp pac MP1B: CSV016I REQUESTED MODULE MQ1150 IS NOT EXECUTABL E
BDY.RTF Description: RTF file
Re: websphere/MQ Best Practice
* *** platform1(W2K)* * platfom2 (MVS) * MQSERVER1 * * MQSERVER2* * * WAS (and applications) * * * (dynamic queues are created)* (local queue) X.SERVER.QUEUE * * a remote queue (X.REQUEST.QUEUE)* (a program gets the message, executes* * * and puts the reply to dynamic queue with * * * the qmanager name: MQSERVER2.)* *** Hello Mark, This is an example only. The key concept here is the dynamic queues. In my opinion this is a very good usage for WAS-MQ connection. Think this for a while, Mark. If you have questions, welcome. Emre KUNT [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 4:47 PM To: [EMAIL PROTECTED] Subject: websphere/MQ Best Practice Can anyone point me to some documentation regarding best practices around the use of MQ and WAS? Clients versus server connections (java bindings)? I believe I read somewhere that it was recommended to run MQ locally on a WAS server as opposed to client channel connections to a remote server, but it might have come to me in a dream. Other than IBM being able to sell more MQ capacity units, are there other advantages/disadvantages? Mark This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. 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
Integrating J2EE and Non-J2EE Publish/Subscribe
We are using MA0C Pub/Sub service pack. So far we have been publishing events only to non-java, non-j2ee applications. So it was easy for these non-j2ee, non-java applications to get the events. But now we are trying to integrate this with WebLogic JMS pub/sub. How do we do this? Even if we dont integrate with weblogic JMS, how can a java program (using the mqseries java api), strip the data portion from the message. The data part of the buffer for a pub/sub message contains the name/value pair - how do they ignore or process it? Any help appreciated. Thanks Ramnath 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
Title: Backup and Recovery of MQSeries for OS390 We are following the same strategy as Rebecca. And as long as I can keep system designers convinced that MQ is a messaging mechanism,NOT a message database, we'll just do MAKEDEFS, fuzzy backups and weekly pack dumps. Our DR policy says we recover to the previous Sunday night, so that is not a problem. Bill -Original Message-From: Jose, Prince [mailto:[EMAIL PROTECTED]]Sent: Tuesday, June 04, 2002 2:26 PMTo: [EMAIL PROTECTED]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
2019 and unreleased connections
I hope this isn't related to my other post... We have a websphere application that is client channel connected to a remote queue manager (both client and mgr are 5.2). This application has a servlet (agent) that is scheduled to inspect a queue for incoming work and process those messages. The servlet is creating the queue manager object, doing a connect, open, query current queue depth, and processes any messages that might be waiting. This process works great during peak hours, however, during off-hours when there is relatively little activity we have issues. It appears the servlet is receiving spuratic 2019 errors (invalid handle) on the queue depth query, and proceeds to close, disconnect, and terminate. However, the socket connection is maintained and the queue manager continues to see an active channel. As the next and the next servlet gets scheduled, the number of active channels grows from the queue manager perspective. If we force garbage-collection, these stray connections go away. Reverse-engineering the MQ client code seems to indicate that the 2019 error is actually coming from the queue manager and not the client code, so something is happening with the client's reaction to the error - maybe saying I don't need to disconnect because I lost the connection anyway. Any thoughts? Mark This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. 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: Backup and Recovery of MQSeries for OS390
Title: RE: Backup and Recovery of MQSeries for OS390 Thanks for all who responded. That was my point too. If the data in transit is not very critical (in our case the data in transit are querries like Rebecca's situation and it is not valid after specific time) is there any other reason, why I should backup pagesets, logs and bootstrap? In case of an MQ failure/ disaster, I can start MQ from the scratch, if I have the backup of object definition right? Thanks Again, Prince -Original Message- From: Bullock, Rebecca (CSC) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 9:32 PM To: [EMAIL PROTECTED] Subject: 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] curtdolny@NORTHWESTER cc: NMUTUAL.COM 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
Re: Win/2K QMGR problem
Rick - Actually, you can use the MQ Service snap-in remotely. From the MQ Service MMC console on your PC (or any MMC console) select Console | Add/Remove Snap-In... On the Add/Remove Snap-in dialog box click the Add button and then select the MQSeries Services snap-in from the list. It will prompt you for a server name. Put in the name of the server you wish to administer (or leave it blank if you want a snap-in for the local server). You can now use the snap-in just as if you were logged on locally to the box. This, of course, assumes you have the appropriate permissions. If you admin several MQ servers, you can build a custom MMC console with a snap-in for each server. Save it under a different name and then create a shortcut to the mmc file. When you need to stop or start a queue manager, just pull up this console and go right to the one you want. You can also do this for the MQ Explorer snap-in as well. - Steve Gies -Original Message- From: Rick Tiedemann/Ontario/IBM [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 7:35 AM To: [EMAIL PROTECTED] Subject: Re: Win/2K QMGR problem Reinstalling via an admin id will definitely let you use traditional commands and also use MQ Explorer. I am not sure what results you will have via Terminal Server. I guess you will have to try it out and see. I use PC Anywhere to access these servers remotely but terminal server would be much better if it works. I also use MMC fro my PC and remotely administer queue managers on these servers (e.g. starting stopping channels and administering queues) but you cannot stop and start queue managers in this way. Rick Tiedemann IBM Global Services [EMAIL PROTECTED] (519) 747-7000 x37301 Mabrito, Greg Greg.Mabrito@USATo: [EMAIL PROTECTED] A.COM cc: Sent by: MQSeriesSubject: Re: Win/2K QMGR problem List MQSERIES@AKH-WIE N.AC.AT 06/06/2002 10:11 AM Please respond to MQSeries List I am currently struggling with this now. I did install MQ locally but not with a admin id and I can only access the queue manager via MMC Explorer, this is still not satisfactory I like to run my scripts via runmqsc on the box. When I connect to the queue manager via terminal server I still get the queue manager not available. Rick are you saying that buy me reinstalling using an Admin id that this will run the queue manager in a global namespace and it will work through terminal server ? Greg Mabrito IMS and MQ Software Support (210)913-3985 D-03-E IBM Certified Specialist - Websphere MQ The opinions herein are solely Greg's and are not necessarily the opinion of USAA. -Original Message- From: Rick Tiedemann/Ontario/IBM [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 8:42 AM To: [EMAIL PROTECTED] Subject: Re: Win/2K QMGR problem Did you install MQ and MMC under an administrator id, did you use Microsoft Terminal Server ?. I originally installed MQSeries using Terminal Server and experienced the same problems. IBM does not support Terminal server so once I re-installed MQ Series from a administrator id everything was fine. Rick Tiedemann IBM Global Services [EMAIL PROTECTED] (519) 747-7000 x37301 Rick Tsujimoto rtsujimoto_consultant@CUSATo: [EMAIL PROTECTED] .CANON.COMcc: Sent by: MQSeries List Subject: Win/2K QMGR problem [EMAIL PROTECTED] 06/05/2002 11:35 AM Please respond to MQSeries List 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
Re: Backup and Recovery of MQSeries for OS390
GGGHH But now lets get in the little bitty Disney boat and take a trip across the magical river to Financial Transaction land where customers will nail you to a cross because their 4.5 billion settlement transaction from one institution to another institution gets lost 5 minutes prior to the FED closing because you are in DR mode. What do you do. Of course this is fictitious because we are in Walt's country. BUT... if you are on the MF you have dual logging and have an offsite hot fiber connected recovery site. BUT...what do you OFTEN (and I stress often) do when you are running on a distribute platform. Redundencey is the answer but how many places are you in where it's a NICE IDEA But, you know, with the financial budget, Well. we'll just cross our fingers and pray. bobbee From: Jose, Prince [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Backup and Recovery of MQSeries for OS390 Date: Thu, 6 Jun 2002 13:02:06 -0400 Thanks for all who responded. That was my point too. If the data in transit is not very critical (in our case the data in transit are querries like Rebecca's situation and it is not valid after specific time) is there any other reason, why I should backup pagesets, logs and bootstrap? In case of an MQ failure/ disaster, I can start MQ from the scratch, if I have the backup of object definition right? Thanks Again, Prince -Original Message- From: Bullock, Rebecca (CSC) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 9:32 PM To: [EMAIL PROTECTED] Subject: 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] curtdolny@NORTHWESTER cc: NMUTUAL.COMSubject: Re: Backup and Recovery of MQSeries for OS390 Sent by:
Queue manager aliases and remote queue defintions
Hi everyone, This doubt is regarding the uses of the remote queue defintions vs queue manager aliases. One of the most basic uses of queue manager aliases (according to the manual) is that the application does not need to change the name of the queue manager which it would be putting in the MQOD structure and still get away with sending messages to different queue managers according to the values in the queue manager alias defintion. My doubt is using remote queue definitions also the application can still send a message to any queue manager it wants to without changing anything in the application. It will only put messages to the remote queue definition..and the transfer will take place again to any queue manager value in the remote queue defintion. I think we can reduce the total number of objects created when we are talking of multi hopping using queue manager aliases and all as compared to trying to acheive the same functionality using remote queue defintions...But otherwise is there some other particular advantage by using the queue manager alias? Or am I missing something in these assumptions? Thanks in advance. Kind Regards Aby Philip 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
Steve, I prefer using PC Anywhere/VNC/Terminal Services when I need to access Win/NT/2000 directly, or Candle's CMW when remote access will do. Thanks anyway. GIES, STEVE STEGIE@SAFECO.To: [EMAIL PROTECTED] COM cc: Sent by: Subject: Re: Win/2K QMGR problem MQSeries List MQSERIES@AKH-W ien.AC.AT 06/06/2002 01:59 PM Please respond to MQSeries List Rick - Actually, you can use the MQ Service snap-in remotely. From the MQ Service MMC console on your PC (or any MMC console) select Console | Add/Remove Snap-In... On the Add/Remove Snap-in dialog box click the Add button and then select the MQSeries Services snap-in from the list. It will prompt you for a server name. Put in the name of the server you wish to administer (or leave it blank if you want a snap-in for the local server). You can now use the snap-in just as if you were logged on locally to the box. This, of course, assumes you have the appropriate permissions. If you admin several MQ servers, you can build a custom MMC console with a snap-in for each server. Save it under a different name and then create a shortcut to the mmc file. When you need to stop or start a queue manager, just pull up this console and go right to the one you want. You can also do this for the MQ Explorer snap-in as well. - Steve Gies -Original Message- From: Rick Tiedemann/Ontario/IBM [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 7:35 AM To: [EMAIL PROTECTED] Subject: Re: Win/2K QMGR problem Reinstalling via an admin id will definitely let you use traditional commands and also use MQ Explorer. I am not sure what results you will have via Terminal Server. I guess you will have to try it out and see. I use PC Anywhere to access these servers remotely but terminal server would be much better if it works. I also use MMC fro my PC and remotely administer queue managers on these servers (e.g. starting stopping channels and administering queues) but you cannot stop and start queue managers in this way. Rick Tiedemann IBM Global Services [EMAIL PROTECTED] (519) 747-7000 x37301 Mabrito, Greg Greg.Mabrito@USATo: [EMAIL PROTECTED] A.COM cc: Sent by: MQSeriesSubject: Re: Win/2K QMGR problem List MQSERIES@AKH-WIE N.AC.AT 06/06/2002 10:11 AM Please respond to MQSeries List I am currently struggling with this now. I did install MQ locally but not with a admin id and I can only access the queue manager via MMC Explorer, this is still not satisfactory I like to run my scripts via runmqsc on the box. When I connect to the queue manager via terminal server I still get the queue manager not available. Rick are you saying that buy me reinstalling using an Admin id that this will run the queue manager in a global namespace and it will work through terminal server ? Greg Mabrito IMS and MQ Software Support (210)913-3985 D-03-E IBM Certified Specialist - Websphere MQ The opinions herein are solely Greg's and are not necessarily the opinion of USAA. -Original Message- From: Rick Tiedemann/Ontario/IBM [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 8:42 AM To: [EMAIL PROTECTED] Subject: Re: Win/2K QMGR problem Did you install MQ and MMC under an administrator id, did you use Microsoft Terminal Server ?. I originally installed MQSeries using Terminal Server and experienced the same problems. IBM does not support Terminal server so once I re-installed MQ Series from a administrator id everything was fine. Rick Tiedemann IBM Global Services [EMAIL PROTECTED] (519) 747-7000 x37301 Rick Tsujimoto rtsujimoto_consultant@CUSATo: [EMAIL PROTECTED] .CANON.COMcc: Sent by: MQSeries List Subject: Win/2K QMGR problem [EMAIL PROTECTED] 06/05/2002 11:35 AM Please respond to MQSeries List 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 -
Re: Win/2K QMGR problem
Steve, Thanks for the info. This is excellent. I always prefer to use a gui on my workstation to administer server apps - rather than working directly on the server (whether physically in front or via remote control). We always could do this with the MQ Explorer MMC, but were not aware of how to do this with the MQ Services MMC - it was rather annoying. We will definitely make use of this. Thanks. Tim. -Original Message- From: GIES, STEVE [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 1:59 PM To: [EMAIL PROTECTED] Subject: Re: Win/2K QMGR problem Rick - Actually, you can use the MQ Service snap-in remotely. From the MQ Service MMC console on your PC (or any MMC console) select Console | Add/Remove Snap-In... On the Add/Remove Snap-in dialog box click the Add button and then select the MQSeries Services snap-in from the list. It will prompt you for a server name. Put in the name of the server you wish to administer (or leave it blank if you want a snap-in for the local server). You can now use the snap-in just as if you were logged on locally to the box. This, of course, assumes you have the appropriate permissions. If you admin several MQ servers, you can build a custom MMC console with a snap-in for each server. Save it under a different name and then create a shortcut to the mmc file. When you need to stop or start a queue manager, just pull up this console and go right to the one you want. You can also do this for the MQ Explorer snap-in as well. - Steve Gies -Original Message- From: Rick Tiedemann/Ontario/IBM [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 7:35 AM To: [EMAIL PROTECTED] Subject: Re: Win/2K QMGR problem Reinstalling via an admin id will definitely let you use traditional commands and also use MQ Explorer. I am not sure what results you will have via Terminal Server. I guess you will have to try it out and see. I use PC Anywhere to access these servers remotely but terminal server would be much better if it works. I also use MMC fro my PC and remotely administer queue managers on these servers (e.g. starting stopping channels and administering queues) but you cannot stop and start queue managers in this way. Rick Tiedemann IBM Global Services [EMAIL PROTECTED] (519) 747-7000 x37301 Mabrito, Greg Greg.Mabrito@USATo: [EMAIL PROTECTED] A.COM cc: Sent by: MQSeriesSubject: Re: Win/2K QMGR problem List MQSERIES@AKH-WIE N.AC.AT 06/06/2002 10:11 AM Please respond to MQSeries List I am currently struggling with this now. I did install MQ locally but not with a admin id and I can only access the queue manager via MMC Explorer, this is still not satisfactory I like to run my scripts via runmqsc on the box. When I connect to the queue manager via terminal server I still get the queue manager not available. Rick are you saying that buy me reinstalling using an Admin id that this will run the queue manager in a global namespace and it will work through terminal server ? Greg Mabrito IMS and MQ Software Support (210)913-3985 D-03-E IBM Certified Specialist - Websphere MQ The opinions herein are solely Greg's and are not necessarily the opinion of USAA. -Original Message- From: Rick Tiedemann/Ontario/IBM [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 8:42 AM To: [EMAIL PROTECTED] Subject: Re: Win/2K QMGR problem Did you install MQ and MMC under an administrator id, did you use Microsoft Terminal Server ?. I originally installed MQSeries using Terminal Server and experienced the same problems. IBM does not support Terminal server so once I re-installed MQ Series from a administrator id everything was fine. Rick Tiedemann IBM Global Services [EMAIL PROTECTED] (519) 747-7000 x37301 Rick Tsujimoto rtsujimoto_consultant@CUSATo: [EMAIL PROTECTED] .CANON.COMcc: Sent by: MQSeries List Subject: Win/2K QMGR problem [EMAIL PROTECTED] 06/05/2002 11:35 AM Please respond to MQSeries List 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
Re: Queue manager aliases and remote queue defintions
Qmgr alias's give you indirection over the qmgr name. Qremotes give you indirection over both the qmgr name and the q name. With a qmgr alias, the program must supply the destination queue name. If it changes, then either the program must use a different queue name or a qalias must be created at the destination qmgr (which defeats the purpose of reducing object quantities). Qmgr aliases are most useful for applications that obtain the destination queue name from the reply-to-queue and for the intermediate qmgrs in multi-hop message routes. You should also be aware that there are also OAM implications if you reference a remote qmgr on the open as opposed to opening a qremote. With a qremote, the qremote name is subjected to the OAM. Otherwise, the XMITQ name is subjected to the OAM. In essence, it means your applications must have write access to the XMITQ, which is potentially a huge security exposure. -Original Message- From: Philip, Aby [SMTP:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 11:47 AM To: [EMAIL PROTECTED] Subject: Queue manager aliases and remote queue defintions Hi everyone, This doubt is regarding the uses of the remote queue defintions vs queue manager aliases. One of the most basic uses of queue manager aliases (according to the manual) is that the application does not need to change the name of the queue manager which it would be putting in the MQOD structure and still get away with sending messages to different queue managers according to the values in the queue manager alias defintion. My doubt is using remote queue definitions also the application can still send a message to any queue manager it wants to without changing anything in the application. It will only put messages to the remote queue definition..and the transfer will take place again to any queue manager value in the remote queue defintion. I think we can reduce the total number of objects created when we are talking of multi hopping using queue manager aliases and all as compared to trying to acheive the same functionality using remote queue defintions...But otherwise is there some other particular advantage by using the queue manager alias? Or am I missing something in these assumptions? Thanks in advance. Kind Regards Aby Philip 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: Design ???
I believe unlimited client attach software for OS390 is free (aka included with OS390 license). You used to be able to download it free from IBM. -Original Message- From: Brian S. Crabtree [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 9:20 PM To: [EMAIL PROTECTED] Subject: 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 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
AMQ6004 6138
All: I have an application with C++ on AIX 4.3.3 connecting to MQ5.2. The application is running 'normal' except that AMQ6004 and AMQ6138 error messages are generated in the /var/mqm/errors directory. Any experience in dealing with this problem? Thanks. Jerry [EMAIL PROTECTED] Cell: (626) 524 - 2554 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: 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...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. IBM doesn't provide any other way to push messages from OS/390. As for the logical reason, perhaps you have answered that yourself. Why not let clients (Linux/VM in my case) connect directly to the OS/390 managed queue? Clients certainly can Pull messages OS/390. The advisability of doing so tends to be customer specific. It's the kind of advice for which you might pay a consultant big $. It's also a feature for which you will pay IBM additional $. You can glean quite a bit by researching the listserv archives, as that topic has been discussed numerous times before. The considerations run the gamut, including performance, scalability, security, system administration, problem diagnosis, availability, etc. The obvious one that usually surfaces is the additional cost of the OS/390 client attach feature compared with the cost of concentrator hub. -Original Message- From: Lindsay, William (USPC.PCT.Hopewell) [SMTP:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 6:04 PM To: [EMAIL PROTECTED] 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
Re: Design ???
Darryl, I believe people are referring to the OS/390 Client Attach Feature (CAF) for MQSeries, which is not free (and has never been). The MQSeries Client is (still) freely downloadable for most platforms. However, some platforms do not support MQSeries Client applications, including OS/390 and AS/400 (amongst others). So, if you want to use MQSeries functionality on OS/390 in any form, you will need to buy at least the base MQSeries product. Stefan From: Sakach, Darryl J. [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Design ??? Date: Thu, 6 Jun 2002 19:55:16 -0400 I believe unlimited client attach software for OS390 is free (aka included with OS390 license). You used to be able to download it free from IBM. -Original Message- From: Brian S. Crabtree [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 9:20 PM To: [EMAIL PROTECTED] Subject: 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 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 _ 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
Server Connection
Hello, I have MQ5.2 running on Win2000. From an MQ cilent an application opens up a server-connection channel per an MQI request -- this is a load testing appliocation -- causing many server-connection channels running simultaneously. I can see this from MQ Explorer. Soon MQ can not handle the load any more -- I do not know how many server-connection channels are running -- poping the message up into the EventViewer like, maximum number of channels reached. It also says the number of permitted channels is a configurable parameter in the Queue manager configuration file. Does anyone know how to configure this? Advice will be greatly appreciated. Thanks, Ingi Hong AmerisourceBergen Corporation Technical Support Capacity Planning Email: [EMAIL PROTECTED] Office: 714) 385-4331 Fax: 714) 704-7031 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: Design ???
I think the CAF for os/390 is usually in the neighborhood of about 900.00 per month - I know it depends on certain variables but I believe we are a fairly average shop and that was what I heard for us. so if utilizing the CAF would make your design easier spend the money... as for Why not let clients (Linux/VM in my case) connect directly to the OS/390 managed queue ? seems to me their is no way to let the client know he should pull the messages if its the type of application that just is going to connect and process whatever is there when the application is executed sure why not but using client to pull messages could result in delays of processing if os/390 has messages but is down when you try and connect but was up for awhile after messages where on the queue the 390 could of sent the messages to the unix or whatever box and then trigggered your application or even if not triggered and user driven the messaes are on the local server now and available whereas if 390 is down they are still on 390 and you can not get to them. I am probably wrong and if not definitely overstating the obvious! Go Nets Laker hater here Miller, Dennis [EMAIL PROTECTED]@AKH-WIEN.AC.AT on 06/06/2002 05:58:07 PM Please respond to MQSeries List [EMAIL PROTECTED] Sent by:MQSeries List [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: 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...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. IBM doesn't provide any other way to push messages from OS/390. As for the logical reason, perhaps you have answered that yourself. Why not let clients (Linux/VM in my case) connect directly to the OS/390 managed queue? Clients certainly can Pull messages OS/390. The advisability of doing so tends to be customer specific. It's the kind of advice for which you might pay a consultant big $. It's also a feature for which you will pay IBM additional $. You can glean quite a bit by researching the listserv archives, as that topic has been discussed numerous times before. The considerations run the gamut, including performance, scalability, security, system administration, problem diagnosis, availability, etc. The obvious one that usually surfaces is the additional cost of the OS/390 client attach feature compared with the cost of concentrator hub. -Original Message- From: Lindsay, William (USPC.PCT.Hopewell) [SMTP:[EMAIL PROTECTED]] Sent: Wednesday, June 05, 2002 6:04 PM To: [EMAIL PROTECTED] 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 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: Server Connection
Ingi, You would require to update your qm.ini file to add following lines in channel stanza: CHANNELS: MaxChannels=256 MaxActiveChannels=256 Hope that will help. -Arif -Original Message- From: Ingi Hong [mailto:[EMAIL PROTECTED]] Sent: Friday, June 07, 2002 10:04 AM To: [EMAIL PROTECTED] Subject: Server Connection Hello, I have MQ5.2 running on Win2000. From an MQ cilent an application opens up a server-connection channel per an MQI request -- this is a load testing appliocation -- causing many server-connection channels running simultaneously. I can see this from MQ Explorer. Soon MQ can not handle the load any more -- I do not know how many server-connection channels are running -- poping the message up into the EventViewer like, maximum number of channels reached. It also says the number of permitted channels is a configurable parameter in the Queue manager configuration file. Does anyone know how to configure this? Advice will be greatly appreciated. Thanks, Ingi Hong AmerisourceBergen Corporation Technical Support Capacity Planning Email: [EMAIL PROTECTED] Office: 714) 385-4331 Fax: 714) 704-7031 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 message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. CREDIT SUISSE GROUP and each legal entity in the CREDIT SUISSE FIRST BOSTON or CREDIT SUISSE ASSET MANAGEMENT business units of CREDIT SUISSE FIRST BOSTON reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. Unless otherwise stated, any pricing information given in this message is indicative only, is subject to change and does not constitute an offer to deal at any price quoted. Any reference to the terms of executed transactions should be treated as preliminary only and subject to our formal written confirmation. 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
Peter Henningsen/Australia/IBM is out of the office.
I will be out of the office starting June 7, 2002 and will not return until June 11, 2002. I have gone home ill today, and 10/06/02 is a Public Holiday here. Please call mobile if urgent (0412.729.961). 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: Server Connection
Open your MQSeries Services panel, RIGHT CLICK on the Queue Manager and click on the PROPERTIES tab then click on CHANNELS tab and there you will find the MAX CHANNELS and MAX ACTIVE CHANNELS . Emile Kearns Software Futures -Original Message- From: Ingi Hong [mailto:[EMAIL PROTECTED]] Sent: 07 June 2002 04:04 To: [EMAIL PROTECTED] Subject: Server Connection Hello, I have MQ5.2 running on Win2000. From an MQ cilent an application opens up a server-connection channel per an MQI request -- this is a load testing appliocation -- causing many server-connection channels running simultaneously. I can see this from MQ Explorer. Soon MQ can not handle the load any more -- I do not know how many server-connection channels are running -- poping the message up into the EventViewer like, maximum number of channels reached. It also says the number of permitted channels is a configurable parameter in the Queue manager configuration file. Does anyone know how to configure this? Advice will be greatly appreciated. Thanks, Ingi Hong AmerisourceBergen Corporation Technical Support Capacity Planning Email: [EMAIL PROTECTED] Office: 714) 385-4331 Fax: 714) 704-7031 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
