IBM WAS/MQ/MB/DATAPOWER Administration Training

Attend Free Demo On DevOps & IBM Data Power On 22nd September (Saturday) at 7 am IST.

2018-09-17T03:56:00.000-07:00

Please refer and inform to your friends & colleagues

For Enquiry call on +91 789 375 1171
Email us: mailme.mq@gmail.com

Hi, Greetings!! I would like to bring blogger notice we are providing training on following technologies with real time experts.

On Every Saturday you can attend demo session.

* IBM Data Power Administration

* IBM Data Power Development

* IIB Development

* DevOps

* Python

* IBM WAS

* IBM MQ

Send What's App Request On +91 789 375 1171

2017-07-24T23:57:00.001-07:00

Madhu Kandula Available in What's App, Send Request On +91 789 375 1171

For Training On WAS, MQ, MB & DataPower. Administration & Development

New Batches Available On WebSphere

2017-07-24T23:52:00.002-07:00

Hi, Greetings!! I would like to bring blogger notice we are providing training on IBM Websphere Family.

Please refer and inform to your friends & colleagues

For Enquiry call on +91 789 375 1171

Email us: mailme.mq@gmail.com

1) IBM Websphere MQ Administration

By Mr. Madhu Kandula (IBM MQ Certified Professional) 6 years of experience

2) WAS (IBM Websphere Application Server) V8.5 Administration

By Mr. Satya (IBM Certified Professional) 10+ years of experience.

3) IIB (IBM Websphere Message Broker) Administration
By Mr. Ram (IBM Certified Professional) 10+ years of experience

4) IIB (IBM Integration Bus) Development

By Mr. Pavan (IBM Certified Professional) 10+ years of experience

5) IBM DataPower Administration

By Mr. Madhu (IBM Certified Professional) 5+ years of experience

IBM MQ Overview

2014-06-01T20:16:00.002-07:00

IBM MQ

A member of websphere family from IBM. Websphere MQ (formally MQseries) is the standard for messaging across multiple platforms, including windows, linux, IBM mainframe and midrange and Unix flavors.
A middleware product that implements a messaging and queuing framework
Middleware - an intermediate software component that bridges dissimilar computing environments.
WebSphere MQ is your complete universal messaging backbone, enabling rapid, reliable, and secure transport of messages and data between applications, systems, and services.
It accelerates the flow of messages across organizations without complexity, cutting costs and reducing maintenance, improving business responsiveness and connecting to new solutions and technologies from the mainframe to the mobile enterprise.

"WebSphere MQ is an assured delivery mechanism, which consists of queues managed by Queue Managers. We can put messages onto, and retrieve messages from queues, and the movement of messages between queues is facilitated by components called Channels and Transmission Queues."

IBM WebSphere MQ Client Overview

2014-02-15T00:38:00.002-08:00

An IBM WebSphere MQ client is part of the IBM WebSphere MQ product that can be installed on its own, on a separate machine from the MQ server. You can run an IBM WebSphere MQ application on an IBM WebSphere MQ client, which interacts with one or more IBM WebSphere MQ servers. The IBM WebSphere MQ client connects to queue managers by means of a communications protocol. The servers to which the client connects might or might not be part of an IBM WebSphere MQ cluster.

The queues and other IBM WebSphere MQ objects are held on a queue manager that you have installed on an MQ server machine. When the application issues a client call, the IBM WebSphere MQ client directs the request to a queue manager, where it is processed and from where a reply is sent back to the IBM WebSphere MQ client. The link between the MQ application and the IBM WebSphere MQ client is established dynamically at runtime.

Messages Backup On Queues Using Qload & Unload Utility

2014-02-06T02:50:00.002-08:00

Create Queue Manager:

CRTMQM QM1

Start Queue Manager:

STRMQM QM1

Get RUNMQSC Console For Queue Manager:

RUNMQSC QM1

Create Two Local Queues:

DEFINE QLOCAL(Q1)

DEFINE QLOCAL(Q2)

Put 10 messages into Q1.

Download MO03 Support Pack To Do Following Operations.

Link: http://www-01.ibm.com/support/docview.wss?uid=swg24009368

Unload a Queue to a File

qload –m QM1 –i Q1 –f c:\myfile

Load a Queue from a File

qload –m QM1 –o Q1 –f c:\myfile

Copy the messages from one Queue to another Queue

qload –m QM1 –i Q1 -o Q2

Copy the first 10 messages from one Queue to another Queue

qload –m QM1 –i Q1 –o Q2 –r#10

Option	Meaning
x	Process message number x only.
x..y	Process message number x through y only
x#y	Process y messages starting from message x
#y	Process y messages starting from the beginning. Note: This is the same as 1#y

Move the messages from one Queue to another Queue

qload –m QM1 –I Q1 –o Q2

Dead Letter Handler Configuration Using Service Object

2014-01-11T00:16:00.003-08:00

Configuring the DLQ Handler as a server service object:

To run the DLQ handler as a service, you need to define a server service object in that queue manager. This example uses a batch file and rules table for the DLQ Handler.

Step:1 Configure Dead Letter Queue For Queue Manager:

Define QLocal(DEAD.QUEUE) LIKE(SYSTEM.DEAD.LETTER.QUEUE)

ALTER QMGR DEADQ(DEAD.QUEUE)

ALTER QL(LOCAL-QUEUE-NAME) MAXDEPTH(5)

Step:2 Create Batch File

Contents of dlqhandler.bat

cd "C:\Program Files\IBM\WebSphere MQ\bin"

runmqdlq %1 %2 %3

The rules table should be defined with some REASON and ACTION sequence and WAIT (YES), which means that the DLQ Handler waits indefinitely for further messages to arrive on the DLQ.

Step:3 Rules table Content : File Name is-- RULETBL.RUL

WAIT(YES) RETRYINT(20)

REASON(*) ACTION(FWD/RETRY/DISCARD/IGNORE) FWDQ('QUEUENAME') FWDQM('QMGRNAME')

Step:4 Define server service object for DLQ Handler

DEFINE SERVICE(dlqhandler) +

SERVTYPE(SERVER) +

CONTROL(QMGR) +

STARTCMD('C:\IBM\WebSphere\MQ\dlqhandler.bat') +

DESCR('dead letter queue handler as server service') +

STARTARG('DEADQ IBMQMR < C:\IBM\WebSphere\MQ\RULETBL.RUL') +

STDOUT('C:\IBM\WebSphere\MQ\Log.txt') +

STDERR('C:\IBM\WebSphere\MQ\Err.txt') +

REPLACE

You can set CONTROL to MANUAL, QMGR, or STARTONLY based on your requirements. The value of STARTCMD is the absolute path of the executable file dlqhandler.bat (on Windows).

Step:5 Start Service:

Start service(dlqhandler)

Step:6 Display Service Status:

Display SVStatus(dlqhandler)

Step:7 Send 10 Messages From Source

5 messages are get stored on local queue

5 messages are get stored on DEAD.QUEUE.

Retrieve messages on local queue. dead letter handler will process messages to local queue.

How To Install IBM MQ On Windows

2013-08-13T07:00:00.003-07:00

Installation On Windows

Login as Administrator to the destination windows server using Remote Desktop Connection Tool
Check hostname of the windows server (command is--- hostname). Hostname should not contain any spaces

We must check Hardware & Software requirements to proceed our MQSeries installation

How much disk space is free. How much disk space is required for our configuration. (command is -- dir | find "free") 900MB required for full installation.
Speed of the processor.
Hardware type (32 bit or 64 bit) (command is--- systeminfo)
Get MQseries Software Dump to our destination server.
Check whether MQSeries installation supports our destination platform or not by invoking MQLaunchpad
Check Eclipse installation required for our MQSeries features.If it is required we must install Eclipse first.

How To Install Eclipse & MQSeries

Find following path then invoke the setup.exe. (Path is ---- MQV7.X/prereqs/IES/setup.exe)
Find MQLaunchpad in the following path. (Path is ----- MQV7.X/MQLaunch.exe)
Click On Software requirements in the MQ Installation Wizard. Following wizard shows prerequisite softwares has installed or not

Click on WebSphereMQ Installation and then click on Launch IBM WebSphere MQ Installer.

It opens following window. accept the license agreement

Choose setup type

select folder for program files and then click on next

select data-files folder and then click on next

select Global securityKit files folder and then click on next

select log files folder and then click on next

select features to install in the following window

In the following window we can have a look what are the features selected to install and then click on install

After installation check MQSeries Installed Version Info Using Command “dspmqver”. (open command prompt then execute command)

What is a Resource Manager, Transaction & Syncpoint

2013-04-03T00:26:00.002-07:00

What is a resource manager?

A resource manager is a computer subsystem that owns and manages resources that can be accessed and updated by applications (i.e., WMQ queue manager – whose resources are its queues, DB2 database – whose resources are its tables).

What is a unit of work?

When a application updates the resources of one or more resource managers, it's often vital that all updates complete successfully as a group, or none of them complete. Updates that complete this way are said to occur within a 'unit of work' or 'transaction'.

What is a sync point coordinator?

