title: Why I get AMQ7077 even after turning security in WebSphere MQ off?
body: <p>In Windows7 when I set <code>MQSNOAUT=yes</code> everything is ok and I can do whatever I want in WebSphere MQ. But in RedHat even after setting <code>MQSNOAUT</code> to <code>yes</code> I'm getting this error:</p>
  
  <pre><code>[root@RHEL6-135 bin]$ ll crtmqm  
  -rwxrwxrwx. 1 mqm mqm 41822 Oct 22  2015 crtmqm  
  [root@RHEL6-135 bin]$ crtmqm testqm  
  AMQ7077: You are not authorized to perform the requested operation.  
  [root@RHEL6-135 bin]$
  </code></pre>
  
  <p>Using <code>mqm</code> user I can create queue manager but cannot start it:</p>
  
  <pre><code>[mqm@RHEL6-135 bin]$ crtmqm testqm  
  WebSphere MQ queue manager created.  
  Directory '/var/mqm/qmgrs/testqm' created.  
  The queue manager is associated with installation 'Installation1'.  
  Creating or replacing default objects for queue manager 'testqm'.  
  Default objects statistics : 79 created. 0 replaced. 0 failed.  
  Completing setup.  
  Setup completed.  
  [mqm@RHEL6-135 bin]$ strmqm testqm  
  WebSphere MQ queue manager 'testqm' starting.  
  The queue manager is associated with installation 'Installation1'.  
  5 log records accessed on queue manager 'testqm' during the log replay phase.  
  Log replay for queue manager 'testqm' complete.  
  Transaction manager state recovered for queue manager 'testqm'.  
  The queue manager ended for reason 545284129, ''.  
  [mqm@RHEL6-135 bin]$
  </code></pre>
  
  <p>Unfortunately, there is no useful information in these log files:  </p>
  
  <p>/var/mqm/errors/AMQERR01.LOG:   </p>
  
  <pre><code>----- amqxfdcx.c : 888 --------------------------------------------------------  
  03/14/2017 10:00:16 AM - Process(15859.1) User(mqm) Program(amqzmur0)  
                      Host(RHEL6-135) Installation(Installation1)  
                      VRMF(8.0.0.4)  
  AMQ6125: An internal WebSphere MQ error has occurred.  
  
  EXPLANATION:  
  An internal error has occurred with identifier 2080520F.  This message is  
  issued in association with other messages.  
  ACTION:  
  Use the standard facilities supplied with your system to record the problem  
  identifier and to save any generated output files. Use either the MQ Support  
  site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support  
  Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a  
  solution is already available.  If you are unable to find a match, contact your  
  IBM support center.  Do not discard these files until the problem has been  
  resolved.  
  ...  
  repeated 27 times!
  </code></pre>
  
  <p>/var/mqm/qmgrs/testqm/errors/AMQERR01.LOG:</p>
  
  <pre><code>03/14/2017 10:00:16 AM - Process(15840.4) User(mqm) Program(amqzmuc0)  
                      Host(RHEL6-135) Installation(Installation1)  
                      VRMF(8.0.0.4) QMgr(testqm)  
  
  AMQ5051: The queue manager task 'LOGGER-IO' has started.  
  
  EXPLANATION:  
  The critical utility task manager has started the LOGGER-IO task. This task has  
  now started 1 times.  
  ACTION:  
  None.  
  -------------------------------------------------------------------------------  
    ....
  -------------------------------------------------------------------------------  
  03/14/2017 10:00:16 AM - Process(15859.6) User(mqm) Program(amqzmur0)  
                      Host(RHEL6-135) Installation(Installation1)   
                      VRMF(8.0.0.4) QMgr(testqm)  
  
  AMQ5037: The queue manager task 'DEFERRED_DELIVERY' has started.  
  
  EXPLANATION:  
  The restartable utility task manager has started the DEFERRED_DELIVERY task.  
  This task has now started 1 times.  
  ACTION:  
  None.  
  -------------------------------------------------------------------------------   
  </code></pre>
  
  <p>The <code>mqm</code> user is <code>sudoer</code> and the following is a part of my /etc/group file:</p>
  
  <pre><code>root:x:0:root, mqm, bin
  adm:x:4:root,adm,daemon, mqm, mquser
  mqm:x:500:root, mqm
  mquser:x:502:mqm
  </code></pre>
  
  <p>... regardless all these, I think having <code>MQSNOAUT</code> variable that is set to <code>yes</code> should be enough to work with WebShpere MQ using any user. Maybe something related to RedHat caused the problem.</p>
  
  <p>BTW, searching for <code>The queue manager ended for reason 545284129, ''.</code>, I couldn't find any solution.</p>
  
  <p>Any thoughts?</p>
  
  <p><strong>UPDATE</strong></p>
  
  <p>Having done <code>chmod -R 6550</code> on <code>/opt/mqm/bin</code>, now I can start queue managers and create queue, channel, ... using IBM MQ's command line binaries. For more convenient, however, still I can't use MQ Explorer, because when I run <code>MQExplorer</code> I get the following error:</p>
  
  <pre><code>[mqm@RHEL6-135 bin]$ MQExplorer
  No protocol specified
  MQExplorer: Cannot open display:
  No protocol specified
  No protocol specified
  MQExplorer: Cannot open display:
  MQExplorer:
  An error has occurred. See the log file
  /var/mqm/IBM/WebSphereMQ/workspace-Installation1/.metadata/.log.
  [mqm@RHEL6-135 bin]$
  </code></pre>
  
  <p>Running it with <code>sudo</code> I get this error:</p>
  
  <pre><code>[mqm@RHEL6-135 bin]$ sudo MQExplorer
  [sudo] password for mqm:
  /opt/mqm/java/jre64/jre/bin/java: error while loading shared libraries: libjli.so: cannot open shared object file: No such file or directory
  
  (process:4451): Gtk-WARNING **: This process is currently running setuid or setgid.
  This is not a supported use of GTK+. You must create a helper
  program instead. For further details, see:
  
      http://www.gtk.org/setuid.html
  
  Refusing to initialize GTK+.
  [mqm@RHEL6-135 bin]$
  </code></pre>
  
  <p>and the <code>/var/mqm/IBM/WebSphereMQ/workspace-Installation1/.metadata/.log</code> is as follows:</p>
  
  <pre><code>!SESSION 2017-03-15 16:41:52.369 -----------------------------------------------
  eclipse.buildId=unknown
  java.fullversion=JRE 1.7.0 IBM J9 2.7 Linux amd64-64 Compressed References 20150630_255653 (JIT enabled, AOT enabled)
  J9VM - R27_Java727_SR3_20150630_2236_B255653
  JIT  - tr.r13.java_20150623_94888.01
  GC   - R27_Java727_SR3_20150630_2236_B255653_CMPRSS
  J9CL - 20150630_255653
  BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
  Command-line arguments:  -os linux -ws gtk -arch x86_64
  
  !ENTRY org.eclipse.osgi 4 0 2017-03-15 16:41:54.516
  !MESSAGE Application error
  !STACK 1
  org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
      at org.eclipse.swt.SWT.error(SWT.java:4423)
      at org.eclipse.swt.widgets.Display.createDisplay(Display.java:925)
      at org.eclipse.swt.widgets.Display.create(Display.java:909)
      at org.eclipse.swt.graphics.Device.&lt;init&gt;(Device.java:156)
      at org.eclipse.swt.widgets.Display.&lt;init&gt;(Display.java:507)
      at org.eclipse.swt.widgets.Display.&lt;init&gt;(Display.java:498)
      at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:691)
      at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:162)
      at com.ibm.mq.explorer.ui.rcp.internal.base.RcpApplication.start(RcpApplication.java:88)
      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
      at java.lang.reflect.Method.invoke(Method.java:620)
      at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
      at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
      at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
      at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
  </code></pre>
  
  <p>The log/stacktrace looks like a <code>catch-all</code> exception handling. I didn't yet completely digged into this error but maybe it is also caused by some permission problems. For example, maybe some authorization errors are raised when MQExplorer tries to load it's components from mqm's sub-directories! However, running <code>chmod -R 6550</code> on some related paths didn't solve the problem.</p>