Re: SHAREPORT Usage and Setup for QSG
Thank you Stefan. I also believe the PORT has to be defined as a shareport in VTAM. Bob Ofeldt -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Stefan Raabe Sent: Wednesday, February 25, 2004 2:42 AM To: [EMAIL PROTECTED] Subject: Re: SHAREPORT Usage and Setup for QSG [Deutsche Boerse Systems :Virus checked] [Deutsche Boerse Systems: Virus checked] Bob, issue START LISTENER TRPTYPE(TCP) PORT(yoursharedport) INDISP(GROUP) on every Queuemanager within your qsg. See MQSC Command Reference for details. Regards, Stefan Ofeldt, Robert [EMAIL PROTECTED] Sent by: MQSeries List [EMAIL PROTECTED] 24.02.2004 14:58 Please respond to MQSeries List To: [EMAIL PROTECTED] cc: (bcc: Stefan Raabe/DBS/GDB) Subject:Re: SHAREPORT Usage and Setup for QSG [Deutsche Boerse Systems:Virus checked] . Can someone please explain how to setup the use of a SHAREPORT in a Q-Sharing Group?My environment will consist of 3 qmgrs in a QSG on the mainframe. I am at V5.3.1 and use TCP/IP.Each qmgr will have it's own PORT and a SHAREPORT for the group. The manual is not clear on how to start a SHAREPORT listener for the group. How do you associate the listener/PORT for the group? Thanking you in advance. Bob Ofeldt This e-mail message and any attachments contain confidential information from Medco Health Solutions, Inc. If you are not the intended recipient, you are hereby notified that disclosure, printing, copying, distribution, or the taking of any action in reliance on the contents of this electronic information is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender by reply message and then delete the electronic message and any attachments. (See attached file: C.htm) - This e-mail message and any attachments contain confidential information from Medco Health Solutions, Inc. If you are not the intended recipient, you are hereby notified that disclosure, printing, copying, distribution, or the taking of any action in reliance on the contents of this electronic information is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender by reply message and then delete the electronic message and any attachments. 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: SHAREPORT Usage and Setup for QSG
Title: Re: SHAREPORT Usage and Setup for QSG Can someone please explain how to setup the use of a SHAREPORT in a Q-Sharing Group? My environment will consist of 3 qmgrs in a QSG on the mainframe. I am at V5.3.1 and use TCP/IP. Each qmgr will have it's own PORT and a SHAREPORT for the group. The manual is not clear on how to start a SHAREPORT listener for the group. How do you associate the listener/PORT for the group? Thanking you in advance. Bob Ofeldt This e-mail message and any attachments contain confidential information from Medco Health Solutions, Inc. If you are not the intended recipient, you are hereby notified that disclosure, printing, copying, distribution, or the taking of any action in reliance on the contents of this electronic information is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender by reply message and then delete the electronic message and any attachments.
Re: MQ 5.2: New code pages
Title: Message Glen can you tell me if the problem below was due to PTF UQ75267 ? Also can you explain why you had to rebuild the Qmgr after the PTF was applied? Also do you know why you ran fine for 3 months before having the problem ? Thanks Bob Ofeldt -Original Message- From: Yeske, Judy [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 24, 2003 12:42 PM To: [EMAIL PROTECTED] Subject: Re: MQ 5.2: New code pages Thanks Glen, I'll pass this along to our Software Install folks ! Judy -Original Message- From: Glen Shubert [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 24, 2003 11:56 AM To: [EMAIL PROTECTED] Subject: Re: MQ 5.2: New code pages We don't have the code pages documented, but I wanted to make you aware of an issue we have had with 5.3. Ensure that you have UQ76767 applied. This PTF supercedes UQ75267, which fixes a page chain corruption problem. We ran fine for approx 3 months, then CHINs started abending with a 5C6, and unable to get messages from the SYSTEM.CHANNEL.SYNCQ, rc=2195. We ended up rebuilding the queue managers to get around this problem, after the maint was applied. Glen Shubert [EMAIL PROTECTED] Associate Director TSYS - MQSeries Technical Support Yeske, Judy [EMAIL PROTECTED] Sent by: MQSeries List [EMAIL PROTECTED] 09/24/2003 09:38 AM Please respond to MQSeries List To:[EMAIL PROTECTED] cc: Subject:MQ 5.2: New code pages Hello, I'm currently migrating my mainframe MQ subsystems from Version 2.1 to Version 5.3 (skipping 5.2). In reviewing the Version 5.2 System Setup Guide, it mentions new code pages being added, including one for Unicode. Does anyone have these documented ? Thanks in advance, Judy Yeske The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. The information may also constitute a legally privileged confidential communication. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you This e-mail message and any attachments contain confidential information from Medco Health Solutions, Inc. If you are not the intended recipient, you are hereby notified that disclosure, printing, copying, distribution, or the taking of any action in reliance on the contents of this electronic information is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender by reply message and then delete the electronic message and any attachments.
Re: MQ V5.3 vs V5.2 Resource Utilization Comparison
Title: Message We are about to start our V5.3.1 upgrade project for ourOS/390 Qmanagers. However, before we start has anyone done a comparison on before/after resource utilization statisticsbetween V5.2 and V5.3.1 ? We would like to get feedback onMIPS and memory utilization and are wondering if anyone could share their experiences (good or bad). Thank you Bob Ofeldt 201-269-4076 This e-mail message and any attachments contain confidential information from Medco Health Solutions, Inc. If you are not the intended recipient, you are hereby notified that disclosure, printing, copying, distribution, or the taking of any action in reliance on the contents of this electronic information is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender by reply message and then delete the electronic message and any attachments.
Re: MQ V5.2 5.3 Compatibility on Mainframe
Could someone please tell me if MQ V5.3 is downward compatible to V5.2 on the mainframe? If I apply early code for v5.3 will utilities and QMGRs using the old v5.2 libraries still run with no problems? Can v5.2 and v5.3 QMGRs in the same Q-sharing group coexist? Will cobol coded programs run OK without recompiling? Thank you Bob Ofeldt MedcoHealth Messaging Infrastructure
Re: MQ Q-Sharing question
Hi, I am sure there are many of you out there that currently use MQ in a Q-Sharing environment. I am knew to Q-Sharing and hope you can help answer some questions for me. I plan to have 2 QMGRs in 1 Q-Sharing group. Each QMGR has 1 CICS region associated with it. Each CICS region has an application program that uses the same Q-alias name. Question is; can these programs use the same alias name to access a particular shared queue on the coupling facility? Can someone point me to a document or manual that explains use of alias qnames in a q-sharing environment? Thank you Bob Ofeldt 201-269-4076 MedcoHealth Messaging Infrastructure
Re: Unsubscribe
Unsubscribe