The point in time when all updates within a unit of work are either committed or backed out is called a 'sync point'. The computer subsystem that manages units of work is called a sync point coordinator.

What Is Dead Letter Queue & Dead Letter Handler

2013-04-03T00:14:00.001-07:00

Dead Letter Queue (DLQ)

- When messages can not be delivered to the intended queue, the messages may be delivered to a Dead Letter Queue (DLQ) if the queue manager has one defined.

- By default a queue manager does not have a Dead Letter Queue but you should define one for every queue manager.

- In every Queue Manager default dead letter queue is SYSTEM.DEAD.LETTER.QUEUE.

Dead Letter Messages

1) Messages can be placed on the DLQ by the queue manager, the channels (MCA) or by applications
2) When the messages are put onto DLQ, they should have a Dead Letter Header (DLH). DLH will be generated by Queue manager and MCA.
3) If application are putting the messages onto DLQ, applications must create the Dead Letter Header (DLH) to message.

Dead Letter Queue Handler

Once a message arrives on the DLQ you can automate the handling of that message using the DLQ handler program. You can have the handler running and waiting for messages to arrive on the DLQ or you can set up the DLQ to trigger the start of the handler program

Starting the DLQ Handler
You can start the DLQ handler using the RUNMQDLQ command.
Example: RUNMQDLQ -Q <DEDA LETTER QUEUE NAME> -M <QMGR NAME> <rules.tb

where DLQ = name of your dead letter queue
QMGR = queue manager name and
rules.tb is a file with your rules table

Rules Table
It Defines how the DLQ handler will process the messages on the DLQ
Two types of entries in the rules table
-Control Data
-Rules

runmqdlq can take rules table from command line or redirect from file.

Sample Program

Websphere MQ supplies a sample program called amqsdlq which provides similar function as runmqdlq. This allows users to customize the way messages are handled from the DLQ, especially useful if you have applications placing messages directly onto DLQ.

How to write Rules in rule table explained
Rule table is looks something like: Pattern/Keyword Action. ( simillat to find a particular keyword and the do the action specified)

Pattern Keywords – allow you to match only certain messages on the DLQ
Ex: REASON – match only messages with a specified reason code

Action Keywords describe how a matching message is processed
ACTION(DISCARD|IGNORE|RETRY|FWD)
FWDQ – name of queue where message is forwarded
FWDQM – name of qmgr where message is forwarded
HEADER(YES|NO) – do messages have DLH header
PUTAUT(DEF|CTX) – userid of runmqdlq program or userid from the MD of the message on the DLQ
RETRY – number of times to retry each matching rule

More about Rule Table
1) A rules table must contain at least one rule.
2) Keywords can occur in any order.
3) A keyword can be included only once in any rule.
4) Keywords are not case-sensitive.
5) A keyword and its parameter value must be separated from other keywords by at least one blank space or comma.
6) There can be any number of blanks at the beginning or end of a rule, and between keywords, punctuation, and values.
7) Each rule must begin on a new line.
8) For reasons of portability, the significant length of a line must not be greater than 72 characters.

Sample Rule Table
***************************************************
* An example rules table for the runmqdlq command *
***************************************************
* Control data entry
* ------------------
* If parameters are not supplied on the runmqdlq command use
* SYSTEM.DEAD.LETTER.QUEUE as the input queue, use QM1_TEST as the
* queue manager and set retry interval to 20 seconds
inputq('SYSTEM.DEAD.LETTER.QUEUE') inputqm('QM1_TEST') retryint(20)

* Rules entries
* -----
* Include a rule with ACTION (RETRY) first to try to deliver the
* message to the intended destination. If a message is placed on the
* DLQ because its destination queue is full, attempt to forward the
* message to its destination queue. Make 5 attempts at approximately
* 20 second intervals (the default value for RETRYINT). Also include
* the "+" just to show how to wrap a command over to the next line.
REASON(MQRC_Q_FULL) ACTION(RETRY) RETRY(5)
* If a message is placed on the DLQ due to put inhibited, attempt to
* forward the message to its destination queue. Make 5 attempts at
* approximately 20 second intervals (the default value for RETRYINT).
REASON(MQRC_PUT_INHIBITED) ACTION(RETRY) RETRY(5)
* Include a rule to handle messages which do not match any of the
* patterns specified above. Send the messages to another queue named
* DEADQ where they can be handled later.
ACTION(FWD) FWDQ('DEADQ')

