| Author | 
		  Message
		 | 
		
		  | pgorak | 
		  
		    
			  
				 Posted: Fri Jul 25, 2003 2:43 am    Post subject: channel not triggered between z/OS and HP-UX | 
				     | 
			   
			 
		   | 
		
		
		    Disciple
 
 Joined: 15 Jul 2002 Posts: 158 Location: Cracow, Poland 
  | 
		  
		    
			  
				Hi all,
 
 
I've set up channels between HP-UX and z/OS so that they're triggered automatically. I use CSQX on z/OS to do this. This was tested and then I defined exactly the same MQSeries objects on different environment.
 
 
In the new environment triggering on z/OS does not work. I have to start the channel z/OS->HP-UX manually. I use SVR - RQSTR pairs.
 
 
Is there anything on z/OS that affects channel triggering, apart from MQSeries definitions?
 
 
Piotr | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mrlinux | 
		  
		    
			  
				 Posted: Fri Jul 25, 2003 5:26 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand Master
 
 Joined: 14 Feb 2002 Posts: 1261 Location: Detroit,MI USA 
  | 
		  
		    
			  
				Post your transmit queue definition and your process definition for the channel you are having troubles with _________________ Jeff 
 
 
IBM Certified Developer MQSeries
 
IBM Certified Specialist MQSeries
 
IBM Certified Solutions Expert MQSeries | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | pgorak | 
		  
		    
			  
				 Posted: Fri Jul 25, 2003 6:13 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Disciple
 
 Joined: 15 Jul 2002 Posts: 158 Location: Cracow, Poland 
  | 
		  
		    
			  
				Mainframe definitions:
 
 
DEFINE QLOCAL(BROKER1) +
 
  USAGE(XMITQ) +
 
  DEFPSIST(NO) +
 
  MAXDEPTH(5000) +
 
  INITQ(SYSTEM.CHANNEL.INITQ) +
 
  PROCESS(BROKER1) +
 
  TRIGGER +
 
  SHARE +
 
  REPLACE
 
 
DEFINE CHANNEL(LEGACY1/BROKER1) +
 
  CHLTYPE(SVR) +
 
  TRPTYPE(TCP) +
 
  CONNAME('10.1.101.112(1414)') +
 
  XMITQ(BROKER1) +
 
  CONVERT(NO) +
 
  REPLACE
 
 
DEFINE PROCESS(BROKER1) +
 
  USERDATA(LEGACY1/BROKER1) +
 
  APPLICID('CSQX START') +
 
  APPLTYPE(MVS)
 
  REPLACE
 
 
 
HP-UX definitions:
 
 
DEFINE CHANNEL(LEGACY1/BROKER1) +
 
  CHLTYPE(RQSTR) +
 
  TRPTYPE(TCP) +
 
  CONNAME('192.168.51.17(1414)') +
 
  MRRTY(0) +
 
  REPLACE | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mrlinux | 
		  
		    
			  
				 Posted: Fri Jul 25, 2003 7:50 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand Master
 
 Joined: 14 Feb 2002 Posts: 1261 Location: Detroit,MI USA 
  | 
		  
		    
			  
				Well on the transmit queue you dont show the trigger type
 
which should be set to trigger First,  without this set it will not generate 
 
a trigger message to the SYSTEM.CHANNEL.INITQ _________________ Jeff 
 
 
IBM Certified Developer MQSeries
 
IBM Certified Specialist MQSeries
 
IBM Certified Solutions Expert MQSeries | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | pgorak | 
		  
		    
			  
				 Posted: Mon Jul 28, 2003 11:08 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Disciple
 
 Joined: 15 Jul 2002 Posts: 158 Location: Cracow, Poland 
  | 
		  
		    
			  
				But TRIGTYPE FIRST is the default, isn't it?
 
 
Piotr | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mrlinux | 
		  
		    
			  
				 Posted: Tue Jul 29, 2003 7:08 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand Master
 
 Joined: 14 Feb 2002 Posts: 1261 Location: Detroit,MI USA 
  | 
		  
		    
			  
				It does default to first, but your definition didnt show it's state, and if it werent set correctly it would cause an issue, the lack of knowing for sure is why I asked.
 
 
What is Input use count count for SYSTEM.CHANNEL.INITQ on the mainframe, is it 1 ???  if not then the channel initiator isnt setup right. _________________ Jeff 
 
 
IBM Certified Developer MQSeries
 
IBM Certified Specialist MQSeries
 
IBM Certified Solutions Expert MQSeries | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |