title: MQ security - getting a 2035 on one queue
body: <p>I have a application that is trying to put a message to a queue(LOG.TRANSACTION.IN) on a remote queue manager.  The message ends up failing with a 2035 and is put on the DLQ on the local queue manager.  On the local queue manager(QMLOCAL), the application puts the message directly on the SCTQ, since there is no remote queue definition.  The application is running under an ID that has full access to MQ.  I know that is not ideal, but that is for another discussion.  We have an mcauser on the clusrcvr channel on the remote end(QMREMOTE) that has been granted access to the local queue.  I thought I had the security worked out, but it appears that is not the case.  Here is the security information</p>
  
  <p>QMLOCAL:</p>
  
  <pre><code>Entity application_id has the following authorizations for object SYSTEM.CLUSTER.TRANSMIT.QUEUE:  
              get  
              browse  
              put  
              inq  
              set  
              crt  
              dlt  
              chg  
              dsp  
              passid  
              passall  
              setid  
              setall  
              clr  
  </code></pre>
  
  <p>QMREMOTE:</p>
  
  <pre><code>Entity MY_MCAUSER has the following authorizations for object LOG.TRANSACTION.IN:  
          put  
          crt  
          setall  
  </code></pre>
  
  <p>Any help on this would be greatly appreciated.  </p>