× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: =?Windows-1250?q?V=E1lasz=3A_RE=3A_MQ_Series_reason_code_2035=2F_Many?=thanks
  • From: Refaie.Heba@xxxxxx
  • Date: Wed, 7 Mar 2001 17:30:19 +0100


Martin,

Thanks a lot  for the fast and sincere help, it was definitely the QM authority...I changed it according to your advise and it works instantly.

Kind regards
All the best to you
Heba    




"McCallion, Martin" <MccalliM@Midas-Kapiti.com>
Feladó: owner-rpg400-l@midrange.com

03/07/01 04:47 PM
Kérem, válaszoljon ennek a személynek: RPG400-L

       
                Címzett:  "'RPG400-L@midrange.com'" <RPG400-L@midrange.com>
                Másolat:  
                Tárgy:  RE: MQ Series reason code 2035                


Heba,

> It is my first time to do something for the MQ series. I want to open
a queue for output and put some messages into it. I get the reason code
2035 from
> the MQOPEN which as far as I could understand means " not
authorized"...although I have changed the queue authority to *all for my
userid...I am still
> getting this message...what else should I check...please advise?

It may not be the queue that you're not authorised to.  From the manual:

"MQRC_NOT_AUTHORIZED
Not authorized for access.

The user is not authorized to perform the operation attempted:

On an MQCONN or MQCONNX call, the user is not authorized to connect to
the queue manager.

On an MQOPEN or MQPUT1 call, the user is not authorized to open the
object for the option(s) specified.

On an MQCLOSE call, the user is not authorized to delete the object,
which is a permanent dynamic queue, and the Hobj parameter specified on
the MQCLOSE call is not the handle returned by the MQOPEN call that
created the queue.
This reason code can also occur in the Feedback field in the message
descriptor of a report message; in this case it indicates that the error
was encountered by a message channel agent when it attempted to put the
message on a remote queue.

Corrective action: Ensure that the correct queue manager or object was
specified, and that appropriate authority exists. "

So it's more likely that it's the Queue Manager you're not authorised
to.  You can use the GRTMQMAUT with OBJTYPE(*MQM) to change this.

HTH.

Martin.


--                                                                    
Martin McCallion                
Midas-Kapiti International
Work:  mccallim@midas-kapiti.com
Home: martin.mccallion@ukonline.co.uk

Apologies for the length of this sig, but company policy says:
This email message is intended for the named recipient only.  It may be
privileged and/or confidential.  If you are not the intended named
recipient of this email then you should not copy it or use it for any
purpose, nor disclose its contents to any other person.  You should
contact Midas-Kapiti International as shown below so that we can take
appropriate action at no cost to yourself.

Midas-Kapiti International Ltd, 1 St George's Road, Wimbledon, London,
SW19 4DR, UK
Email: Postmaster@midas-kapiti.com Tel: +44 (0)208 879 1188 Fax: +44
(0)208 947 3373
Midas-Kapiti International Ltd is registered in England and Wales under
company no. 971479
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.