Topic
  • 3 replies
  • Latest Post - ‏2014-01-29T09:31:19Z by VarunGupta7
SystemAdmin
SystemAdmin
8523 Posts

Pinned topic AMQ7121: when installing a new version of the QMQ trail version

‏2013-02-18T05:49:54Z |
Hi,

I had websphere mq7.1-trial in my redhat machine. I uninstalled it and re-installed WMQ 7.5-trail. But ended up with following message when i tried to create a queue manager after the installation.
AMQ7121: The trial period for this copy of WebSphere MQ has now expired.
Appreciate quick help.

Thanks,
Yumani
Updated on 2013-02-18T10:46:00Z at 2013-02-18T10:46:00Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    8523 Posts

    Re: AMQ7121: when installing a new version of the QMQ trail version

    ‏2013-02-18T10:46:00Z  
    Please can you raise a PMR in order to get this dealt with?

    Cheers
    Morag
  • VarunGupta7
    VarunGupta7
    5 Posts

    Re: AMQ7121: when installing a new version of the QMQ trail version

    ‏2014-01-29T08:07:53Z  

    Hi,

    I've faced the similar situation on AIX box where I've installed the MQ Trial of v7.5. Earlier I was getting the same error and at that time server had MQv6 installed on it. 

    I removed version 6 and installed latest trial of MQv7.5.

    You can find the below screen shot for the same. I have not yet found the remedy for this. Let me know if you've got that fixed earlier.

    $ sudo su - mqm
    $ dspmqver
    Name:        WebSphere MQ
    Version:     7.5.0.2
    Level:       p750-002-130704.TRIAL
    BuildType:   IKAP - (Production)
    Platform:    WebSphere MQ for AIX
    Mode:        64-bit
    O/S:         AIX 6.1
    InstName:    Installation1
    InstDesc:
    Primary:     Yes
    InstPath:    /usr/mqm
    DataPath:    /var/mqm
    MaxCmdLevel: 750
    $ dspmq
    $ crtmqm QM1
    AMQ7121: The trial period for this copy of WebSphere MQ has now expired.

     

    Thanks & Regards !!

    Varun

  • VarunGupta7
    VarunGupta7
    5 Posts

    Re: AMQ7121: when installing a new version of the QMQ trail version

    ‏2014-01-29T09:31:19Z  

    As a matter of fact and testing on the Lab Server, re-installation (un-install and install) of MQv7.5 Trail has been done after REMOVING the Files of Old MQ from /var/mqm FS.

    Also made sure that un-installation of MQv7.5 has cleared all the MQ Setup files from /usr/mqm. And after that checked up the FS /var/mqm and cleared it up.

    $ sudo su - mqm
    $ dspmqver
    Name:        WebSphere MQ
    Version:     7.5.0.2
    Level:       p750-002-130704.TRIAL
    BuildType:   IKAP - (Production)
    Platform:    WebSphere MQ for AIX
    Mode:        64-bit
    O/S:         AIX 6.1
    InstName:    Installation1
    InstDesc:
    Primary:     Yes
    InstPath:    /usr/mqm
    DataPath:    /var/mqm
    MaxCmdLevel: 750
    $ crtmqm QM1
    There are 90 days left in the trial period for this copy of WebSphere MQ.
    WebSphere MQ queue manager created.
    Directory '/var/mqm/qmgrs/QM1' created.
    The queue manager is associated with installation 'Installation1'.
    Creating or replacing default objects for queue manager 'QM1'.
    Default objects statistics : 74 created. 0 replaced. 0 failed.
    Completing setup.
    Setup completed.
    $ dspmq
    QMNAME(QM1)                                               STATUS(Ended immediately)
    $ strmqm QM1
    There are 90 days left in the trial period for this copy of WebSphere MQ.
    WebSphere MQ queue manager 'QM1' starting.
    The queue manager is associated with installation 'Installation1'.
    5 log records accessed on queue manager 'QM1' during the log replay phase.
    Log replay for queue manager 'QM1' complete.
    Transaction manager state recovered for queue manager 'QM1'.
    WebSphere MQ queue manager 'QM1' started using V7.5.0.2.
    $ dspmq
    QMNAME(QM1)                                               STATUS(Running)
    $

     

    So every time you hit the command, you get the alert for how many days are left for your trial, to keep you on toes.

    It's been fixed.

    But you could let us know if there was an another better fix for this issue, which you could have used in your system. Thanks !!