MA88 V5.2 compatibility with applications built based on JDK 1.1.8 and JDK 1.2.x
I am in the process of upgrading some v5.1 machines running the MA88 V5.1 extension to MQSeries V5.2, including the MA88 extension. Our current application environment includes applications that were built based on code generated using older versions of the SDK. Releases mentioned by the applications groups include IBM JDK 1.1.8 and Java 1.2.x. It appears, according to the documentation that the current MA88 extension requires the 1.3.1 versions of the IBM and Sun SDKs. Products mentioned that are in use are: WebLogic, Corba, and VisiBroker. Questions * Will installing the new JDK per the requirements cause any issues with the applications? * Will the applications built based on the older JDKs need to be recreated or modified in any way to run on the new MA88 product? * Any other issues that I have not mentioned that I need to consider? Thanks in advance, Dan Jones ING Americas Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
MQSeries in highly available and fault tolerant/failover environments
We are currently working on a project that calls for setting up MQSeries in, if not a highly available environment, one that is fault tolerant and provides for failover capabilities. While I don't believe they are using such products as AIX HACMP or the Sun equivalent for Solaris, they are using something called BigIP in an attempt to provide some level of failover. In was my plan to use [MQSeries] clustering to provide some basic function of 'high' availability, however, I don't know how that will behave in some of these failover environments. Questions + Any experience in using MQSeries in 'high availability' environments? + Aware of any documentation [i.e. white papers, redbooks, product manuals, etc] that could provide me with some useful guidance in providing MQSeries 'high availability'? Thanks in advance, Dan Jones Systems Consultant ING AMERICAS - Technology Management Office IA3 - Integrated Americas Adaptive Architecture TOMORROW. TODAY @ING 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
Application using MQ Java/JMS MA88 and PubSub MA0C
Background We have an application group that is trying to build an MQSeries Publish/Subscribe application, using JMS as the front-end. Publish/Subscribe is something new for our company and I [MQSeries support/administration technician] am unfamiliar[though learning] with the whole Java/JMS interface. The application program [attached below] is, I'm being told, basically an IBM sample program. The developer is right now just trying to get something to work, which has been a struggle. Her ultimate goal is to [Java/JMS defines attached below]: + using normal queue connection factories and queue definitions, put a message on a queue [which is working]; + using topic connnection factories and topic definitions, publish the contents of that message [which seems to be working]; + using topic connnection factories and topic definitions, subscribe to that and retrieve that message [which does not appear to be working]. Environment + Solaris machine running the user [JMS] application and the following software: - MQ Client 5.2.05 - MQ MA88 5.2.05 + Solaris machine set up with an MQSeries QManager and the MQ MA0C PubSub Support Pack - MQ Server 5.1.07 [Understanding this is an unsupported product - Upgrade scheduled] - MQ MA0C [July 2002] Current Issue In reviewing some queues that were previously defined and some that appear to have been dynamically created, it appears that the Publish has completed successfully. However, in reviewing the SYSTEM.JMS.REPORT.QUEUE, I found a message that indicates the 'RegSub' function is failing [see attached file for sample] with, MSPSComp=2, MQPSReason=3076, and MQPSerrorid=2085. The queue it appears to be unable to find is; SYSTEM.JMS.ND.2002121619391544. Though that queue does not exist, there are others similarly name; SYSTEM.JMS.ND.2002 . Any input on what I am missing would be greatly appreciated. Thanks in advance Software code (See attached file: TransferMessages.java) View of the error message (See attached file: JMS_PubSub.gif) Input to Java/JMS administration program (See attached file: JNDISetup) Dan Jones Systems Consultant ING AMERICAS - Technology Management Office Email: [EMAIL PROTECTED] IA3 - Integrated Americas Adaptive Architecture TOMORROW. TODAY @ING TransferMessages.java Description: Binary data <> JNDISetup Description: Binary data
Dan Jones/EIC/ING-FSI-NA is out of the office.
I will be out of the office starting 10/28/2002 and will not return until 11/04/2002. I will be out of the office in training from Oct 28 through Nov 1. I will be available for emergencies via my pager and reviewing voice mail and email morning and evening. All problems 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
Dan Jones/EIC/ING-FSI-NA is out of the office.
I will be out of the office starting 07/29/2002 and will not return until 08/05/2002. I will be out of the office from July 29 through August 2. I will be unavailable during this period. All problems 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
Any compatibility issues with MQSI v1.? - 2.01 running with MQSeries v5.2
We are upgrading our distributed MQSeries environment from MQSeries v5.1 to v5.2. We are currently using MQSI v1.? and MQSI v2.01. I have looked for compatility issues doc but have been unsuccessful. Can anyone provide an insight as to whether the old MQSI versions will have an issue with MQSeries v5.2? Thanks in advance, Dan Jones ING Americas 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
Dan Jones/EIC/ING-FSI-NA is out of the office.
I will be out of the office starting 07/03/2002 and will not return until 07/09/2002. I will be out of the office from July 3 through July 8. I will be unavailable during this period. All problems 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
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: Problem with MQSeries Bridge running on CICS TS Version 1.3.0 and interfacing with MQSeries 5.2
Stefan, Thanks for the information. Changing the 'data' queue to be shareable seems to have resolved the issue. It appears that I was confused by the context of the message CSQC711E. I had been looking through the manual for something to verify that I was looking at the right queue. I interpreted the ...711E message to mean that the bridge queue was specified in the 'Q=' parameter of the CKBR startup [what I believed to be the CSCQPARM values at CICS startup]; which it would seem points to what is known as the 'init' queue. Thanks again for your help, Dan Jones ING Americas Stefan Sievert cc: Sent by: MQSeriesSubject: Re: Problem with MQSeries Bridge running on CICS TS Version List 1.3.0 and interfacing with MQSeries 5.2 05/09/2002 05:23 PM Please respond to MQSeries List Daniel, you are talking about your INITQ, which is probably not the queue that the message "CSQC755E CKBR 0018720 Bridge queue is not shareable, queue must be defined with the SHARE option" is referring to. I don't know much about the CICS bridge but isn't this message referring to the bridge request queue (what you call the data queue), not the initiation queue the trigger monitor transaction CKTI is running against? Just guessing, Stefan >From: "Daniel G. Jones" <[EMAIL PROTECTED]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Problem with MQSeries Bridge running on CICS TS Version 1.3.0 and > interfacing with MQSeries 5.2 >Date: Thu, 9 May 2002 16:25:24 -0600 > >Problem: > >A preexisting InitQ was in place and functional with a previous >application. It was defined with the following share options: >Permit shared access . . . : N Y=Yes,N=No >Default share option . . . : E E=Exclusive,S=Shared. > > Another group wanted to use the same CICS region, so when I defined the >new data queue, I directed it to the same InitQ and process already in use. >When data was placed on the new data queue, we got the following error >messages in the CICS msgusr DD: >CSQC700I CKBR 0018720 IBM MQSeries for OS/390 V5.2 - CICS bridge. >Copyright(c) 1997,2000 IBM. All rights reserved >CSQC725I CKBR 0018720 Messages on bridge queue are not persistent by >default >CSQC726I CKBR 0018720 Bridge queue backout count not hardened >CSQC727I CKBR 0018720 Bridge queue defined with MSGDLVSQ(PRIORITY) but >should be FIFO for efficiency >CSQC755E CKBR 0018720 Bridge queue is not shareable, queue must be defined >with the SHARE option > >We then tried setting up an additional InitQ in CICS via the CICS panels >and the CKTI transaction. I defined that queue to MQSeries and changed the >data queue to point to the new InitQ. This queue by the way was defined >as: >Permit shared access . . . : Y Y=Yes,N=No >Default share option . . . : S E=Exclusive,S=Shared. > >I still got the same CSQC messages shown above > >In accordance with the messages manual, I changed the InitQ [same one >defined in the IQ= parm in CICS] that I had directed the data queue at to: >Permit shared access . . . : Y Y=Yes,N=No >Default share option . . . : S E=Exclusive,S=Shared. > >The CICS region was then recycled. > >Still go the same error messages. > >The QMgr was then recycled. > >Still getting the same messages. > >Any ideas on what I'm missing?? > > >Thanks in advance, > >Dan Jones >ING Americas > >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 _ 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 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
Problem with MQSeries Bridge running on CICS TS Version 1.3.0 and interfacing with MQSeries 5.2
Problem: A preexisting InitQ was in place and functional with a previous application. It was defined with the following share options: Permit shared access . . . : N Y=Yes,N=No Default share option . . . : E E=Exclusive,S=Shared. Another group wanted to use the same CICS region, so when I defined the new data queue, I directed it to the same InitQ and process already in use. When data was placed on the new data queue, we got the following error messages in the CICS msgusr DD: CSQC700I CKBR 0018720 IBM MQSeries for OS/390 V5.2 - CICS bridge. Copyright(c) 1997,2000 IBM. All rights reserved CSQC725I CKBR 0018720 Messages on bridge queue are not persistent by default CSQC726I CKBR 0018720 Bridge queue backout count not hardened CSQC727I CKBR 0018720 Bridge queue defined with MSGDLVSQ(PRIORITY) but should be FIFO for efficiency CSQC755E CKBR 0018720 Bridge queue is not shareable, queue must be defined with the SHARE option We then tried setting up an additional InitQ in CICS via the CICS panels and the CKTI transaction. I defined that queue to MQSeries and changed the data queue to point to the new InitQ. This queue by the way was defined as: Permit shared access . . . : Y Y=Yes,N=No Default share option . . . : S E=Exclusive,S=Shared. I still got the same CSQC messages shown above In accordance with the messages manual, I changed the InitQ [same one defined in the IQ= parm in CICS] that I had directed the data queue at to: Permit shared access . . . : Y Y=Yes,N=No Default share option . . . : S E=Exclusive,S=Shared. The CICS region was then recycled. Still go the same error messages. The QMgr was then recycled. Still getting the same messages. Any ideas on what I'm missing?? Thanks in advance, Dan Jones ING Americas 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
