Skip to main content

Posts

Showing posts from October, 2011

WebSphere MQ for Windows v6.0 Explorer Trace - Middleware News

WebSphere MQ for Windows v6.0 Explorer Trace - Middleware News Follow the instructions listed below to run trace for the WebSphere MQ for Windows v6.0 Explorer using the MQ Java API. Modify the files runmqcfg.cmd and runmqcfg_rcp.cmd in the directory C:\Program Files\IBM\WebSphere MQ\bin Add the following line, which specifies the properties file in C:\TEMP\internal.properties set AMQ_EXPLORER=%AMQ_EXPLORER% "-Dcom.ibm.mq.commonservices=C:\TEMP\internal.properties" Note: The command must be typed on ONE LINE in the runmqcfg.cmd and runmqcfg_rcp.cmd files and BEFORE the statement: start "WebSphere MQ Explorer" %AMQ_EXPLORER% Create a file internal.properties in the C:\TEMP directory as with the following text: Diagnostics.MQ=enabled Diagnostics.Java=explorer,wmqjavaclasses,all #Diagnostics.Java=explorer Diagnostics.Java.Trace.Detail=high Diagnostics.Java.Trace.Destination.File=enabled Diagnostics.Java.Trace.Destination.Console=disabled Diagnostics.Jav

WebSphere MQ for Windows trace - Middleware News

WebSphere MQ for Windows trace - Middleware News Follow the instructions listed below to start, stop and format WebSphere MQ for Windows trace. Start trace: normal : strmqtrc Or start a high detail trace: strmqtrc -t all -t detail Or start a high detail wrapping trace and limit the file size to 5MB : strmqtrc -l 5 -t all -t detail End trace: endmqtrc Format trace: No formatting is required The trace records are written to the following directory where is the directory where WebSphere MQ was installed. MQ 5.3: \errors MQ 6: \trace On Windows, the trace files are readable without formatting. However, they are still called AMQppppp.TRC (where ppppp is the process identifier or pid which created the file) rather than AMQppppp.FMT.

WebSphere MQ for HP-UX - Middleware News

WebSphere MQ for HP-UX - Middleware News Follow the instructions listed below to start, stop and format WebSphere MQ for HP-UX 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 5 MB : 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 re

WebSphere MQ for HP-UX - Middleware News

WebSphere MQ for HP-UX - Middleware News Follow the instructions listed below to start, stop and format WebSphere MQ for HP-UX 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 5 MB : 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 A

WebSphere MQ for AIX Trace V6.0 - Middleware News

WebSphere MQ for AIX Trace V6.0 - Middleware News 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 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 M

WebSphere MQ for AIX Trace V6.0 - Middleware News

WebSphere MQ for AIX Trace V6.0 - Middleware News 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 trace formatter program converts binary files named AMQppppp.TRC (where ppppp is the process identifier or pid which created the file) into readable files nam

adsrerrapop