Runmqdlq examples
If you use the DLQ handler without redirecting stdin from a file (the rules table), the DLQ handler reads its input from the keyboard.
In WebSphere MQ for AIX, Solaris, HP-UX, and Linux, the DLQ handler does not start to process the named queue until it receives an end_of_file (Ctrl+D) character.
In WebSphere MQ for Windows it does not start to process the named queue until you press the following sequence of keys: Ctrl+Z, Enter, Ctrl+Z, Enter

C:\>runmqdlq SYSTEM.DEAD.LETTER.QUEUE QM1_TEST
WAIT(YES) RETRYINT(20)
REASON(MQRC_Q_FULL) ACTION(RETRY) RETRY(5)
REASON(MQRC_PUT_INHIBITED) ACTION(RETRY) RETRY(5)
REASON(*) ACTION(FWD) FWDQ('DEADQ')
^Z

2005-04-08 02.20.09 AMQ8708: Dead-letter queue handler started to process
INPUTQ(SYSTEM.DEAD.LETTER.QUEUE)

MQ Reason Codes

2012-10-05T00:19:00.001-07:00

2001

2009

2016

2025

2027

2029

2030

2031

2033

2035

2036

2037

2038

2039

2040

2101

2537

2538

2539

2540

2051

2052

2053

2058

2059

2092

2196

2195

2197

2198

2199

2189

MQRC_ALIAS_BASE_Q_TYPE_ERROR

MQRC_CONNECTION_BROKEN

MQRC_GET_INHIBITED

MQRC_MAX_CONNS_LIMIT_REACHED

MQRC_MISSING_REPLY_TO_Q

MQRC_MSG_TYPE_ERROR

MQRC_MSG_TOO_BIG_FOR_Q

MQRC_MSG_TOO_BIG_FOR_Q_MGR

MQRC_NO_MSG_AVAILABLE

MQRC_NOT_AUTHORIZED

MQRC_NOT_OPEN_FOR_BROWSE

MQRC_NOT_OPEN_FOR_INPUT

MQRC_NOT_OPEN_FOR_INQUIRE

MQRC_NOT_OPEN_FOR_OUTPUT

MQRC_NOT_OPEN_FOR_SET

MQRC_OBJECT_DAMAGED

MQRC_CHANNEL_NOT_AVAILABLE

MQRC_HOST_NOT_AVAILABLE

MQRC_CHANNEL_CONFIG_ERROR

MQRC_UNKNOWN_CHANNEL_NAME

MQRC_PUT_INHIBITED

MQRC_Q_DELETED

MQRC_Q_FULL

MQRC_Q_MGR_NAME_ERROR

MQRC_Q_MGR_NOT_AVAILABLE

MQRC_XMIT_Q_USAGE_ERROR

MQRC_UNKNOWN_XMIT_Q

MQRC_UNEXPECTED_ERROR

MQRC_UNKNOWN_DEF_XMIT_Q

MQRC_DEF_XMIT_Q_TYPE_ERROR

MQRC_DEF_XMIT_Q_USAGE_ERROR

MQRC_CLUSTER_RESOLUTION_ERROR

Linux Basic Commands

2012-09-29T07:20:00.001-07:00

$ -- Normal User Prompt
# -- System Admin Prompt

Commands

$ logname (or) whoami --------- To Check Present Working User
$ who ---------------------------- To Know Present Working Users
$ hostname --------To Know HostName(Machine Name) Of A Server
$ ifconfig ---------- To Find an IP
$ lscpu ------------- To check CPU architecture
$ su [super user name] ---- Switch to Super User
$ clear---------- To Clear Screen
$ exit ------------To exit From user Session
$ man [cmd]----------- Help Facility
$ date ----------- To Display date
$ cal [month] [year] ----- To Display Calender
$ pwd ---------- To Know Present Working Directory
$ ls [flags]--------------To Display Directory Content
$ mkdir [dir name]---------- To Create New Directory
$ cd [dir name] -------------- To Change Directory
$ mv [oldname] [newname) -------- To Rename Directory
$ rmdir [Directory Name] ---------- To delete directory
$ mv [source path] [target path] ---- To Move directory with sub directories
$ cp [source path] [target path] ---- To Copy directory with sub directories
$ cat > [file name] ----------------- To Create File
$ cp [source file] [target file] ------- To Copy A File
$ mv [Old File] [New File] --------- To Rename A File
$ rm [file name] --------------------- To Remove A File
$ locate [file name] ------------------- To Search A file In Whole File System
$ find [file name] [path] ---------------- To Search A file in Specified Path
$ gzip [file name] ---------------------- To Compress A File
$ gunzip [file name] ------------------- To Uncompressed A File
$ chmod [777] [file name] ------------- To Change File Permissions
$ chown [new owner name] [file name] --- To Change Owner
$ chgrp [new group name] [file name] ----- Change Group To A File
$ useradd -u [uid] -g [group name] -d [user home dir] -s [shell]- Creating New User
$ groupadd -g [group id] [group name] ------ To Create New Group
$ userdel [user name] ------ To Delete User
$ shutdown [time] -------- To Shutdown System At Particular Time
$ shutdown -r now ------------- Shutdown and reboot immediately
$ shutdown -h halt -------------- Shutdown immediately and halt
$ df/df-k/df -g/df -h ---------- To Check Free Disk Space
$ du / du -s [dir name] ------- To Check Used Space
$ vi [file name] -------------- To Open a File with VI Editor
$ head -n [no of lines] [file name] ---- To Display First N line in A File
$ tail -n [no of line] [file name] -------- To Display Last N lines In A File

