MQ

MQ

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  QM log management clarifications

    Posted Fri August 04, 2023 10:27 AM

    Hello MQ community users,

    I have an AIX QM (v9.1.x LTS)  that was initially configured (10 years ago) to use Linear Logging without Log management  (Automatic or Archive) of log extents (qm.ini -> Log stanza). Recently (less than a year) the QM was configured to use Circular logging).

    The above resulted to 518 log extents (S000xxxx.LOG) under /var/mqm/log/QMGRname/active...     

    (oldest: S0005684.LOG...........most recent: S0006199.LOG).

    AMQ8705I: Display Queue Manager Status Details.
       QMNAME(xxxxxx)                          STATUS(RUNNING)
       ARCHLOG( )                              ARCHSZ(0)
       CURRLOG(S0006199.LOG)                   LOGINUSE(8)
       LOGPATH(/var/mqm/log/MQDLRP/active/)    LOGUTIL(25)
       MEDIALOG(S0006186.LOG)                  MEDIASZ(51)
       RECLOG(S0006199.LOG)                    RECSZ(1)
       REUSESZ(0) 

    The oldest log required for QM's recovery is S0006186.LOG (MEDIALOG VALUE), meaning that only 16 out of 518 log extents are actually need for QM's recovery.

    My question is the f ollowing:

    Given that currently QM is configured to use CIRCULAR LOGGING,  is there a way to automatically clean/delete unused log extents, similar to the way Automatic or Archive Log Management handles not required log extents on LINEAR LOGGING?

    For instance, is it recommended to use the RESET QMGR TYPE(REDUCELOG) REDUCE(MAX or AUTO)  in order to reduce the max no of log extents possible, or delete the unused/not required log extents manually (obviously when QM is not running)?

    Since we are dealing with a Production QM, which is the suggested way?

    Any advise will be much appreciated.

    Thanks in Advance,

    Rgds, Nick.



    ------------------------------
    NICK DAKORONIAS
    Application Integration & Middleware Solution Certified Specialist
    Kyndryl
    Athens
    ------------------------------


  • 2.  RE: QM log management clarifications

    Posted Mon August 07, 2023 01:07 AM

    Hi Nick,

    Any log that is prior to the log needed to restart the queue manager can be removed while the queue manager is running.

    So in your case I'd look at removing all the logs prior to 6186. I might as a precaution keep the number of primaries and secondaries needed starting from one.

    If the command works I would first try and reduce the logs running the reset qmgr type(reducelog) reduce(max). This way you let the qmgr decide which logs to get rid of because it doesn't need them anymore...

    Hope it helps



    ------------------------------
    Francois Brandelik
    ------------------------------



  • 3.  RE: QM log management clarifications

    Posted Mon August 07, 2023 11:04 AM

    You state "Recently (less than a year) the QM was configured to use Circular logging" but then go on to show a DIS QMSTATUS which includes MEDIALOG and MEDIASZ.

    I'd speculate that you have NOT correctly configured the QM to use circular logging as these attributes would not be shown on a circular logging queue manager.

    For example you CANNOT change the log type by simply editing qm.ini.  You need to use the migmqlog command to migrate between linear and circular logging.



    ------------------------------
    Andrew Hickson
    ------------------------------



  • 4.  RE: QM log management clarifications

    Posted Tue August 08, 2023 06:11 AM

    Thanks for the notification Andrew.

    Then in my case, I assume I have to run the command: migmqlog -m QMGRname -lc  so that QM to be reconfigured to use circular logging. 

    Obviously this command should be executed after stopping & taking backup of QM.



    ------------------------------
    Nick Dakoronias
    ------------------------------