Forum Stats

  • 3,827,458 Users
  • 2,260,778 Discussions
  • 7,897,251 Comments

Discussions

MQRC_NOT_AUTHORIZED using tuxedo MQ Adapter

user878
user878 Member Posts: 25
edited Dec 23, 2013 6:25AM in Tuxedo

We are facing an issue with TM_MQO server that when this server tried to write any message to queue it receives MQRC_NOT_AUTHORIZED. The tuxedo is installed on windows server 2008 and MQ version is 7.0.1.3. The version of tuxedo is 11.

We raised the issue to IBM and they say that the program is providing a user '1717' as alternate user name while putting message to MQ that is causing MQ not able to return the above error. I am unable to locate any user with name 1717 at OS level as well as at tuxedo configuration level. Can someone tell me what user TM_MQO puts as alternate user ID while putting messages to MQ?

Tagged:

Answers

  • Can u paste a glimpse of your ubbconfig (text) regarding  TM_MQO server and The MQ writer code.

    show us how you initialized and performed the write operation?

    If its in Prod - ask them to provide global access as a work around.Till then you can buy time to troubleshoot.

  • user878
    user878 Member Posts: 25

    Hi

    The configuration line for TM_MQO is:

    TM_MQOSRVGRP=MQGRP2_A      SRVID=1780 MIN=1 MAX=1 CLOPT=" -- -C C:\scm\conf\ServProv31.cfg"

    And the contents of the ServProv31.cfg are:

    *SERVER

    minmsglevel=0

    maxmsglevel=9

    defmaxmsglen=4096

    *QUEUE_MANAGER

    NAME=QM_CMSCAGW_51

    *SERVICE

    name=ServProv3

    mqname=TTYY

    TIMEOUT=15

    TRAN=Y

    MAXMSGLEN=4096

    INFIELD=FML_TLVMSG

    The error in ULOG is:

    153840.IDCCMS51!TM_MQO.1952.11992.0: gtrid x0 x52b6dbbe xa8f3: TUXMQ_CAT:1115: TPMQ_EAPP_API MQPUT1 on Queue TTYY failed, Reason = 2035

    153840.IDCCMS51!TMSMQM.10080.13624.0: gtrid x0 x52b6dbbe xa8f3: CMDTUX_CAT:7025: ERROR: tms_abort xa_rollback returned XA_RBROLLBACK for group MQGRP2_A

    When this was taken up with IBM support, they said that disabling the authorization is not possible in 7.0. I am not from where user 1717 is being setup as alternate user name, that is all I am interested to know. I have verified that these is no user with name 1717 in tpusr file of tuxedo.

This discussion has been closed.