Cluster Commands

2012-09-28T00:52:00.001-07:00

How To Display Cluster Queue Managers	DISPLAY CLUSQMGR(*)
How To Display Cluster Queues In Cluster Queue Manager	DISPLAY QCLUSTER(*)
How To Display Cluster Channels Status	DISPLAY CHSTATUS(*)
How To Know A Queue Manager Is Full Repository or Not	DISPLAY CLUSQMGR(QMGR-NAME) QMTYPE

How To Suspend Queue Manager From Cluster	SUSPEND QMGR CLUSTER(CLUSTER-NAME)
How To Know A Queue Manager Suspended or Active QMGR	DISPLAY CLUSQMGR(QMGR-NAME) SUSPEND
How To Resume A Queue Manager To Cluster	RESUME QMGR CLUSTER(CLUSTER-NAME)
How To Refresh Cluster	REFRESH CLUSTER(CLUSTER-NAME) REPOS(YES/NO)

How To Reset Cluster

RESET CLUSTER(CLUSTER-NAME) QMID(QMGR-QMID) ACTION(FORCEREMOVE) QUEUES(YES/NO)

Channel And Listener Commands

2012-09-27T08:45:00.002-07:00

Channel Commands

How To Define channel Object	Sender Channel: Define Channel(Channel-Name) Chltype(sdr) Conname('ip(port)') xmitq(Transmission queue name) Receiver Channel: Define Channel(channel name) Chltype(RCVR) Trptype(TCP)
How To Display Channel Object	Display Channel(Channel-Name)
How To Display Channel Status	Display ChStatus(Channel-Name)
How To Alter Channel Object	Alter Channel(Channel-Name) Chltype(SDR/RCVR..) Maxmsgl(1024(Bytes))
How To Start Channel	Start Channel(Channel-Name)
How To Stop Channel	Stop Channel(Channel-Name) status(Inactive/Stopped)
How Ping Channel	Ping Channel(Channel-Name)
How To Reset Channel	Reset Channel(Channel-Name) Seqnum(1)
How To Delete Channel Object	Delete Channel(Channel-Name) Note: Channel Must Be In Down State to Delete.

Listener Commands:

How To Define Listener Object	Define Listener(Lstr-Name) Trptype(TCP/SPX/NETBIOS/LU 62) Port(1515) Control(qmgr/manual)
How To Display Listener Object	Display LSTR(Lstr_Name)
How To Alter Listener Object	Alter LSTR(Lstr-Name) Trptype(TCP/SPX/...) Control(qmgr/manual)
How To Start Listener service	Start LSTR(Lstr-Name)
How To Display Listener Service Status	Display LSStatus(Lstr-Name)
How To Stop Listener Service	Stop LSTR(Lstr-Name)
How To Delete Listener Object	Delete LSTR(Lstr-Name)

Queue Commands

2012-09-27T08:24:00.001-07:00

Queue Commands

Define QLocal(Queue-name)..
Define QLocal(Queue-Name) Usage(Xmitq)
Define QAlias(Queue-Name) Target(Target-Queue-Name)..
Define QRemote(Queue-Nmae) RName(Target-Queue_Name) RQMName(Target-QMGR-Name) Xmitq(Xmitq-Name)
Define QModel(Queue_name) Deftype(Tempdyn/PermDyn) ..

Display QLocal(Queue-Name)
Display Qstatus(Queue-Name)
Display QLocal(Queue-Name) Usage
Display QAlias(Queue-Name)
Display QRemote(Queue-Name) All
Display QModel(Queue-Name)

Alter QLocal(Queue-name) Maxdepth(10000) Maxmsgl(1024(bytes)) ..
Alter QRemote(Queue-Name) Rname(...) RQMName(....) Xmitq(...) ...
Alter QModel(Queue-Name) Deftype(TempDyn/PermDyn) ....
Alter QAlias(Queue_Name) Target(....) ...

