| Author | 
		  Message
		 | 
		
		  | Reeti | 
		  
		    
			  
				 Posted: Tue May 13, 2003 1:19 am    Post subject: Authorization problem | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 11 Jul 2002 Posts: 40
  
  | 
		  
		    
			  
				Hi:
 
 
I'm sending a message using C++ API and using the MQOO_SET_ALL_CONTEXT in both queue open and PMO options. While I'm trying to generate Expiry report which is not working. With out the SET_ALL_CONTEXT it's able to generate the message expiry report. When it's not generating the report then in the error log file it's giving 2035 error on the ReplyToQueue, whcich is a authorization problem. I tried to set all the permitions to the queue but still it is not working. Pls. help.
 
 
thanks and regards
 
Reeti Saha | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | dnaren | 
		  
		    
			  
				 Posted: Tue May 13, 2003 2:20 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Apprentice
 
 Joined: 10 Aug 2001 Posts: 45 Location: Charlotte, NC 
  | 
		  
		    
			  
				| Are you using any server connection channel or client connection channel? Is it a sever program or a client program? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Reeti | 
		  
		    
			  
				 Posted: Tue May 13, 2003 2:36 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Apprentice
 
 Joined: 11 Jul 2002 Posts: 40
  
  | 
		  
		    
			  
				I'm not using any server/client connection channel... using the same qmgr to send the expiration msg using server API's.
 
 
thanks
 
Reeti | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | vmcgloin | 
		  
		    
			  
				 Posted: Tue May 13, 2003 4:50 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Knight
 
 Joined: 04 Apr 2002 Posts: 560 Location: Scotland 
  | 
		  
		    
			  
				Have you double checked that the MQMD UserIdentifier you are setting with SET_ALL_CONTEXT exists on the machine where the replyq is, and that either the userid or the group it belongs to has been granted authority on the replyq? 
 
        put
 
        passid
 
        passall
 
        setid
 
        setall
 
 
The default userid when you don't set all context probably already has authority.
 
 
Cheers,
 
Vicky | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mqonnet | 
		  
		    
			  
				 Posted: Tue May 13, 2003 4:51 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand Master
 
 Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa. 
  | 
		  
		    
			  
				Wheres the message landing onto.  I guess it would be going over to the replytoq queue manager's dlq, if your replytoq is not on the same queue manager as your target queue.  Meaning channels involved.
 
 
If the message goes into the dlq.  Just do a browse of the message and you could find the userid that it it trying to use to put the message onto replytoq, unless you already know this for sure.
 
 
Once you get this userid, do a dspmqaut on the replytoq for this userid.  If you dont see anything, then you need to assign appropriate authority using setmqaut.
 
 
Hope this helps.
 
 
Cheers
 
Kumar _________________ IBM Certified WebSphere MQ V5.3 Developer
 
IBM Certified WebSphere MQ V5.3 Solution Designer
 
IBM Certified WebSphere MQ V5.3 System Administrator | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | vennela | 
		  
		    
			  
				 Posted: Tue May 13, 2003 7:54 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Jedi Knight
 
 Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India 
  | 
		  
		    
			  
				| If I am not wrong, the MQMDs userids are set using SET_IDENTITY_CONTEXT and SET_ALL_CONTEXT will not do that. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mqonnet | 
		  
		    
			  
				 Posted: Tue May 13, 2003 3:44 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand Master
 
 Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa. 
  | 
		  
		    
			  
				Straight from the manuals..
 
 
[quote][color=red][/color]
 
Allow all context to be set. 
 
This allows the MQPMO_SET_ALL_CONTEXT option to be specified in the PutMsgOpts parameter when a message is put on a queue; this gives the message the identity and origin context information contained in the MsgDesc parameter specified on the  MQPUT  or  MQPUT1  call. For more information on message context, see the MQSeries Application Programming Guide. 
 
 
This option implies the following options, which need not therefore be specified: 
 
 
MQOO_PASS_IDENTITY_CONTEXT 
 
MQOO_PASS_ALL_CONTEXT 
 
MQOO_SET_IDENTITY_CONTEXT 
 
[/quote] _________________ IBM Certified WebSphere MQ V5.3 Developer
 
IBM Certified WebSphere MQ V5.3 Solution Designer
 
IBM Certified WebSphere MQ V5.3 System Administrator | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |