You might want to try this instead of cataloging as a remote database. You might see better performance.
The AIX environment variable EXTSHM can be used to increase the maximum number of shared memory segments to which a process can attach. To use EXTSHM with DB2, do the following: In client sessions: export EXTSHM=ON When starting the DB2 server: export EXTSHM=ON db2set DB2ENVLIST=EXTSHM Db2start -Greg -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Rajkumar Bagavathiappan Sent: Monday, December 29, 2003 9:37 AM To: [EMAIL PROTECTED] Subject: Re: WMQI: Message Flows, Message Set or Execution Group problems Hi Luis, I faced a similar problem in AIXv5.2 with WMQI v2.1 CSD 04, which was due to DB2 problem on AIX, that a process cann't have more than 10 connections if the database is local, as it uses IPC's for DB2 Connections. For analysing the exact problem, try logging the ExceptionList tree from MQOutput Node to a file using Trace node. If the problem is related to DB2, then try cataloging the broker database as a remote database, in which case the DB2 connections are obtained through TCP/IP Sockets. Please refer to the attached text file for information related to changes required for DB2. Regards, Rajkumar Torry Harris Business Solutions Bangalore, India 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
