Skip to main content

mqat.ini file in IBM WebSphere MQ 7.5 - Middeware News

[root@karthik KARTHICK]# dspmqver
Name:        WebSphere MQ
Version:     7.5.0.1
Level:       p750-001-130308.1
BuildType:   IKAP - (Production)
Platform:    WebSphere MQ for Linux (x86-64 platform)
Mode:        64-bit
O/S:         Linux 2.6.32-220.el6.x86_64
InstName:    Installation1
InstDesc:
InstPath:    /opt/mqm
DataPath:    /var/mqm
Primary:     Yes
MaxCmdLevel: 750
[root@karthik KARTHICK]#


[root@karthik KARTHICK]# cat mqat.ini
#*******************************************************************#
#* Module Name: mqat.ini                                           *#
#* Type       : WebSphere MQ queue manager configuration file      *#
#  Function   : Define the configuration of application activity   *#
#*              trace for a single queue manager.                  *#
#*                                                                 *#
#*******************************************************************#

AllActivityTrace:           # Global settings stanza
  ActivityInterval=1        # Time interval between trace messages
                            #   Values: 0-99999999 (0=off)
                            #   Default: 0
  ActivityCount=100         # Number of operations between trace msgs
                            #   Values: 0-99999999 (0=off)
                            #   Default: 0
  TraceLevel=MEDIUM         # Amount of data traced for each operation
                            #   Values: LOW | MEDIUM | HIGH
                            #   Default: MEDIUM
  TraceMessageData=0        # Amount of message data traced
                            #   Values: 0-104857600
                            #   Default: 0
  StopOnGetTraceMsg=ON      # Stop trace on get of activity trace message
                            #   Values: ON | OFF
                            #   Default: ON

##################################################################
# Prevent the sample activity trace program from generating data #
##################################################################
ApplicationTrace:           # Application specific settings stanza
  ApplClass=ALL             # Application type
                            #   Values:  (USER | MCA | ALL)
                            #   Default: USER
  ApplName=amqsact*         # Application name (may be wildcarded)
                            #   (matched to app name without path)
                            #   Default: *
  Trace=OFF                 # Activity trace switch for application
                            #   Values:  ( ON | OFF )
                            #   Default: OFF
  ActivityInterval=0        # Time interval between trace messages
                            #   Values: 0-99999999 (0=off)
                            #   Default: 0
  ActivityCount=0           # Number of operations between trace msgs
                            #   Values: 0-99999999 (0=off)
                            #   Default: 0
  TraceLevel=MEDIUM         # Amount of data traced for each operation
                            #   Values: LOW | MEDIUM | HIGH
                            #   Default: MEDIUM
  TraceMessageData=0        # Amount of message data traced
                            #   Values: 0-104857600
                            #   Default: 0

[root@karthik KARTHICK]#
Labels:

Comments

Post a Comment

adsrerrapop

Popular posts from this blog

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure
136 comments
Read more

IBM Websphere MQ Reason code list / mq reason codes / websphere mq error codes / mq error messages

Reason code list ================= The following is a list of reason codes, in numeric order, providing detailed information to help you understand them, including: * An explanation of the circumstances that have caused the code to be raised * The associated completion code * Suggested programmer actions in response to the code * 0 (0000) (RC0): MQRC_NONE * 900 (0384) (RC900): MQRC_APPL_FIRST * 999 (03E7) (RC999): MQRC_APPL_LAST * 2001 (07D1) (RC2001): MQRC_ALIAS_BASE_Q_TYPE_ERROR * 2002 (07D2) (RC2002): MQRC_ALREADY_CONNECTED * 2003 (07D3) (RC2003): MQRC_BACKED_OUT * 2004 (07D4) (RC2004): MQRC_BUFFER_ERROR * 2005 (07D5) (RC2005): MQRC_BUFFER_LENGTH_ERROR * 2006 (07D6) (RC2006): MQRC_CHAR_ATTR_LENGTH_ERROR * 2007 (07D7) (RC2007): MQRC_CHAR_ATTRS_ERROR * 2008 (07D8) (RC2008): MQRC_CHAR_ATTRS_TOO_SHORT * 2009 (07D9) (RC2009): MQRC_CONNECTION_BROKEN * 2010 (07DA) (RC2010): MQRC_DATA_LENGTH_ERROR * 2011 (07DB) (RC2011): MQRC_DYNAMIC_Q_NAME_ERROR * 2012 (07DC) (RC201
2 comments
Read more

IBM WebSphere MQ – Common install/uninstall issues for MQ Version on Windows - Middleware News

Creating a log file when you install or uninstall WebSphere MQ WebSphere MQ for Windows is installed using the Microsoft Installer (MSI). If you install the MQ server or client through launchpad , MQPARMS or setup.exe , then a log file is automatically generated in %temp% during installation. Alternatively you can supply parameters on the installation MSI command msiexec to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). If you uninstall through the Windows Add/Remove programs option, no log file is generated. You should either uninstall from the MSI command line and supply parameters to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). For details on how to enable MSI logging, see the following article in the WebSphere MQ product documentation: Advanced installation using msiexec For details on how to enable system-w
Post a Comment
Read more