Re: Any change management tools out their for WMQ objects

2004-01-19 Thread Tony Devitt
** Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ** : The 'saveqmgr' supportpac is the best tool for what you

Any change management tools out their for WMQ objects

2004-01-19 Thread Adiraju, Rao
Title: Any change management tools out their for WMQ objects Hi We have embarked on a "standardisation" path of queue names across various platforms and unfortunately WebSphere MQ doesn't provide any functionality to RENAME the queue (it would have been handy to have this facility). I ha

Re: AMQ6150 MQSeries semaphore is busy

2004-01-19 Thread Jim Nuckolls
It is possible that your system is running on the edge as far as resources (in this case semaphores) are concerned. You might want to start gathering statistics as far as resource usage is concerned and begin to make a case for regen'ing the kernel and increasing your systems resources (shared mem

Re: SYSTEM.JMS.REPORT.QUEUE -- Question

2004-01-19 Thread Nick Dilauro
This may help. http://www-306.ibm.com/software/integration/mqfamily/library/manuals99/csqza w/csqzaw2l.htm Nick -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Mittal, Gaurav Sent: Monday, January 19, 2004 2:42 PM To: [EMAIL PROTECTED] Subject: SYSTEM.JMS.

Re: Problem committing messages

2004-01-19 Thread Thomas Dunlap
Jeff, You should have the MQ systems administrator check out the "Log" options for the queue manager. It sounds like either you log files are not large enough (specified as a number of 4K pages) or you do not have enough log files (primary) to handle the large messages. It is not only a matter of

SYSTEM.JMS.REPORT.QUEUE -- Question

2004-01-19 Thread Mittal, Gaurav
Hi All, Does anyone knows what message is put on SYSTEM.JMS.REPORT.QUEUE ?? We are using WMQ 5.3 with csd4 along with WMQI2.1, predominantly our applications are pub/sub based, with all durable subscriptions. Till recently the depth of report queue used to be 0, but since last one week messages ar

Re: Image backup of a Full Repository QM. Then a restore. Uh-oh

2004-01-19 Thread Ruzi R
Peter, > What is the right way to get QM2FULL to get itself up to date > >REFRESH CLUSTER(CLUSTER1) REPOS(NO) did not do it. You would have to use REPOS(YES) on QM2FULL after altering it so that it is not a full rep. The steps are: 1- Alter QM2FULL REPOS(' ') 2- REFRESH CLUSTER(CLUSTER1) RE

Re: Problem committing messages

2004-01-19 Thread Nick Dilauro
Is there some file size limit controlled by the OS? Is there a message on the qmgr error log? Nick -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Jeff A Tressler Sent: Monday, January 19, 2004 1:35 PM To: [EMAIL PROTECTED] Subject: Problem committing messag

Problem committing messages

2004-01-19 Thread Jeff A Tressler
Our Java application is reading multiple entries in Oracle. Each record is placed in an MQSeries message object. When four messages are created, written and committed the commit fails. When three messages are created, written to the queue and committed the commit succeeds. In our case, the messages

Moving WMQI Config Manager

2004-01-19 Thread Web Sphere
Hi everyone, I've got a scenario as follows: Windows Box W1 hosts the configmgr for Broker B1 on Unix box A1. There are message flows , message sets already deployed on B1. The requirement now is : - To delete the config mgr on W1. - Create a new config mgr on box W2 that will act as the

Yongky Limawan is out of the office.

2004-01-19 Thread Yongky Limawan
I will be out of the office starting 19/01/2004 and will not return until 03/02/2004. Please forward the message to group id RHO.IT.CS.FCS for urgent attention. -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received thi

Jones, Dan -- OOTO, Friday, 16 Jan PTO; Monday, 19 Jan Holiday

2004-01-19 Thread Dan Jones
I will be out of the office starting 01/16/2004 and will not return until 01/20/2004. Calls on problems involving MQSeries or MQSI should be directed to the ING Solutions Center at 800.790.2978. Calls on problems involving MQSeries or MQSI should be directed to the ING Solutions Center at 800.79