MQ and adopted authority

[Evan Harris <spanner@xxxxxxxxxx>]

Hi guys

I have a client running V4R5 who just upgraded MQ from V4R2M1 to V5R2.

Some processes that previously worked now seem to exhibit some different 
behaviour and I'm wondering if MQ 5.2 treats adopted authorities any 
differently.

The scenario is this: programs that used to place entries on MQ queues now 
get a 2035 (not authorised or queue does not exist) error when attempting 
to put an entry on the queue. The owner of the program has *ALLMQI 
authority to the queues in question and the program adopts owner authority.

Is this a valid approach (i.e using adopted authority) under MQ or is there 
a better/preferred way to do this.

I'm pretty sure that *PUBLIC was previously *EXCLUDE on this and I've 
worked around it for the time being by granting *PUBLIC authority using 
GRTMQMAUT for the time being but want a better aproach, if there is one.

Any and all advice regarding MQ authorities welcome.

Regards
Evan Harris

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---