| Author | 
		  Message
		 | 
		
		  | smite0hb | 
		  
		    
			  
				 Posted: Thu Sep 07, 2006 9:36 am    Post subject: Sender Channel not starting on Win2000 | 
				     | 
			   
			 
		   | 
		
		
		   Novice
 
 Joined: 19 May 2006 Posts: 24
  
  | 
		  
		    
			  
				| I have a sender channel that will not autoconnect.  MQ starts and all the Q managers start.. The manager for this channel starts..but the sender channel wont start automatically... I cant find any configuration "switch" to set it to autoconnect once the manager comes us.  The queue it connects to on a different machine is up and running.. Any Idea's on where to look?  Thanks | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | xxx | 
		  
		    
			  
				 Posted: Thu Sep 07, 2006 9:38 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Centurion
 
 Joined: 13 Oct 2003 Posts: 137
  
  | 
		  
		    
			  
				there is no switch , you have to set the tranmit queue to trigger ,
 
check the channel and transmit queue , especially the xmit queue setting how it is set for triggering | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | smite0hb | 
		  
		    
			  
				 Posted: Thu Sep 07, 2006 9:47 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Novice
 
 Joined: 19 May 2006 Posts: 24
  
  | 
		  
		    
			  
				| for the queue , the trigger control = on, trigger type = First, trigger depth = 1, trigger message priority = 0, rest of values are blank | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | wschutz | 
		  
		    
			  
				 Posted: Thu Sep 07, 2006 9:51 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Jedi Knight
 
 Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired) 
  | 
		  
		    
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | smite0hb | 
		  
		    
			  
				 Posted: Thu Sep 07, 2006 10:21 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Novice
 
 Joined: 19 May 2006 Posts: 24
  
  | 
		  
		    
			  
				Triggering Info:
 
Alternatively, for WebSphere MQ for UNIX systems and Windows, you can eliminate the need for a process definition by specifying the channel name in the TRIGDATA attribute of the transmission queue.
 
 
I added the channel name in the TRIGDATA attribute of the transmission queue.. and from what I read.. that should do it.. but it still doest start.. 
 
 
I have trigger control = on, type = first, depth =1, message pri = 0 and trigger data = name of channel... 
 
 
I am missing something.. any idea's | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | kevinf2349 | 
		  
		    
			  
				 Posted: Thu Sep 07, 2006 10:30 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand Master
 
 Joined: 28 Feb 2003 Posts: 1311 Location: USA 
  | 
		  
		    
			  
				| What is the depth of the XMITQ? If it is > 1 you will have to start the channel manually for the first time. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | smite0hb | 
		  
		    
			  
				 Posted: Thu Sep 07, 2006 10:32 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Novice
 
 Joined: 19 May 2006 Posts: 24
  
  | 
		  
		    
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | kevinf2349 | 
		  
		    
			  
				 Posted: Thu Sep 07, 2006 10:33 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand Master
 
 Joined: 28 Feb 2003 Posts: 1311 Location: USA 
  | 
		  
		    
			  
				My bad...anything > 0 will need a manual start for the first time.
 
 
Trigger type of FIRST is really...when the depth goes from 0 to 1 | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | smite0hb | 
		  
		    
			  
				 Posted: Thu Sep 07, 2006 11:30 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Novice
 
 Joined: 19 May 2006 Posts: 24
  
  | 
		  
		    
			  
				| I rebooted the win2000 system and MQ started.  The channel is showing inactive status, I put a message in the tranmission queue  and the message just sits in the queue and the channel is showing inactive status.   Trigger control is on , type is First and Depth = 1...  any idea on what I am missing?  Thanks | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | jefflowrey | 
		  
		    
			  
				 Posted: Thu Sep 07, 2006 11:39 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Grand Poobah
 
 Joined: 16 Oct 2002 Posts: 19981
  
  | 
		  
		    
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | kevinf2349 | 
		  
		    
			  
				 Posted: Thu Sep 07, 2006 11:55 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand Master
 
 Joined: 28 Feb 2003 Posts: 1311 Location: USA 
  | 
		  
		    
			  
				
   
	| Quote: | 
   
  
	| type is First and Depth = 1 | 
   
 
 
 
I wrote: 
 
 
   
	| Quote: | 
   
  
	| Trigger type of FIRST is really...when the depth goes from 0 to 1 | 
   
 
 
 
Start the CHANNEL manually for the first time. Either that or clear the transmission queue. After that...all should be well and triggering will work. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | smite0hb | 
		  
		    
			  
				 Posted: Thu Sep 07, 2006 12:28 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Novice
 
 Joined: 19 May 2006 Posts: 24
  
  | 
		  
		    
			  
				| I just want to say thanks.. with the information provided.. I should be able to fix my issue.. and when I do fix it.. I will post the solution.. Thanks again.... | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | smite0hb | 
		  
		    
			  
				 Posted: Mon Sep 11, 2006 12:26 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Novice
 
 Joined: 19 May 2006 Posts: 24
  
  | 
		  
		    
			  
				| The fix was to add the the SYSTEM.CHANNEL.INITQ value in the Initiation queue input box in the triggering sections of my xmit queue. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |