| Author | 
		  Message
		 | 
		
		  | depuk | 
		  
		    
			  
				 Posted: Wed Sep 14, 2016 1:56 am    Post subject: Getting error with   MQCCDTURL environment | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 13 Nov 2015 Posts: 31
  
  | 
		  
		    
			  
				I have installed MQ 9 on Linux server and trying to test the server and client enivornment by using new MQCCDTURL. I defined both server and clinet connect channels on the Qmanger and set the environment varibale. The same configuration is working when i used  with environment variables MQCHLLIB and MQCHLTAB.
 
 
 
export MQCCDTURL=file:///var/mqm/qmgrs/QM9/@ipcc/AMQCLCHL.TAB
 
 
[mqm@fedora17-64-base ~]$ echo $MQCCDTURL
 
file:///var/mqm/qmgrs/QM9/@ipcc/AMQCLCHL.TAB
 
 
I am getting this exception in the log files .Please help me
 
 
 
 
   
	| Quote: | 
   
  
	09/10/2016 02:05:37 PM - Process(4036.1) User(mqm) Program(amqsputc)
 
                    Host(fedora17-64-base.eidikointernal.com) Installation(Installation3)
 
                    VRMF(9.0.0.0)
 
AMQ9516: File error occurred for file
 
'file:///var/mqm/qmgrs/QM9/@ipcc/AMQCLCHL.TAB'.
 
 
EXPLANATION:
 
The filesystem returned error code 536908176 for file
 
'file:///var/mqm/qmgrs/QM9/@ipcc/AMQCLCHL.TAB'.
 
ACTION:
 
Record the name of the file and tell the systems administrator, who should
 
ensure that file is correct and available, for example that the current user
 
has appropriate access to the file for reading or writing. | 
   
 
 
 
When i test | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | bruce2359 | 
		  
		    
			  
				 Posted: Wed Sep 14, 2016 5:31 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Poobah
 
 Joined: 05 Jan 2008 Posts: 9486 Location: US: west coast, almost. Otherwise, enroute. 
  | 
		  
		    
			  
				Post the results when you tried the equivalent, pre-v9 
 
export MQCHLLIB= 
 
export MQCHLTAB=
 
 
or 
 
 
MQSERVER= _________________ I like deadlines. I like to wave as they pass by.
 
ב''ה
 
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mqjeff | 
		  
		    
			  
				 Posted: Wed Sep 14, 2016 5:39 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Grand Master
 
 Joined: 25 Jun 2008 Posts: 17447
  
  | 
		  
		    
			  
				Why does the "file" have three / after it? _________________ chmod  -R ugo-wx / | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | bruce2359 | 
		  
		    
			  
				 Posted: Wed Sep 14, 2016 5:53 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Poobah
 
 Joined: 05 Jan 2008 Posts: 9486 Location: US: west coast, almost. Otherwise, enroute. 
  | 
		  
		    
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mqjeff | 
		  
		    
			  
				 Posted: Wed Sep 14, 2016 6:06 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Grand Master
 
 Joined: 25 Jun 2008 Posts: 17447
  
  | 
		  
		    
			  
				Ah.  Right.  Two for "file://" and one for the filesystem root. _________________ chmod  -R ugo-wx / | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | depuk | 
		  
		    
			  
				 Posted: Wed Sep 14, 2016 6:23 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 13 Nov 2015 Posts: 31
  
  | 
		  
		    
			  
				Hi Bruce,
 
Please find the MQCHLLIB and MQCHLTAB details.When i tried with this environment variables then i am able to connect .
 
 
[mqm@fedora17-64-base ~]$ echo $MQCHLLIB
 
/var/mqm/qmgrs/QM9/@ipcc
 
[mqm@fedora17-64-base ~]$ echo $MQCHLTAB
 
AMQCLCHL.TAB
 
 
   
	| Quote: | 
   
  
	
 
[mqm@fedora17-64-base ~]$ /opt/MQ9/samp/bin/amqsputc QL1 QM9
 
Sample AMQSPUT0 start
 
target queue is QL1
 
hi 
 
 
Sample AMQSPUT0 end | 
   
 
 
 
   
	| Quote: | 
   
  
	dis chs(*)
 
     1 : dis chs(*)
 
AMQ8417: Display Channel Status details.
 
   CHANNEL(CHAN2)                          CHLTYPE(SVRCONN)
 
   CONNAME(XX.XX.XX)                   CURRENT
 
   STATUS(RUNNING)                         SUBSTATE(RECEIVE)
 
 | 
   
 
 | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | PaulClarke | 
		  
		    
			  
				 Posted: Wed Sep 14, 2016 9:01 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand Master
 
 Joined: 17 Nov 2005 Posts: 1002 Location: New Zealand 
  | 
		  
		    
			  
				Do you have any exits ? This could be a complete red herring but  536908176 is 20009190 in hex. If you issue MQRC AMQ9190 you get this....
 
   
	| Code: | 
   
  
	536908176  0x20009190  rrcE_EXIT_ERROR
 
 
MESSAGE:
 
Channel stopping because of an error in the exit.
 
 
EXPLANATION:
 
The user exit '<insert one>', invoked for channel '<insert two>' with id '1111'
 
and reason '2222', returned values that are not valid, as reported in the
 
preceding messages. The channel stops.
 
 
ACTION:
 
Investigate why the user exit program set values that are not valid.
 
 | 
   
 
 
 
As I say, could be a red herring or the default failing return code for this feature. 
 
 
Cheers,
 
Paul. _________________ Paul Clarke
 
MQGem Software
 
www.mqgem.com | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | tczielke | 
		  
		    
			  
				 Posted: Wed Sep 14, 2016 6:04 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Guardian
 
 Joined: 08 Jul 2010 Posts: 943 Location: Illinois, USA 
  | 
		  
		    
			  
				The following might provide a clue.  Run your program as follows:
 
 
strace -f /opt/MQ9/samp/bin/amqsputc QL1 QM9 2>strace.out
 
 
Once you are done, grep the strace.out file for AMQCLCHL.TAB, and see if there is an error being listed when accessing this file.  If you don't get any hits for AMQCLCHL.TAB, then go to the bottom of the strace.out file, page up to where the AMQERR01.LOG file is being opened to write out your error, and then look a little above that for a clue on what might be failing to cause the entry in the MQ error log. _________________ Working with MQ since 2010. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |