|   | 
	 
  
    | 
RSS Feed - WebSphere MQ Support
 | 
RSS Feed - Message Broker Support
 |   
 
  
	|  MQ Listener handshake logs? | 
	« View previous topic :: View next topic »  | 
   
  
  	
	  
		
		
		  | Author | 
		  Message
		 |  
		
		  | tczielke | 
		  
		    
			  
				 Posted: Fri Feb 06, 2015 10:59 am    Post subject:  | 
				     | 
			   
			 
		   | 
		 
		
		   Guardian
 
 Joined: 08 Jul 2010 Posts: 943 Location: Illinois, USA 
  | 
		  
		    
			  
				To go along the lines of what fjb_saper suggested and if you have Visual Studio installed on the Windows server, you could do the following to check how it is linked:
 
 
1.  Open a Visual Studio command prompt
 
2.  Do a "dumpbin /dependents executable" on their executable.
 
 
ex.  dumpbin /dependents vendor.exe
 
 
If the output shows mqm.dll, they have it linked to the server dll. If the output shows mqic.dll, they have it linked to the client dll. | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | smeunier | 
		  
		    
			  
				 Posted: Fri Feb 06, 2015 11:28 am    Post subject:  | 
				     | 
			   
			 
		   | 
		 
		
		    Partisan
 
 Joined: 19 Aug 2002 Posts: 305 Location: Green Mountains of Vermont 
  | 
		  
		    
			  
				After much confabulation with the customer, they relented and modified code. Connectivity has been established. Still going to look through the server side trace files to see if anything would have been reported at that level. 
 
 
Thanks everyone for listening and suggestions. | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | bruce2359 | 
		  
		    
			  
				 Posted: Fri Feb 06, 2015 1:21 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		 
		
		    Poobah
 
 Joined: 05 Jan 2008 Posts: 9486 Location: US: west coast, almost. Otherwise, enroute. 
  | 
		  
		    
			  
				
   
	| smeunier wrote: | 
   
  
	After much confabulation with the customer, they relented and modified code. Connectivity has been established. Still going to look through the server side trace files to see if anything would have been reported at that level. 
 
 
Thanks everyone for listening and suggestions. | 
   
 
 
How did they modify their code? _________________ 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 | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | smeunier | 
		  
		    
			  
				 Posted: Fri Feb 06, 2015 2:26 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		 
		
		    Partisan
 
 Joined: 19 Aug 2002 Posts: 305 Location: Green Mountains of Vermont 
  | 
		  
		    
			  
				
   
	| Quote: | 
   
  
	| How did they modify their code? | 
   
 
 
 
They did not share the details of what change was made to their code but I provided them a snippet of code that works with C client applications.
 
 
   
	| Code: | 
   
  
	MQHCONN    hConn;        /* Connection handle                   */
 
    MQHOBJ     hObject;      /* Object handle                       */
 
    MQCHAR48   qmgrName;     /* Name of queue manager               */
 
    MQLONG     iCompCode;    /* Completion code                     */
 
    MQLONG     iReason;      /* Reason code                         */
 
    
 
    /* These are the MQ Structs to be used in this program          */
 
    MQOD    mqod = {MQOD_DEFAULT};    /* Object description         */
 
    
 
    /* These are the special structures used          */
 
    MQCNO   mqcno = {MQCNO_DEFAULT} ; /* Connection options         */
 
    MQCD    mqcd  = {MQCD_CLIENT_CONN_DEFAULT};  /* Channel Defs    */
 
 
 
 
    /*  can also retrive data such as queue name and such           */
 
    memset( qmgrName , 0 , MQ_Q_MGR_NAME_LENGTH) ;
 
    strncpy(mqcd.ConnectionName,"<hostname.domain(mq port)>",MQ_CONN_NAME_LENGTH);
 
    strncpy(mqcd.ChannelName,"<SVRCONN channel Name>",MQ_CHANNEL_NAME_LENGTH);
 
 
/* Point the MQCNO to the client connection definition and set its */ /*ClientConnOffset or the ClietConnPtr will be ignored... */
 
 
   mqcno.ClientConnPtr = &mqcd;
 
   mqcno.Version = MQCNO_VERSION_2;
 
 
    MQCONNX(qmgrName,
 
         &mqcno,
 
         &hConn,
 
         &iCompCode,
 
         &iReason);
 
 | 
   
 
 
 
They were not using MQCONNX but MQCONN, which is fine. They implemented the MQCONNX into their code and it worked. | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | 
		    
		   | 
		 
	   
	 | 
   
 
 
 
  
  	
	  
		
		  
 
  | 
		  You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
  | 
  		 
	   
	 | 
   
 
  	 | 
	  |