Delete QLocal(Queue-Name)
Delete QAlias(Queue-Nmae)
Delete QRemote(Queue-Name)
Delete QModel(Queue-Name)
Clear QLocal(Queue-Name)

What Is NameList

2012-09-27T08:07:00.001-07:00

NameList:
Use DEFINE NAMELIST to define a list of names. This is most commonly a list of cluster names or queue names.

Note:

On UNIX systems, the command is valid only on AIX, HP-UX, Linux and Solaris.

How To Define NameList

Define NL(NameList_name) Names(cluster1,cluster2) ....

Notes:

Valid only on z/OS when the queue manager is a member of a queue-sharing group.
Valid only on z/OS.

What Is Cluster

2012-09-24T11:29:00.000-07:00

Cluster:
"A cluster is a network of Queue Managers that are logically connected each other. Each cluster must have a unique name."

If you don't use clusters, your Queue Managers are independent and communicating using DQM (Distributed Queue Management).if one Queue Manager needs to send and receive messages from multiple Queue Managers it must have defined

Remote Queues
Transmission Queues
Many sender definitions

If you group Queue Managers in a cluster, the Queue Manager can make the queues that they host available to every other Queue Manager in the cluster.

Any Queue Manager can send and receive messages to and from other Queue Managers in the same cluster without defining remote queues,transmission queues and to many channels.

In every cluster one full repository is must. Two full repositories are strongly recommended by IBM.

Repository

A repository is a collection of information about the Queue Managers that are members of a cluster. Cluster has two types of repositories

Full Repository
Partial Repository

Full Repository

A repository Queue Manager hosts a complete set of info about every Queue Manager in the cluster. This set of information is called the repository or some times called as full repository.

Partial Repository

The other queue managers each hold a partial repository, containing information about the subset of queues and queue managers with which they need to communicate. The queue managers build up their partial repositories by making inquiries when they first need to access another queue or queue manager, and by requesting that thereafter they be notified of any new information concerning that queue or queue manager.

Each queue manager stores its repository information in messages on a queue called SYSTEM.CLUSTER.REPOSITORY.QUEUE. The queue managers exchangerepository information in messages on a queue called SYSTEM.CLUSTER.COMMAND.QUEUE.

Default Cluster Queues

SYSTEM.CLUSTER.REPOSITORY.QUEUE

Each queue manager in a cluster has a local queue called SYSTEM.CLUSTER.REPOSITORY.QUEUE. This queue is used to store all the full repository information. This queue is not normally empty.

SYSTEM.CLUSTER.COMMAND.QUEUE

Each queue manager in a cluster has a local queue called SYSTEM.CLUSTER.COMMAND.QUEUE. This queue is used to carry messages to the full repository. The queue manager uses this queue to send any new or changed information about itself to the full repository queue manager and to send any requests for information about other queue managers. This queue is normally empty.

SYSTEM.CLUSTER.TRANSMIT.QUEUE

Each queue manager has a definition for a local queue called SYSTEM.CLUSTER.TRANSMIT.QUEUE. This is the transmission queue for all messages to all queues and queue managers that are within clusters.

SYSTEM.DEF.CLUSSDR

Each cluster has a default CLUSSDR channel definition called SYSTEM.DEF.CLUSSDR. This is used to supply default values for any attributes that you do not specify when you create a cluster-sender channel on a queue manager in the cluster.

SYSTEM.DEF.CLUSRCVR

Each cluster has a default CLUSRCVR channel definition called SYSTEM.DEF.CLUSRCVR. This is used to supply default values for any attributes that you do not specify when you create a cluster-receiver channel on a queue manager in the cluster.

Types Of Logging

2012-09-20T09:14:00.002-07:00

Logging
The type of logging to be used by the queue manager. You cannot change the type of logging to be used once the queue manager has been created. Refer to the description of the LogType attribute in for information about creating a queue manager with the type of logging you require.

CIRCULAR
Use circular logging if all you want is restart recovery, using the log to roll back transactions that were in progress when the system stopped. Circular logging keeps all restart data in a ring of log files. Logging fills the first file in the ring, then moves on to the next, and so on, until all the files are full. It then goes back to the first file in the ring and starts again. This continues as long as the product is in use, and has the advantage that you never run out of log files.
LINEAR
Use linear logging if you want both restart recovery and media recovery (recreating lost or damaged data by replaying the contents of the log).

Linear logging keeps the log data in a continuous sequence of files. Space is not reused, so you can always retrieve any record logged in any log extent that has not been deleted

As disk space is finite, you might have to think about some form of archiving. It is an administrative task to manage your disk space for the log, reusing or extending the existing space as necessary.

The number of log files used with linear logging can be very large, depending on your message flow and the age of your queue manager. However, there are a number of files that are said to be active. Active files contain the log entries required to restart the queue manager. Collectively, active log files are known as the active log. The number of active log files is usually less than the number of primary log files as defined in the configuration files.

MORE

Types Of Logs

2012-09-18T08:12:00.002-07:00

Logs
IBM MQ has two types of logs

Transaction Logs
Error Logs

Transaction Logs
Transactions like messages inbound, outbound, objects creation, deletion, permission etc.are going to be written to the transaction logs for every QueueManager.

Default Path For Log Files On Windows

C:\Program Files\IBM\WebSphere MQ\log\QMGR(QM1)\active\

S0000000.log

S0000001.log

S0000002.log

Default Path For Log Files On Linux/Solaris/AIX/Unix

$ /var/mqm/log/QMGR(QM1)/active/

S0000000.log

S0000001.log

S0000002.log

Types Of Transaction Logs

Primary Logs

LogPrimaryFiles=3|2-254 (Windows)|2-510 (UNIX systems)
The log files allocated when the queue manager is created.

The minimum number of primary log files you can have is 2 and the maximum is 254 on Windows, or 510 on UNIX systems. The default is 3.

The total number of primary and secondary log files must not exceed 255 on Windows, or 511 on UNIX systems, and must not be less than 3.

The value is examined when the queue manager is created or started. You can change it after the queue manager has been created. However, a change in the value is not effective until the queue manager is restarted, and the effect might not be immediate.

Secondary Logs

LogSecondaryFiles=2|1-253 (Windows)|1-509 (UNIX systems)
The log files allocated when the primary files are exhausted.
The minimum number of secondary log files is 1 and the maximum is 253 on Windows, or 509 on UNIX systems. The default number is 2.

The total number of primary and secondary log files must not exceed 255 on Windows, or 511 on UNIX systems, and must not be less than 3.

The value is examined when the queue manager is started. You can change this value, but changes do not become effective until the queue manager is restarted, and even then the effect might not be immediate.

Log File Size Detail Table

OS Min File Size Default File Size Max File Size

Win 128 KB (32 Pages) 16 MB (4096 Pages) 256 MB (65535 Pages)

Linux 256 KB (64 Pages) 16 MB (4096 Pages) 2 GB (65535*8(pages))

Error Logs

The operations going on(running) on MQ series will be written to errorlogs.
MQSeries have 2 types of error logs

MQ Level Error Logs

The operations or errors which are occurring on MQSeries are considered as MQSeries level errors.

Default Path Of MQ Level Error logs on windows

C:\program files\IBM\Websphere mq\errors\

AMQERRO1.log
AMQERRO2.log
AMQERRO3.log

Default Path Of MQ Level Error Logs On Linux,AIX

$/var/mqm/errors/

AMQERRO1.log
AMQERRO2.log
AMQERRO3.log

Note: each file size is 256KB

QueueManager Level Error Logs

The operations and errors happening at QueueManager are written to the QueueManager error logs

Default Path Of QMGR Level Error logs on windows

C:\Program Files\IBM\WebSphere MQ\Qmgrs\QMGR(QM1)\errors\

Default Path Of QMGR Level Error Logs On Linux,AIX

$/var/mqm/Qmgrs/QMGR(QM1)/errors

MORE

MQI Calls

2012-09-13T00:33:00.001-07:00

MQI – The MQSeries Programming Interface

MQCONN – Connect to QMGR
MQDISC – Disconnect from QMGR
MQOPEN – Open object
MQCLOSE – Close object
MQPUT – Put message(S)
MQPUT1 – Put one message
MQGET – Get message(S)
MQBEGIN – Begin unit of work
MQCMIT – Commit
MQBACK – Back out
MQINQ – Inquire about object attributes
MQSET -set object attributes

What Are The Trigger Monitors In MQ

2012-09-13T00:07:00.002-07:00

Trigger Monitors
In MQ Trigger Monitors are

Channel Initiator
Trigger Monitor

Channel Initiator

A channel initiator acts as a trigger monitor for sender channels, because a transmission queue may be defined as a triggered queue. When a message arrives on a transmission queue that satisfies the triggering criteria for that queue, a message is sent to the initiation queue, triggering the channel initiator to start the appropriate sender channel. You can also start server channels in this way if you specified the connection name of the partner in the channel definition. This means that channels can be started automatically, based upon messages arriving on the appropriate transmission queue.

How to start channel Initiator

runmqchi -m qmgr-name -q initq-name

Trigger Monitor

Trigger Monitor runs applications in response to a trigger event. When message(s) arrives on a application queue(local queue) that satisfies the triggering criteria for that queue, a message is sent to the initiation queue, now trigger monitor starts appropriate application.

How to start Trigger Monitor

runmqtrm -m qmgr-name -q initq-name

What Is Triggering & Types Of Triggering In MQ

2012-09-12T22:44:00.002-07:00

Triggering
WebSphere MQ provides a feature that enables an application or channel to be started automatically when there are messages available to retrive from queue

Types Of Triggering

Channel Triggering
Application triggering

Channel Triggering
Channel Triggering intended for to start channel by a channel initiator in response to a trigger event. To implement channel triggering we enable trigger service on transmission queue and apply trigger conditions on transmission queue.

Application Triggering
Application Triggering intended for to run/start an application by a trigger monitor in response to a trigger event. To implement application triggering we enable trigger service on application queue (local queue) and apply trigger conditions.

How To Define Channels

2012-09-11T00:37:00.002-07:00

Define Sender Channel

DEFINE CHANNEL(CHANNEL-NAME) +
CHLTYPE(SDR) +
CONNAME('IP(PORT)') +
XMITQ(XMITQ-NAME) +
TRPTYPE(TCP)

Default Sender Cahnnel is "SYSTEM.DEF.SENDER"

Define Receiver Channel

DEFINE CHANNEL(CHANNEL-NAME) +
CHLTYPE(RCVR) +
TRPTYPE(TCP)

Default Receiver Channel is "SYSTEM.DEF.RECEIVER"

Define Server Channel

DEFINE CHANNEL(CHANNEL-NAME) +
CHLTYPE(SVR) +
CONNAME('IP(PORT)') +
XMITQ(XMITQ-NAME) +
TRPTYPE(TCP)

Default Server Channel is "SYSTEM.DEF.SERVER"

Define Requester Channel

DEFINE CHANNEL(CHANNEL-NAME) +
CHLTYPE(RQSTR) +
CONNAME('IP(PORT)') +
TRPTYPE(TCP)

Default Requester channel is "SYSTEM.DEF.REQUESTER"

Define Cluster Sender Channel

DEFINE CHANNEL(CHANNEL-NAME) +
CHLTYPE(CLUSSDR) +
CONNAME('IP(PORT-NO)') +
CLUSTER(CLUSTER-NAME)

Default Cluster Sender Channel is "SYSTEM.DEF.CLUSSDR"

Define Cluster Receiver Channel

DEFINE CHANNEL(CHANNEL-NAME) +
CHLTYPE(CLUSRCVR) +
CONNAME('IP(PORT-NO)') +
CLUSTER(CLUSTER-NAME)

Default Cluster Sender Channel is "SYSTEM.DEF.CLUSRCVR"

Define ServerConnection Channel

DEFINE CHANNEL(CHANNEL-NAME) +
CHLTYPE(SVRCONN) +
TRPTYPE(TCP)

Default ServerConnection Channel is "SYSTEM.DEF.SVRCONN"

Define ClientConnection Channel

DEFINE CHANNEL(CHANNEL-NAME) +
CHLTYPE(CLNTCONN) +
CONNAME('IP(PORT)') +
QMNAME(QMGR-NAME) +
TRPTYPE(TCP)

Default ClientConnection is "SYSTEM.DEF.CLNTCONN"

Types Of MCAs And Message Channels

2012-09-10T23:10:00.003-07:00

Broadly In MQ Six Types Of MCAs Available

1. Sender MCA (SDR)

2. Receiver MCA (RCVR)

3. Server MCA (SVR)

4. Requester MCA (RQSTR)

5. ClusterSender MCA (CLUSSDR)

6. ClusterReceiver MCA (CLUSRCVR)

Possible Combinations Of Message Channels
A message channel is communication link between two QMGRs.
A message channel is defined using one of these types defined at one end , and a compatible type at the other end. Possible combinations are:

1. SDR-RCVR

2. SDR-RQSTR

3. SVR-RCVR

4. SVR-RQSTR

5. CLUSSDR-CLUSRCVR

Sender -- Initiate Connection to receiver
Receiver--Passive. Waits for initiation sequence from sender
Server--Initiate Connection to receiver, responds for requester
Requester--Initiate connection then becomes receiver

What Is Message Channel

2012-09-10T23:07:00.002-07:00

Message Channel

A message channel is communication link between two QMGRS
This path is used by QMGRS to exchange messages
Message channel is a combination of two ends
This communication path is uni-directional