| Author | 
		  Message
		 | 
		
		  | giuly020277 | 
		  
		    
			  
				 Posted: Wed Nov 21, 2007 3:22 am    Post subject: message CSQX531E | 
				     | 
			   
			 
		   | 
		
		
		    Centurion
 
 Joined: 07 Aug 2007 Posts: 146 Location: Florence,Italy 
  | 
		  
		    
			  
				Hello all,
 
when i proove to start/stop a channel...i receive this message:  
 
 
 
CSQX531E :MFET CSQXSUPR Queue WPSSIBUS for channel WMQ.TO.WPSSIBUS is 
 
in use or wrong type                                                                  
 
 
 
I have look for this message on messages and code...so i have used display qstatus command.
 
 
which parameters of display qstatus type(handle) i have to see to understand who is using wpssibus?
 
 
Ciao   | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Wed Nov 21, 2007 3:39 am    Post subject: Re: message CSQX531E | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				
   
	| giuly020277 wrote: | 
   
  
	which parameters of display qstatus type(handle) i have to see to understand who is using wpssibus?
 
 | 
   
 
 
 
The ones documented as part of the DISPLAY QSTATUS command?    
 
 
You'll get something like PSBNAME, PSTID or TASKNO/TRANSID depending on APPLTYPE.
 
 
I'd double check the queue in question is really an xmitq first, rather than a local queue. Especially if the channel has never worked and always produces this message. _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | giuly020277 | 
		  
		    
			  
				 Posted: Wed Nov 21, 2007 5:47 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Centurion
 
 Joined: 07 Aug 2007 Posts: 146 Location: Florence,Italy 
  | 
		  
		    
			  
				thanks vitor...
 
i've seen that i have associated the same initiation queue to 2 different xmit queue. It could be an error?
 
 
I find an error again: there was no process associated to xmit queue who start channel when a message arrive on queue.Now i have corrected it...and i can start and stop the channel without errors.
 
 
 
last question... if remote queue manager go down....i have some messages on a my xmit queue( in my queue manager). When remote manager go up again....message are automatically delivered or i have to do some operations to do this?
 
 
Thanks
 
 
Ps. As u see   ...i start to study mq series on z/os just not too much time ago...so..i'm so sorry for my (i think) "simple" questions.... | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Wed Nov 21, 2007 5:49 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				
   
	| giuly020277 wrote: | 
   
  
	last question... if remote queue manager go down....i have some messages on a my xmit queue( in my queue manager). When remote manager go up again....message are automatically delivered or i have to do some operations to do this?
 
 | 
   
 
 
 
It's the same behaviour in this situation on z/OS as it is on the distributed platforms. _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | fjb_saper | 
		  
		    
			  
				 Posted: Wed Nov 21, 2007 12:38 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 18 Nov 2003 Posts: 20768 Location: LI,NY 
  | 
		  
		    
			  
				Just make sure the channel is triggered, that the trigger interval is not too big on the qmgr and that the retry intervals are set right.
 
 
When the problem is resolved, on the next retry the channel should connect and send the messages waiting in the xmitq.
 
 
Enjoy   _________________ MQ & Broker admin | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | giuly020277 | 
		  
		    
			  
				 Posted: Thu Nov 22, 2007 1:11 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Centurion
 
 Joined: 07 Aug 2007 Posts: 146 Location: Florence,Italy 
  | 
		  
		    
			  
				thank u...
 
 
i will examine it... | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | giuly020277 | 
		  
		    
			  
				 Posted: Mon Dec 24, 2007 1:53 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Centurion
 
 Joined: 07 Aug 2007 Posts: 146 Location: Florence,Italy 
  | 
		  
		    
			  
				Hello,
 
i continue to get csqx531e message :
 
 
CSQX531E :MFEP CSQXSUPR Queue QMAS400P for channel MFEP.TO.QMAS400P is
 
in use or wrong type                                                  
 
CSQ9023E :MFEP CSQXCRPS ' START CHANNEL' ABNORMAL COMPLETION          
 
 
I have done then a display qstatus and it give me :
 
 
CSQM441I :MFEP              
 
 QSTATUS(QMAS400P)          
 
 TYPE(QUEUE)                
 
 OPPROCS(1)                 
 
 IPPROCS(1)                 
 
 CURDEPTH(15)               
 
 UNCOM(NO)                  
 
 MONQ(OFF)                  
 
 QTIME( , )                 
 
 MSGAGE( )                  
 
 LPUTDATE( )                
 
 LPUTTIME( )                
 
 LGETDATE( )                
 
 LGETTIME( )                
 
 QSGDISP(QMGR)              
 
 
 
