| Author | 
		  Message
		 | 
		
		  | giuly020277 | 
		  
		    
			  
				 Posted: Mon Nov 12, 2007 4:27 am    Post subject: message on queue when cics is down | 
				     | 
			   
			 
		   | 
		
		
		    Centurion
 
 Joined: 07 Aug 2007 Posts: 146 Location: Florence,Italy 
  | 
		  
		    
			  
				Hello everyone,
 
 i have a queue on zos. When it receive a message...trigger let start a process (transaction called TMAT on cics) which update our database.
 
 
When cics is down....messages remain on the queue . 
 
 
if i restart cics...messages let start process TMAT . But it depend how i have configurated my trigger (every, first and so on) or it is a normally process of mq?
 
 
i mean....when i restart cics  my transaction tmat start (if i have messages on queue)....but it doesn't work good. When cics is up..and a message arrive on queue...tmat start and all goes right. I think it's a programmer's problem...what do u think??
 
 
Thank u all
 
 
Giuliano | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Mon Nov 12, 2007 5:38 am    Post subject: Re: message on queue when cics is down | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				
   
	| giuly020277 wrote: | 
   
  
	 I think it's a programmer's problem...what do u think??
 
 | 
   
 
 
 
I think you should review the APG on the conditions for triggering.
 
 
If the trigger conditions are met for any trigger then it will fire. 
 
 
Triggering (and if it fires or not) is always an administrative issue. If the triggered application "doesn't work good" this may or may not be an administrative issue. _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | jefflowrey | 
		  
		    
			  
				 Posted: Mon Nov 12, 2007 6:06 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Grand Poobah
 
 Joined: 16 Oct 2002 Posts: 19981
  
  | 
		  
		    
			  
				I'm really confused.
 
 
You want a CICS transaction to run when CICS is not running?
 
 
Do you want the Update or Insert to function, when the database is down? _________________ I am *not* the model of the modern major general. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Mon Nov 12, 2007 6:26 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | giuly020277 | 
		  
		    
			  
				 Posted: Mon Nov 12, 2007 7:07 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Centurion
 
 Joined: 07 Aug 2007 Posts: 146 Location: Florence,Italy 
  | 
		  
		    
			  
				Yes Vitor,
 
it's the same.
 
 
Last time...we set trigger on EVERY....and all go rights. As someone tell me.....i was lucky.
 
Now...it doesn' t work again at startup of CICS.....so i'm almost sure that it's an application problem. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Mon Nov 12, 2007 7:12 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				IMHO you're going to get better advice if you give us something more to work with than "it doesn't work good" - error codes, messages, symptoms, all that sort of thing will help us help you.
 
 
Also have you tracked down the possible causes laid out in the previous post? What were the results of your investigation?
 
 
Following on from that previous post, it's generally considered best practice to code an application to read from a queue until the queue is empty and fire it from a FIRST trigger, so the application is coded in a good way. I accept that this pattern is not always best in a CICS environment, where EVERY becomes a more accepted trigger because of CICS's throtteling facilities, but even so the application should read all the messages it can find.
 
 
I'd start by looking into the sequence of events at CICS startup, as previously suggested. _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | giuly020277 | 
		  
		    
			  
				 Posted: Mon Nov 12, 2007 7:58 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Centurion
 
 Joined: 07 Aug 2007 Posts: 146 Location: Florence,Italy 
  | 
		  
		    
			  
				...when cics is up...and a message arrives on queue...TMAT starts and update database...as u can see from monitor CICS 
 
 
EsssssssssssssssssssssssssssssssssssssPssssssssssssssssssssssssssssssssssssss
 
e   Task number  . . . . : 1999       e   Transaction ID . . . . : TMAT      
 
e   Facility ID  . . . . : n/a        e   CICS transaction ID  . : TMAT      
 
e   Facility type  . . . : Task       e   FCT requests . . . . : 0           
 
e   VTAM netname . . . . : None       e   Primary program ID . . : D07018A0  
 
e   Userid . . . . . . . : CXFD9T     e   HWM storage used >16M  : 174K      
 
e   CPU time . . . . . . : 0.006s     e   HWM storage used <16M  : 112K      
 
e                                     e   Response time  . . . . : 1.302s    
 
e   DB2 requests . . . . : 30         e   DB2 elapsed time . . . : 0.028s    
 
e   DL/I requests  . . . : 27         e   DL/I elapsed time  . . : 0.090s    
 
DsssssssssssssssssssssssssssssssssssssGsssssssssssssssssssssssssssssss
 
 
 
at startup of cics...if we have some messages on queue....tmat starts but do nothing ...as u can see :
 
 
sssssssssssssssssssssssssssssssssssssPssssssssssssssssssssssssssssssss
 
   Task number  . . . . : 31         e   Transaction ID . . . . : TMAT      
 
   Facility ID  . . . . : n/a        e   CICS transaction ID  . : TMAT      
 
   Facility type  . . . : Task       e   FCT requests . . . . : 0           
 
   VTAM netname . . . . : None       e   Primary program ID . . : D07018A0  
 
   Userid . . . . . . . : CXFD9T     e   HWM storage used >16M  : 52K       
 
   CPU time . . . . . . : 0.001s     e   HWM storage used <16M  : 38K       
 
                                     e   Response time  . . . . : 1.298s    
 
sssssssssssssssssssssssssssssssssssssPssssssssssssssssssssssssssssssss
 
 
There are no messages on CICS about this.... | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Mon Nov 12, 2007 8:07 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				I repeat, are you certain about the sequence of events at CICS startup?
 
 
What do the application and database logs say? _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | fjb_saper | 
		  
		    
			  
				 Posted: Mon Nov 12, 2007 12:44 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 18 Nov 2003 Posts: 20768 Location: LI,NY 
  | 
		  
		    
			  
				What is the qmgr's trigint and is the trigger monitor already running when you bring CICS up or does it only get started once CICS is fully up?
 
 
Enjoy   _________________ MQ & Broker admin | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |