Access Twitter from AIX command line

Very interesting article on IBM DeveloperWorks on how to access twitter from AIX command line using Ruby.

Accessing Twitter from the command line

WMQ channels monitoring

I have come across a situation wherein I have to monitor any dead channels; Using support pack MO71 & filters, you can develop a simple monitor quickly; Using MO71 support pack auto refresh, filters will scan WMQ channels automatically at specific intervals and write info to a file.

Below is a sample script to report channels which are open but not received a message more than few hours.

This Script opens a file in C:\IBM\WMQ\tools\mo71\temp\Channel_Status.log and appends the information with details.


@ChlStartTime := mqtime(CHSTADA,CHSTATI);
@LstMsgTime := mqtime(LSTMSGDA,LSTMSGTI);
@diffTime := @LstMsgTime - @ChlStartTime;
if (@diffTime > 3600) {
@fd := fopen("C:\\IBM\\WMQ\\tools\\mo71\\temp\\Channel_Status.log","a");
fprintf(@fd, "%-17s\t", date$(_time));
fprintf(@fd, "%-20s\t", _qmname);
fprintf(@fd, "%-20s %5s %5s \t",CHANNAME,STATUS,MCASTAT);
fprintf(@fd, "%-15s %-11s %-10s ",CONNAME,CHSTADA,CHSTATI);
fprintf(@fd, "%-11s %-10s ",LSTMSGDA,LSTMSGTI);
fprintf(@fd, "%-5s %-5s %20s ",CHLTYPE,SUBSTATE,JOBNAME);
fprintf(@fd, "\tChannel Start Time = %s\tLast Message Received Time = %s Difference in time = %s\t\t %s Days opened \n", @ChlStartTime,@LstMsgTime ,@diffTime, (@diffTime/86400) );
fclose(@fd);
} else {
csl(1,info,"All channel connections are good");
}


You can get more details on this WebSphere MQ MO71 support pack from IBM.

WebSphere Integration Developer 7.0 upgrade

After installing the WebSphere Integration Developer 7.0, when you attempt to update WID using IBM Installation Manager you will see a warning message that there is an unsupported fix pack installed; you must remove the fix pack before you can update/upgrade.







To remove the fix pack you will have to use IBM Update Installer; a different product to update WID.

Please visit IBM tech note on this

WebSphere MQ for Windows GUI administrator

Recently I have to browse a queue with more than 8000 messages in it and reload messages from a back-out queue to application queue. With "WebSphere MQ Explorer you can browse at most 5000 messages. If you ever need to examine a message contents which are in position greater than 5000; you have left with no choice with the standard tools shipped with WebSphere MQ.

M071 will save your day with build in queue load/unload utility a.k.a MO03


Please visit the inline links and download support packs from IBM.

WebSphere MQ on Windows, MaxChannels setting in registry

WebSphere MQ on Windows uses registry for queue manager configuration. I was looking for MaxChannels in my queue manager registry and didn't find a corresponding entry. I have modified the MaxChannels to 10 using WebSphere MQ Explorer, and registry entry appeared automatically.

C:>reg query HKLM\SOFTWARE\IBM\MQSeries\CurrentVersion\Configuration\QueueManager\testQM /s

! REG.EXE VERSION 3.0

HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\Configuration\QueueManager\testQM
Name REG_SZ testQM
Prefix REG_SZ C:\IBM\WMQ
Directory REG_SZ testQM

HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\Configuration\QueueManager\testQM\CHANNELS
MaxChannels REG_SZ 10

I guess default values not stored in registry. This should have been better documented in IBM Infocenter.

WebSphere MQ V7 and Windows 64 bit

On Windows, MQ runs in 32 bit mode; but it supports both 64 bit and 32 bit applications. You need to make sure that you are using correct bindings to connect with WMQ; more on this subject visit WebSphere MQ infocenter.


To change WebSphere MQ registry entries look in (click on WOW6432Node to know more on registry in windows 2008/Windows 7 64 bit os versions).

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\IBM\MQSERIES\CurrentVersion\Configuration\

Example:

C:\WMQ\bin>reg query HKEY_LOCAL_MACHINE\Software\Wow6432Node\IBM\MQSeries\CurrentVersion\Configuration\QueueManager\TEST\Log
HKEY_LOCAL_MACHINE\Software\Wow6432Node\IBM\MQSeries\CurrentVersion\Configuration\QueueManager\TEST\Log
LogPrimaryFiles REG_SZ 3
LogSecondaryFiles REG_SZ 3
LogFilePages REG_SZ 4096
LogType REG_SZ CIRCULAR
LogBufferPages REG_SZ 0
LogPath REG_SZ C:\WMQ\log\TEST\
LogWriteIntegrity REG_SZ TripleWrite