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.
Friday, January 22, 2010
Interesting Visualization
Thursday, January 21, 2010
GbsNcoSql User Guide
Wednesday, January 20, 2010
Now you have an alternative to FreeTDS - GbsNcoSql
- Currently, it can run any Omnibus "SELECT" queries only. Though the utility could potentially be modified to run other queries, the idea is to use the nco_sql utility for all other type of queries.
- Consistent one-record per line output
- Ability to specify your own delimiter with "-d" switch.
- Ability to suppress header output with "-n" switch.
- Ability to specify queries in a file or read from command line.
- No need to compile any FreeTDS drivers. It comes with the necessary FreeTDS drivers.
- Authorization information kept in a separate file and can be specified with -a switch. You don't need to specify the password in your scripts.
- Platform independent and works with the IBM and Sun JREs.
-a
-d
-f
-h Displays the help information
-n No header output
-q
Node,Tally
sys1,1
sys21,1
sys3,1
192.168.1.50,190
$ cat my.auth
user=root
password=mypass