|   | 
	 
  
    | 
RSS Feed - WebSphere MQ Support
 | 
RSS Feed - Message Broker Support
 |   
 
  
	|  Search found 4 matches | 
   
  
  	
	  
		
		  | Author | 
		  Message | 
  		 
  		
		     Topic: Reason 2046..., browse and lock, does it really work? | 
  		 
  		
		  Hannibal
  
	  	  Replies: 11 Views: 9947
  | 
		   Forum: IBM MQ Java / JMS   Posted: Sun Jun 02, 2002 11:56 pm   Subject: Reason 2046..., browse and lock, does it really work? | 
  		 
  		
		  Hi,
  I have taken the original code from IBM and added the LOCK option
 (see this comment // <-- lock option added)
  I get always 2046. 
 
 
 /**************************************************** ... | 
  		 
  		
		     Topic: Reason 2046..., browse and lock, does it really work? | 
  		 
  		
		  Hannibal
  
	  	  Replies: 11 Views: 9947
  | 
		   Forum: IBM MQ Java / JMS   Posted: Fri May 24, 2002 3:08 am   Subject: Reason 2046..., browse and lock, does it really work? | 
  		 
  		
		  Version 5.1
 And the OS is Tandem NSK, as you said.
 It seems that MQGMO_LOCK is not supported for this platform (although it is not noted in the manual) since this option causes failure in sample C p ... | 
  		 
  		
		     Topic: Reason 2046..., browse and lock, does it really work? | 
  		 
  		
		  Hannibal
  
	  	  Replies: 11 Views: 9947
  | 
		   Forum: IBM MQ Java / JMS   Posted: Thu May 23, 2002 7:33 am   Subject: Reason 2046..., browse and lock, does it really work? | 
  		 
  		
		  Thanks for your reply.
 These are the only get options I use. The queue is opened with
 int openOptions = MQC.MQOO_INQUIRE + MQC.MQOO_BROWSE;
 the get option 
 browseOptions.options = MQC.MQGMO_BROWSE ... | 
  		 
  		
		     Topic: Reason 2046..., browse and lock, does it really work? | 
  		 
  		
		  Hannibal
  
	  	  Replies: 11 Views: 9947
  | 
		   Forum: IBM MQ Java / JMS   Posted: Thu May 23, 2002 7:06 am   Subject: Reason 2046..., browse and lock, does it really work? | 
  		 
  		
		  I always get  2046 back when I specify
 MQC.MQGMO_BROWSE_FIRST + MQC.MQGMO_LOCK
 or 
 MQC.MQGMO_BROWSE_NEXT + MQC.MQGMO_LOCK
 as get option.
 It should work, following manual.  
 Have you ever try t ... | 
  		 
	   
	 | 
   
 
  	 | 
	  |