Yes. Our script has that built in... #!/usr/bin/ksh (date;echo) >$0.`date "+%y%m%d`.out /bin/ksh -v >>$0.`date "+%y%m%d`.out 2>&1 << EOF #------------------------------------------------------ # Set authorization #
/opt/mqm/bin/setmqaut -m QM1 -t qmgr -g mqmdev -all +inq +connect +dsp /opt/mqm/bin/dspmqaut -m QM1 -t qmgr -g mqmdev /opt/mqm/bin/setmqaut -m QM1 -t queue -n INPUT -g mqmdev +all /opt/mqm/bin/dspmqaut -m QM1 -t queue -n INPUT -g mqmdev #------------------------------------------------------ # Refresh security and save the auths queue #------------------------------------------------------ echo refresh security | runmqsc NJSTLDDB1 rcdmqimg -m NJSTLDDB1 -t queue SYSTEM.AUTH.DATA.QUEUE #------------------------------------------------------- # END OF SCRIPT #------------------------------------------------------- -----Original Message----- From: Gorse, Darry [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 01, 2002 1:44 PM To: [EMAIL PROTECTED] Subject: Re: Problem setting ID Context First, just a simple question. Did you do a refresh security with each permission change? Cheers, Darry -----Original Message----- From: Wyatt, T. Rob [mailto:[EMAIL PROTECTED]] Sent: Tuesday, October 01, 2002 12:21 PM To: [EMAIL PROTECTED] Subject: Problem setting ID Context Before I open a problem ticket with IBM, I wanted to know if anyone else has seen this error. I have a vendor that requires specific values in the ApplIdentityData field. I set up the developer's ID with +setid permissions to the remote queue and to the XMitQ. We incrementally added authorizations to his ID until we were using +all but nothing worked until I put his ID in the mqm group. Once we got him going, I set up an ID mqmdev in it's own mqmdev group but NOT in the mqm group so that I could duplicate the problem. The developer was using Java so I wrote a simple test program in C to eliminate any Java or CLASSPATH issues. I tried opening the remote queue and also used QMgr name resolution to open the XMitQ directly. No matter what I try, there does not seem to be any combination of permissions that allows setting the ApplIdentityData field short of adding the ID to the mqm group. This is on Solaris MQ 5.2 CSD05. Any ideas what I might be overlooking? Is this a known problem? Thanks -- T.Rob Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
