IBM Support

SE39477: WMQ V701: MESSAGE AMQ7259 GENERATED FOR CRTMQM COMMAND

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • WMQ user has installed WebSphere MQ V7.0.1.0 and attempts to
    create a queue manager using the CRTMQM command.  Upon
    creation message AMQ7259 (WebSphere MQ Queue manager &1 could
    not obtain data lock) is generated.
     .
     <<<JOBLOG>>>
       Message . . . . : CRTMQM MQMNAME(<QMGRNAME>)
     * MSGAMQ7259 20 20:02:35.97
           F/LIBMQMCS   X/*STMT
           T/QUIMNDRV   X/060C
          From module . . . : AMQXEIMX_N
           From procedure  . : xcsSendMessage
      Statement . . . . : 38
      Message . . . . : WebSphere MQ queue manager <QMGRNAME> could
      not obtain data lock.
      Cause . . . . . :  Queue manager <QMGRNAME> could not be
      started because it could not obtain a lock on its data in the
      file-system. The most likely cause is that the queue manager
      is running on another computer.
      Technical Description . . . . . . . . :   None.
    * MSGCPF0001 30 20:02:36.16
          F/AMQOCRMX   X/*STMT T/QUIMNDRV   X/060C
          From module . . . : AMQOCRMX_N
          From procedure  . : main
          Statement . . . . : 102
      Message . . . . : Error found on CRTMQM command.
    .
    <<< WMQ Trace :AMQ33.0.FMT - line 5914 to 5950 >>>
    000 > zutRequestQMFileLocks
    000      DataPath(/QIBM/UserData/mqm/qmgrs/<QMGRNAME>)
             Flags(0X41)
    001 .> xcsIsEnvironment
    001      xcsIsEnvironment[AMQ_FILE_LOCKS_OFF] = FALSE
    001 .< xcsIsEnvironment rc=OK
    001 .> xcsOpenFileLock
    001      FileName(/QIBM/UserData/mqm/qmgrs/<QMGRNAME>/master)
             LockMode(0X1)
    001 .< xcsOpenFileLock rc=OK
    001      Lock details to write into master: ,1256727755,
              1256727755
    001 .> xcsWriteFileLock
    001      LockData(,1256727755,1256727755)
    001 .< xcsWriteFileLock rc=OK
    001 .> xcsOpenFileLock
    001      FileName(/QIBM/UserData/mqm/qmgrs/<QMGRNAME>/active)
             LockMode(0X1)
    001 .< xcsOpenFileLock rc=OK
    001      Lock details to write into active: ,1256727755,
             1256727755
    001 .> xcsWriteFileLock
    001      LockData(,1256727755,1256727755)
    001 .< xcsWriteFileLock rc=OK
    001 .> xcsCloseFileLock
    001      Data: 0x00000005
    001 .< xcsCloseFileLock rc=OK
    001 .> xcsOpenFileLock
    001      FileName(/QIBM/UserData/mqm/qmgrs/<QMGRNAME>/active)
             LockMode(0X2)
    001 .< xcsOpenFileLock rc=OK
    001 .> xcsReadFileLock
    001 .< xcsReadFileLock rc=OK
    001      Lock details read from active: ,1256727755,
             1256727755
    001 .> xcsCloseFileLock
    001      Data: 0x00000005
    001 .< xcsCloseFileLock rc=OK
    001 .> zutReleaseQMFileLocks
    002 ..> xcsCloseFileLock
    002      Data: 0x00000004
    002 ..< xcsCloseFileLock rc=OK
    001 .< zutReleaseQMFileLocks rc=OK
    000 <!zutRequestQMFileLocks rc=lpiRC_Q_MGR_LOCK_UNAVAILABLE
    .
    Additional Description:
    When starting a queue manager queue where the server does
    not have a hostname, message AMQ8083 and AMQ7260 are
    generated for the STRMQM command.
    .
    

Local fix

  • Add a Host Name for the system using CFGTCP Option 12
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users attempting to create a queue manager at 7.0.1.0 on a
    system with no host name specified in CFGTCP option 12
    
    
    Platforms affected:
    iSeries
    
    ****************************************************************
    PROBLEM SUMMARY:
    WMQ 7010 attempts to use file locks during CRTMQM. Part of the
    file locking mechanism utilizes the TCP host name of the system.
    If no host name is specified in CFGTCP Opt 12, the WMQ code
    incorrectly assumes that the locks cannot be used, and posts the
    AMQ7259 error.
    

Problem conclusion

  • WMQ code has been modified to utilize the serial number of the
    system when no TCP host name is defined. This will allow for the
    file locks to be created and not result in AMQ7259.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.1
    --------           --------------------
    iSeries            tbc_p700_0_1_1
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available, information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    SE39477

  • Reported component name

    WMQ ISERIES V7

  • Reported component ID

    5724H7226

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2009-11-02

  • Closed date

    2009-11-02

  • Last modified date

    2010-02-04

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • RCHMGR
    

Fix information

  • Fixed component name

    WMQ ISERIES V7

  • Fixed component ID

    5724H7226

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
27 April 2020