| Author | 
		  Message
		 | 
		
		  | zlj | 
		  
		    
			  
				 Posted: Mon Nov 17, 2008 12:26 am    Post subject: Auto start channel when a message coming. | 
				     | 
			   
			 
		   | 
		
		
		    Apprentice
 
 Joined: 13 Nov 2008 Posts: 32
  
  | 
		  
		    
			  
				I am so sorry for I have so many questions. I have read another topic about this, but I need more help.
 
 
I have some general idea.
 
 
1.Define a transfer queue with trigger.
 
2.Open trigger, Set type to every,depth to 1.
 
 
That is all I know.
 
Should I define a service for trigger?
 
 
Help me please. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | exerk | 
		  
		    
			  
				 Posted: Mon Nov 17, 2008 2:06 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Jedi Council
 
 Joined: 02 Nov 2006 Posts: 6339
  
  | 
		  
		    
			  
				On the definition of your XMITQ ensure that you have:
 
 
TRIGGER +
 
TRIGTYPE(FIRST) +
 
INITQ('SYSTEM.CHANNEL.INITQ') +
 
TRIGDATA('<CHANNEL NAME>')
 
 
Take the time to read the manuals regarding triggering channels. _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | zlj | 
		  
		    
			  
				 Posted: Mon Nov 17, 2008 5:42 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Apprentice
 
 Joined: 13 Nov 2008 Posts: 32
  
  | 
		  
		    
			  
				
   
	| exerk wrote: | 
   
  
	On the definition of your XMITQ ensure that you have:
 
 
TRIGGER +
 
TRIGTYPE(FIRST) +
 
INITQ('SYSTEM.CHANNEL.INITQ') +
 
TRIGDATA('<CHANNEL NAME>')
 
 
Take the time to read the manuals regarding triggering channels. | 
   
 
 
 
Thank you very much first of all!
 
 
If I dont want to use SYSTEM.CHANNEL.INITQ, how can I define a customer INITQ? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | fjb_saper | 
		  
		    
			  
				 Posted: Mon Nov 17, 2008 7:22 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 18 Nov 2003 Posts: 20768 Location: LI,NY 
  | 
		  
		    
			  
				Any (local) queue will do as long as you run a channel initiator against it.
 
  the intercommunications manual will give you all the clues   _________________ MQ & Broker admin | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | exerk | 
		  
		    
			  
				 Posted: Tue Nov 18, 2008 1:07 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Jedi Council
 
 Joined: 02 Nov 2006 Posts: 6339
  
  | 
		  
		    
			  
				
   
	| zlj wrote: | 
   
  
	| If I dont want to use SYSTEM.CHANNEL.INITQ, how can I define a customer INITQ? | 
   
 
 
 
Why would you not want to use the 'default' initiation queue? Why add in complexity?
 
 
   
	| fjb_saper wrote: | 
   
  
	| Any (local) queue will do as long as you run a channel initiator against it. | 
   
 
 _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | zlj | 
		  
		    
			  
				 Posted: Tue Nov 18, 2008 5:28 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Apprentice
 
 Joined: 13 Nov 2008 Posts: 32
  
  | 
		  
		    
			  
				
   
	| exerk wrote: | 
   
  
	
 
Why would you not want to use the 'default' initiation queue? Why add in complexity?
 
 | 
   
 
 
I have a MQ server which needs to send message to  handred client, so I have the same number remote queue and XMITQ. Should I use SYSTEM.CHANNEL.INITQ support so many XMITQ?
 
 
   
	| fjb_saper wrote: | 
   
  
	
 
Any (local) queue will do as long as you run a channel initiator against it. 
 
 | 
   
 
 
I defined a local queue named CLInitQ, then change the defination of XMITQ, typing INITQ with 'CLInitQ' instead of SYSTEM.CHANNEL.INITQ. When I send a message with a remote queue through XMITQ, channel 
 
was not auto started at all.
 
Do I miss something? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | fjb_saper | 
		  
		    
			  
				 Posted: Tue Nov 18, 2008 9:16 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 18 Nov 2003 Posts: 20768 Location: LI,NY 
  | 
		  
		    
			  
				You missed a lot of things.
 
-  an initq queue can start multiple channels
 
 -  to start any channels you need to run a channel initiator. The qmgr does that at startup for the SYSTEM.CHANNEL.INITQ
 
 -  you have successfully created an alternate channel initq but you did not specify that you ever started a channel initiator against it. So why should it work?
 
 -  the default number of channel initiators a qmgr will accept is limited at 3
 
 -  the main reason to deviate from the default is to run the channel initiator under a non mqm id.
 
 - The second reason to run an additional channel initiator is to load balance the start of channels across multiple initiators on a very busy qmgr with a very short chl idle before shutdown time. I would expect to see this kind of need only in a very unstable network environment
  
 
  intercommunications manual  
 
 
Have fun   _________________ MQ & Broker admin | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |