| Author | 
		  Message
		 | 
		
		  | rajasudan | 
		  
		    
			  
				 Posted: Mon Nov 10, 2014 6:05 pm    Post subject: AMQ9514 / AMQ9999 Sender channel in use (Window to mainframe | 
				     | 
			   
			 
		   | 
		
		
		    Newbie
 
 Joined: 04 May 2011 Posts: 8
  
  | 
		  
		    
			  
				Hello All
 
 
We are having issue with our windows sender channel -> "WIN.MAIN"
 
Issue escalated for workflow affected between two different applications.
 
I can found out similar issue in google for RCVR channels and it can be sort out by AdopnewMCA concept, but issue with sender channel I help less.
 
Please some one help out 
 
 
 
Error log from Windows box:
 
-------------------------------------------------------------------------------
 
13/07/2014 23:27:51 - Process(1472.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
 
                      Host(TF_TK_AGT3) Installation(Installation1)
 
                      VRMF(7.5.0.0) QMgr(TFCP71)
 
                     
 
AMQ9002: Channel 'WIN.MAIN' is starting.
 
 
EXPLANATION:
 
Channel 'WIN.MAIN' is starting.
 
ACTION:
 
None. 
 
-------------------------------------------------------------------------------
 
13/07/2014 23:28:11 - Process(3640.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
 
                      Host(TF_TK_AGT3) Installation(Installation1)
 
                      VRMF(7.5.0.0) QMgr(TFCP71)
 
                     
 
AMQ9514: Channel 'WIN.MAIN' is in use.
 
 
EXPLANATION:
 
The requested operation failed because channel 'WIN.MAIN' is currently
 
active.
 
ACTION:
 
Either end the channel manually, or wait for it to close, and retry the
 
operation. 
 
----- amqrcsia.c : 1048 -------------------------------------------------------
 
13/07/2014 23:28:11 - Process(3640.1) User(MUSR_MQADMIN) Program(runmqchl.exe)
 
                      Host(TF_TK_AGT3) Installation(Installation1)
 
                      VRMF(7.5.0.0) QMgr(TFCP71)
 
                     
 
AMQ9999: Channel 'WIN.MAIN' to host '172.31.xx.xx(1422)' ended
 
abnormally.
 
 
EXPLANATION:
 
The channel program running under process ID 3640(1444) for channel
 
'TFCP71.MPW1.UPD01' ended abnormally. The host name is '172.31.xx.xxx(1422)';
 
in some cases the host name cannot be determined and so is shown as '????'.
 
ACTION:
 
Look at previous error messages for the channel program in the error logs to
 
determine the cause of the failure. Note that this message can be excluded
 
completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage"
 
attributes under the "QMErrorLog" stanza in qm.ini. Further information can be
 
found in the System Administration Guide.   
  Last edited by rajasudan on Mon Nov 10, 2014 10:20 pm; edited 1 time in total | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | fjb_saper | 
		  
		    
			  
				 Posted: Mon Nov 10, 2014 7:48 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 18 Nov 2003 Posts: 20768 Location: LI,NY 
  | 
		  
		    
			  
				Looks like one the hosts thinks the channel is still running.
 
What is the idle disconnect interval on the channel?
 
 
This happens more often if the channel is always on, but the network does not support an always on channel...
 
 
Adopt new MCA can help at the receiving end. If you have no control over the receiving end, make sure you set your idle disconnect interval to an appropriate value and have the channel triggered on first.
 
 
Have fun   _________________ MQ & Broker admin | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | rajasudan | 
		  
		    
			  
				 Posted: Mon Nov 10, 2014 10:19 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Newbie
 
 Joined: 04 May 2011 Posts: 8
  
  | 
		  
		    
			  
				Ideal disconnection interval is 0 and does that mean channel goes to end abnormally after in use log register??
 
Also in other few set up I can see channel disconnection interval is 0 and that works fine.    | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | PaulClarke | 
		  
		    
			  
				 Posted: Tue Nov 11, 2014 1:51 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand Master
 
 Joined: 17 Nov 2005 Posts: 1002 Location: New Zealand 
  | 
		  
		    
			  
				rajasudan
 
 
Can you explain a little more about the problem. From the log it just looks like someone ran RUNMQCHL for a particular channel and it was already running. While this is not ideal it doesn't strike me as a problem.
 
 
Can you say why the RUNMQCHL program was started? Nowadays it is often better to configure channels to run as threads of AMQRMPPA although I do agree that there are times that RUNMQCHL is handy. Do you have a script starting RUNMQCHL or is it started manually? Is the actually running channel not working?
 
 
Cheers,
 
Paul. _________________ Paul Clarke
 
MQGem Software
 
www.mqgem.com | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | fjb_saper | 
		  
		    
			  
				 Posted: Tue Nov 11, 2014 3:28 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 18 Nov 2003 Posts: 20768 Location: LI,NY 
  | 
		  
		    
			  
				
   
	| rajasudan wrote: | 
   
  
	Ideal disconnection interval is 0 and does that mean channel goes to end abnormally after in use log register??
 
Also in other few set up I can see channel disconnection interval is 0 and that works fine.    | 
   
 
 
 
That was IDLE and not IDEAL. I understand English might not be your first language, so please look up the difference in a dictionary.
 
 
A value of 0 means the channel is always on. With a network that may experience "blips" this might cause a problem. See if a triggered channel would suit you better, with a reasonable idle disconnect interval.
 
 
Think also of firewalls cutting the connection after some idle time.
 
 
Have fun   _________________ MQ & Broker admin | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |