| Author | 
		  Message
		 | 
		
		  | 16legal | 
		  
		    
			  
				 Posted: Mon Jan 27, 2014 8:15 am    Post subject: CICS Error Output | 
				     | 
			   
			 
		   | 
		
		
		   Novice
 
 Joined: 05 Jun 2013 Posts: 21
  
  | 
		  
		    
			  
				| How do we capture error message from CICS error terminal through esql ? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Mon Jan 27, 2014 8:19 am    Post subject: Re: CICS Error Output | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				
   
	| 16legal wrote: | 
   
  
	| How do we capture error message from CICS error terminal through esql ? | 
   
 
 
 
By connecting an ESQL Compute note to the relevant terminal on the CICS node. 
 
 
That can't be the question you're really asking. _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 16legal | 
		  
		    
			  
				 Posted: Mon Jan 27, 2014 8:45 am    Post subject: CICS Error Output | 
				     | 
			   
			 
		   | 
		
		
		   Novice
 
 Joined: 05 Jun 2013 Posts: 21
  
  | 
		  
		    
			  
				| Yes connecting the ERROR terminal to the compute node is the approach but what is the structure of ERROR output which can be captured in compute node through esql? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 16legal | 
		  
		    
			  
				 Posted: Mon Jan 27, 2014 9:08 am    Post subject: CICS Error Output | 
				     | 
			   
			 
		   | 
		
		
		   Novice
 
 Joined: 05 Jun 2013 Posts: 21
  
  | 
		  
		    
			  
				As in for SOAP fault , we create a fault message similar to the below structure
 
 
SET OutputRoot.SOAP.Context.Namespace.(SOAP.NamespaceDecl)xmlns:soapenv = soapenv;
 
 SET OutputRoot.SOAP.Body.ns:Fault.faultcode = SOAP_FAULTCODE_VALUE_CLIENT;
 
 SET OutputRoot.SOAP.Body.ns:Fault.faultstring = 'Error while parsing message';
 
 SET OutputRoot.SOAP.Body.ns:Fault.faultactor = InputRoot.HTTPInputHeader."X-Original-HTTP-Command";
 
 SET OutputRoot.SOAP.Body.ns:Fault.detail.ExceptionType = messageText;
 
 
Similarly , how do we capture CICS Error message ? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Mon Jan 27, 2014 9:21 am    Post subject: Re: CICS Error Output | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				
   
	| 16legal wrote: | 
   
  
	| Yes connecting the ERROR terminal to the compute node is the approach but what is the structure of ERROR output which can be captured in compute node through esql? | 
   
 
 
 
Have you considered examing the output of the error terminal to see the structure? _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | smdavies99 | 
		  
		    
			  
				 Posted: Mon Jan 27, 2014 9:21 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Jedi Council
 
 Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land. 
  | 
		  
		    
			  
				You can examing the ExceptionList for the CICS Error.
 
 
There are several posts here about traversing an exceptionList.
 
 
Looking at it with A trace node can be very revealling. _________________ WMQ User since 1999
 
MQSI/WBI/WMB/'Thingy' User since 2002
 
Linux user since 1995
 
 
 
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |