MQSeries.net :: View topic - FYI

tczielke · Posted: Fri Aug 07, 2015 6:20 am Post subject:

This APAR is worth noting if you use the Application Activity Trace -> http://www-01.ibm.com/support/docview.wss?uid=swg1IT09496&myns=swgws&mynp=OCSSFKSJ&mync=R&cm_sp=swgws-_-OCSSFKSJ-_-R

I ran across it when I inadvertently copied a Unix based mqat.ini (the lines only end with \n) to a Windows server where it expects the mqat.ini lines to end with both a \r \n. In my case, encountering the issue in the APAR was sporadically consistent. There were three Windows queue managers that had the Unix based mqat.ini file. Only two of the three queue managers saw the issue. For the two queue managers that saw the issue, they encountered it every time that I turned on the Activity Trace with ALTER QMGR ACTVTRC(ON) ). Also, when I encountered the issue, the queue manager become unstable and had to be restarted to be corrected.

I wanted to mention my experience, since it is a very serious issue when it happens. However, I use the Activity Trace a fair bit on Solaris/Linux and Windows, and I have only seen it happen for the above use case. In the PMR that I opened, there was mention that another customer had encountered the issue due to how that mqat.ini file was formatted. However, the APAR does not state that this issue is caused by the format of the mqat.ini file.
_________________
Working with MQ since 2010.