| Author | 
		  Message | 
  		
  		
		     Topic: command to display pids associated to particular queue mager | 
  		
  		
		  vpkjadhav
  
	  	  Replies: 3 Views: 3630
  | 
		   Forum: General IBM MQ Support   Posted: Sat Dec 09, 2006 3:16 pm   Subject: command to display pids associated to particular queue mager | 
  		
  		
		  | display qstatus(Qname) type(handle) all | 
  		
  		
		     Topic: FMC00013E communication error with reason code 2103 | 
  		
  		
		  vpkjadhav
  
	  	  Replies: 7 Views: 8045
  | 
		   Forum: Workflow Engines - IBM MQ Workflow & Business Process Choreographer   Posted: Thu Nov 02, 2006 7:50 am   Subject: 2103 error | 
  		
  		
		  You are right. We are having a Client Concentrator set up.  We are having 3 profiles
 ABCX
 ABCGRP01   ABCSYSX   ABCQMX    ABC
 
 ABCY
 ABCGRP01   ABCSYSY  ABCQMY   ABC
 
 ABCZ
 ABCGRP01   ABCSYSZ  AB ... | 
  		
  		
		     Topic: FMC00013E communication error with reason code 2103 | 
  		
  		
		  vpkjadhav
  
	  	  Replies: 7 Views: 8045
  | 
		   Forum: Workflow Engines - IBM MQ Workflow & Business Process Choreographer   Posted: Tue Oct 31, 2006 8:08 am   Subject: web applications and web client | 
  		
  		
		  Thx for post. The post talks about Two web clients running on different WAS Servers which is alright. However let me sum up the issue 
 
 3.5
 
 uses Java API which allows only one configuration to ac ... | 
  		
  		
		     Topic: FMC00013E communication error with reason code 2103 | 
  		
  		
		  vpkjadhav
  
	  	  Replies: 7 Views: 8045
  | 
		   Forum: Workflow Engines - IBM MQ Workflow & Business Process Choreographer   Posted: Thu Oct 26, 2006 9:07 am   Subject: reason code 2103 | 
  		
  		
		  The WAS version is 5.1.1.5 . When a weblient is installed on WAS server,
 any other application installed on same WAS server can not get connectivity. Is this a limitation of WF 3.6?
 
 I tried to mak ... | 
  		
  		
		     Topic: FMC00013E communication error with reason code 2103 | 
  		
  		
		  vpkjadhav
  
	  	  Replies: 7 Views: 8045
  | 
		   Forum: Workflow Engines - IBM MQ Workflow & Business Process Choreographer   Posted: Thu Oct 26, 2006 4:08 am   Subject: FMC00013E communication error with reason code 2103 | 
  		
  		
		  After WF migration from 3.5 to 3.6 Webclient is installed on websphere. When first application connects , it gets connection. When second application tries to connected above error is thrown. 
 
 The  ... | 
  		
  		
		     Topic: WBI collaborations for order management 1.0 installation err | 
  		
  		
		  vpkjadhav
  
	  	  Replies: 0 Views: 2048
  | 
		   Forum: WebSphere Interchange Server + Adapters   Posted: Wed Oct 04, 2006 4:22 pm   Subject: WBI collaborations for order management 1.0 installation err | 
  		
  		
		  | I am trying to install order management collaboration v1.0 on windows xp. I have ICS 4.3.0.0 and DB2 8.2. Java 1.4.2 , JDBC connector 2.6, MQ Worflow connector 2.8 installed on my system. The installe ... | 
  		
  		
		     Topic: cluster functioning error | 
  		
  		
		  vpkjadhav
  
	  	  Replies: 4 Views: 5280
  | 
		   Forum: Clustering   Posted: Thu Aug 03, 2006 4:17 pm   Subject: server1 que manegr  is throwing error | 
  		
  		
		  MQPUT1 on object '' returned 2085 Unknown object name..
 
 above error is echoed from server1 (que manager) | 
  		
  		
		     Topic: cluster functioning error | 
  		
  		
		  vpkjadhav
  
	  	  Replies: 4 Views: 5280
  | 
		   Forum: Clustering   Posted: Thu Aug 03, 2006 3:56 pm   Subject: cluster error | 
  		
  		
		  | Yes put is successful.  A message put in DEMOQ cluster que on SERVER1 can be acessed from SERVER1. However it is not accessible from SERVER 2 or 3, 4 . DEMOQ is hosted on all qmanagers (SERVER1,2,..4  ... | 
  		
  		
		     Topic: cluster functioning error | 
  		
  		
		  vpkjadhav
  
	  	  Replies: 4 Views: 5280
  | 
		   Forum: Clustering   Posted: Thu Aug 03, 2006 3:35 pm   Subject: cluster functioning error | 
  		
  		
		  | I am trying to create a cluster network on one system. This is a cluster gui demo available from IBM support pack. There are four servers SERVER1, SERVER2, SERVER3, SERVER4  as queue mangers and CLIEN ... |