Sent to you by Frank Tate via Google Reader:
Things you can do from here:
- Subscribe to IBM developerWorks : Java technology using Google Reader
- Get started using Google Reader to easily keep up with all your favorite sites
I think this where i will focus any free time. This should allow for mobile browsers to render the interface and be a lot quicker.
This is not technical, just a word of advice. I watched 8 episodes of the Sopranos on DVD back to back. I started swearing at truly inapprpriate moments. Probably good to throw a Brady Bunch episode in the mix.
#!/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
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.
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.
GBSCMD is a free Gulf Breeze offering for performing ITM operations from command line. It is complimentary to tacmd tool and performs many operations that are not provided by tacmd. GBSCMD uses ITM Webservices feature extensively and some of the benefits of GBSCMD are listed below.
If you would like to learn about GBSCMD tool, here are some links to the past articles about GBSCMD. You can google search "gbscmd site:blog.gulfsoft.com".
http://blog.gulfsoft.com/2008/03/gbscmd-v35-new-features.html
http://blog.gulfsoft.com/2008/03/simple-postemsg-like-solution-for-itm_15.html
We have been tweaking the tool from time to time to introduce new features and address bug fixes and this blog discuss some of the changes introduced during the recent versions. The latest and greatest version of the tool as of this writing is version 3.6.4. If you would like to get the latest version, please feel free to contact me at venkat at gulfsoft.com or Tony Delgross at gulfsoft.com. If you have some suggestion on features that you would like to see in GBSCMD, please feel free to write to me as well.
Here are the changes introduced to GBSCMD since version 3.6.1
Version 3.6.1
This version introduced support for row filtering of SOAP Call results with --afilter option. The following example uses --afilter option to get the disk data from an agent and filters the results to include only C: drive information.
./gbscmd ct_get --auth itm62.auth --Object NT_Logical_Disk --target Primary:ITM62:NT --afilter Disk_Name;EQ;C:
You can also get the last 24 hour history data from the agent using --history switch to CT_Get. Some of the other changes include ability to see the results in XML format using --xml option (Thanks IV for making that change!).
Version 3.6.2
This version introduced new SOAP calls for starting and stopping situations at RTEMS level using --starttemssit and --stoptemssit options. If you are running backlevel of ITM and would like the ability to start and stop situations, you can use this feature. It also addressed some timeout issues while getting large SOAP data. (e.g. listing of all managed systems in the entire enterprise for a large ITM Setup).
Version 3.6.3
This version uses new SOAP call for listing situations running on individual agents.
Version 3.6.4
This version introduces column filtering of SOAP results with --attribute option. For example, if you want to get the disk data and only interested in Disk Name and Free Megabytes attributes, the following command line will get you the information.
./gbscmd ct_get --auth itm62.auth --Object NT_Logical_Disk --target Primary:ITM62:NT --attribute Disk_Name --attribute Free_Megabytes
This version also adds --version switch to identify the current GBSCMD version.
The complete documentation is available for download from the following link.