Middleware News

You are using WebSphere MQ 7.0.1.8 or later (MQ 7.1.0.1 or later; MQ 7.5 or later) and you have opened an IBM Service Request ticket (PMR) to report a problem and you need to provide the MQ error logs, FDC files, version/fix pack of MQ, etc. Is there a tool that you could use to gather those files and optionally send them to IBM Support via ftp? Yes, you can use the MQ "runmqras" tool. The utility "runmqras" is a Java based tool shipped with WebSphere MQ. Note: Although runmqras is available since 7.0.0.0 as a proof of concept, not until 7.0.1.8, 7.1.0.1 and 7.5 did the tool became fully functional. a) If you are going to gather information from all the queue managers, issue the following, assuming that the PMR number is 01234,567,890 (for the flag "-pmrno"). The flag "-ftp IBM" indicates that the resulting zip file will be sent via ftp to the IBM ftp server used for receiving PMR data. runmqras -ftp IBM -pmrno 01234,56

Follow the instructions listed below to run trace for the WebSphere MQ for Linux V6 and V7 Explorer using the MQ Java API: 1. Modify the files runmqcfg.cmd and runmqcfg_rcp.cmd in the directory: /opt/mqm/bin Modify the line: AMQ_EXPLORER="./eclipse" to the following, according to the version of MQ: v6.0: AMQ_EXPLORER="/opt/mqm/ies30/eclipse/eclipse" v7.0: AMQ_EXPLORER="/opt/mqm/eclipseSDK33/eclipse/eclipse" And add the single line: AMQ_EXPLORER="$AMQ_EXPLORER -Dcom.ibm.mq.commonservices=/tmp/internal.properties" before the statement cd $AMQECLIPSE 2. Both of these scripts are dependent on the environment variable AMQECLIPSE. If this environment variable does not exist then it should be created as the first line in the script. For example: v6.0: export AMQECLIPSE="/opt/mqm/ies30/eclipse" v7.0: export AMQECLIPSE="/opt/mqm/eclipseSDK33/eclipse" Note: If you want, you can include the above

Follow the instructions listed below to start, stop and format WebSphere MQ for Linux trace. Trace files are written to the directory /var/mqm/trace, so delete or relocate old trace files before beginning a new trace. Start trace for every WebSphere MQ process: strmqtrc -e Or start trace only for one queue manager: strmqtrc -m MY.QMGR Or start a high detail trace for one queue manager: strmqtrc -t all -t detail -m MY.QMGR Or start a high detail wrapping trace and limit the file size to ~5MB: strmqtrc -l 5 -t all -t detail -m MY.QMGR End all tracing: endmqtrc -a Format the trace files: dspmqtrc *.TRC Or format wrapping trace files: dspmqtrc *.TRC *.TRS The trace formatter program converts binary files named AMQppppp.TRC (where ppppp is the process identifier or pid which created the file) into readable files named AMQppppp.FMT. If you used a wrapping trace, then each time a .TRC reaches the size limit MQ renames it to a .TRS extension and starts a n

WebSphere MQ V6 and V7 on AIX now supports the standard WebSphere MQ trace facility as well as the AIX system trace. It is recommended that V6 and V7 customers use the WebSphere MQ trace commands unless requested by the WebSphere MQ service team to use the AIX system trace hooks. Follow the instructions listed below to start, stop and format WebSphere MQ for AIX trace. Trace files are written to the directory /var/mqm/trace, so delete or relocate old trace files before beginning a new trace. Start trace for every WebSphere MQ process: strmqtrc -e Or start trace only for one queue manager: strmqtrc -m MY.QMGR Or start a high detail trace for one queue manager: strmqtrc -t all -t detail -m MY.QMGR Or start a high detail wrapping trace and limit the file size to ~5MB: strmqtrc -l 5 -t all -t detail -m MY.QMGR End all tracing: endmqtrc -a Format the trace files: dspmqtrc *.TRC Or format wrapping trace files: dspmqtrc *.TRC *.TRS The trac

What is the purpose of the MAXHANDS queue manager parameter? MAXHANDS (Maximum Open Handles) is the queue manager parameter that limits the number of handles that any one process can have at the same time. The details relating to it are as follows: Setting MAXHANDS: Alter the MAXHANDS queue manager parameter using the MQSC alter queue manager command. Example: alter qmgr maxhands (300) On Windows you can also use the WebSphere MQ Explorer to alter the queue manager's Max handles, extended property. MAXHANDS(integer): The maximum number of open handles that any one task can have at the same time. This is a value in the range zero through 999 999 999. For clarification: MAXHANDS refers to the maximum number of objects that a single connection can have open at the same time. So, if an application thread issues an MQOPEN for a queue, that counts as 1, and so on for each queue that is opened in that thread. A separate thread in the same or in a differ