I controlled that trasmission queue is type XMIT :
 
 
Usage . . . . . . . . . . . : X  N=Normal, X=XmitQ
 
 
so what is the problem in your opinion?i have to controll something more? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | giuly020277 | 
		  
		    
			  
				 Posted: Mon Dec 24, 2007 1:58 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Centurion
 
 Joined: 07 Aug 2007 Posts: 146 Location: Florence,Italy 
  | 
		  
		    
			  
				..i forget..
 
 
i have done a DISPLAY CHSTATUS AND IT TELL ME
 
 
CHSTATUS(MFEP.TO.QMAS400P)                 
 
CHLDISP(PRIVATE)                           
 
XMITQ(QMAS400P)                            
 
CONNAME(XX.XX.XX.XX)                     
 
CURRENT                                    
 
CHLTYPE(SDR)                               
 
STATUS(STOPPED)                            
 
SUBSTATE( )                                
 
INDOUBT(NO)                                
 
LSTSEQNO(14)                               
 
LSTLUWID(B84053D8824D4043)                 
 
CURMSGS(0)                                 
 
CURSEQNO(7)                                
 
CURLUWID(C1AC613AD029E044)                 
 
LSTMSGTI(12.27.2                          
 
LSTMSGDA(2007-12-20)                       
 
MSGS(7)                                    
 
BYTSSENT(6467706)                          
 
BYTSRCVD(904)                              
 
BATCHES(0)                                 
 
CHSTATI(12.09.14)                          
 
CHSTADA(2007-12-20)                        
 
BUFSSENT(229)                              
 
BUFSRCVD(24)                               
 
LONGRTS(999999999)                         
 
SHORTRTS(10)                               
 
MONCHL(OFF)                                
 
STOPREQ(YES)                               
 
KAINT(360)                                 
 
QMNAME(MFEP)                               
 
RQMNAME(QMAS400P)                          
 
SSLCERTI( )                                
 
SSLCERTU(MFEPCHIN)                         
 
SSLRKEYS(0)                                
 
SSLKEYTI( )                                
 
SSLKEYDA( )                                
 
 SSLPEER( )                     
 
 LOCLADDR(XX.XX.XX.XX(1074))     
 
 BATCHSZ(50)                    
 
 MAXMSGL(4194304)               
 
 COMPHDR(                       
 
  NONE                          
 
  NONE                          
 
  )                             
 
 COMPMSG(                       
 
  NONE                          
 
  NONE                          
 
  )                             
 
 HBINT(300)                     
 
 NPMSPEED(FAST)             
 
 
MAYBE IT WILL BE USEFUL | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | giuly020277 | 
		  
		    
			  
				 Posted: Mon Dec 24, 2007 2:30 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Centurion
 
 Joined: 07 Aug 2007 Posts: 146 Location: Florence,Italy 
  | 
		  
		    
			  
				...SOMETHING MORE...
 
 
 on ispf panel...i see that the state of my channel is STOP.
 
 
Then i try to do a ping to it...and it tell me :
 
 
CSQX514E :MFEP CSQXPING Channel MFEP.TO.QMAS400P is active on MFEP
 
 
...but i continued to see STOP in ispf panel.
 
 
After some minutes i received the followiing message :
 
 
CSQX208E :MFEP CSQXRCTL Error receiving data,  932     
 
channel MFEP.TO.QMAS400P,                              
 
connection (xx.xx.xx.xx)                             
 
(queue manager QMAS400P)                               
 
TRPTYPE=TCP RC=00000480 reason=00000000      
 
 
 
After that...all go right     
 
 
Can u help me to understand why? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | giuly020277 | 
		  
		    
			  
				 Posted: Mon Dec 24, 2007 3:14 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Centurion
 
 Joined: 07 Aug 2007 Posts: 146 Location: Florence,Italy 
  | 
		  
		    
			  
				my investigation go on  
 
 
 
I got message CSQX208E because remote queue manager was down.
 
 
Now i see that my trasmission queue was not triggered.
 
 
Now i have triggered it...so..when a message arrive on queue...it start channel. 
 
 
It seems it is all right....in your opinion my problem depend on the fact my xmit queue was not triggered to start channel?
 
 
Thank u all...and MERRY CHRISTMAS    | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |