Wednesday, May 26, 2010
Configuring the TBSM 4.2.1 Discovery Library Toolkit to work with TADDM 7.1.1 and later
Scheduled Wakeup in Ubuntu
Here are the exact steps needed on my Lucid Lynx. Please note that you need to have Kernel 2.6.22 or later for this to work.
1) Install the Power management interface tools.
sudo apt-get install powermanagement-interface
2) Copy the following code somewhere in your filesystem and save it as "suspend_x_hours.sh".
#!/bin/bash3) Schedule the script in root's crontab. e.g the following crontab entry runs at 8PM and puts the system in sleep for 10 hours, waking it up at 6:00 AM.
# This script puts the system under standby mode for x hoursusage() {echo "usage: $0 <n-hours>"echo "where <n-hours> is the number of hours to be on standby"exit 0
}
if [ $# -ne 1 ]thenusagefi
PATH=$PATH:/usr/sbin
hours=$1
echo 0 > /sys/class/rtc/rtc0/wakealarm
echo `date '+%s' -d "+ $hours hours"` > /sys/class/rtc/rtc0/wakealarm
pmi action suspend
00 20 * * * /home/venkat/bin/suspend_x_hours.sh 10 2>/dev/null
Sunday, May 16, 2010
ITM Tip: Disabling default situations during install time
Many ITM sites want to disable default ITM situations so that unnecessary alerts are not sent to the operations. In old days, we usually disable the situations by running a simple script. One such example of the script is posted below.
http://blog.gulfsoft.com/2008/03/disable-all-default-situations.html
This task is much easier with ITM 6.2.2. While seeding application support, ITM asks you to whether you want to add the default managed system groups to the situation distribution. If you answer no, the default situations will not be distributed to any managed system unless you explicitly assign them! However, this feature is applicable only for fresh installation of ITM 6.2.2 and may not apply to those who are upgrading from old version of ITM.
Tuesday, March 9, 2010
GbsNcoSql V2.0
Tuesday, March 2, 2010
IBM - Recording RPT 8 HTTP scripts
IBM - Recording RPT 8 HTTP scripts
Tuesday, February 9, 2010
Some possible responses to TADDM Error CTJTD3602E
IBM's documentation contains the following description of this error:
CTJTD3602E: The Change Manager is still processing. Wait and retry the discovery at a later time.
Explanation: The Change Manager is still running to process recent changes discovered. The discovery cannot be started until the Change Manager completes.
Operator Response: None.
Administrator Response: Allow time for the Change Manager to complete its processing before starting a discovery.
Programmer Response: None.
What we have found is that this condition can possibly occur for at least a couple of different reasons. The two situations we've found have been:
1. There was a deadlock on the database that we had to clear. A "little while" after we cleared the lock, we were able to successfully run a discovery again without receiving the error message.
2. The change manager partially ran, but didn't update the CHANGE_SERVER_STATUS table. Specifically, it left the value of the STATUS column set to 16 for the last discovery. To fix this, we had to run the following SQL:
update DB2TADDM.CHANGE_SERVER_STATUS set status = 17
This updates the STATUS column for all rows in the table. You could limit it with a WHERE clause, but in our case, it was valid as is.
We then needed to stop and restart TADDM, and the error message went away.
Monday, February 1, 2010
Identifying newly added systems in Tivoli Monitoring using GBSCMD
Come see Gulf Breeze at Pulse so we can show why we are the best.