<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>JDS Media</title>
	<atom:link href="http://www.jdsmedia.net/feed" rel="self" type="application/rss+xml" />
	<link>http://www.jdsmedia.net</link>
	<description>Tivoli deployment and integration</description>
	<lastBuildDate>Mon, 08 Mar 2010 17:08:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>ITM Situation Rename &#8212; BEWARE</title>
		<link>http://www.jdsmedia.net/miscellaneous/itm-situation-rename-beware#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://www.jdsmedia.net/miscellaneous/itm-situation-rename-beware#comments</comments>
		<pubDate>Sun, 28 Feb 2010 21:04:49 +0000</pubDate>
		<dc:creator>jimsander</dc:creator>
				<category><![CDATA[ITM6.2.1]]></category>
		<category><![CDATA[Non-Tivoli]]></category>
		<category><![CDATA[aof]]></category>
		<category><![CDATA[attribute]]></category>
		<category><![CDATA[column]]></category>
		<category><![CDATA[crap]]></category>
		<category><![CDATA[eif]]></category>
		<category><![CDATA[field]]></category>
		<category><![CDATA[Fullname]]></category>
		<category><![CDATA[itm]]></category>
		<category><![CDATA[length]]></category>
		<category><![CDATA[name]]></category>
		<category><![CDATA[new situation]]></category>
		<category><![CDATA[response problem]]></category>
		<category><![CDATA[situation]]></category>
		<category><![CDATA[situation name]]></category>

		<guid isPermaLink="false">http://www.jdsmedia.net/?p=458</guid>
		<description><![CDATA[ As of ITM 6.2.1, there is a perceived capability to now rename situations within the editor.
However, the rename is actually a new attribute called &#8216;Full Name&#8217; and only changes the TEPS display name for the situation; the EIF will still send the original situation name.
IBM responds this is &#8220;working as designed&#8221; &#8212; a load [...]]]></description>
		<wfw:commentRss>http://www.jdsmedia.net/miscellaneous/itm-situation-rename-beware/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ITM6 : Take Action : Remount Stale remote filesystems</title>
		<link>http://www.jdsmedia.net/itm-documentation/itm6x/itm6-take-action-remount-stale-remote-filesystems#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://www.jdsmedia.net/itm-documentation/itm6x/itm6-take-action-remount-stale-remote-filesystems#comments</comments>
		<pubDate>Thu, 09 Jul 2009 03:54:54 +0000</pubDate>
		<dc:creator>jimsander</dc:creator>
				<category><![CDATA[ITM6.x]]></category>
		<category><![CDATA[Action]]></category>
		<category><![CDATA[action script]]></category>
		<category><![CDATA[amp]]></category>
		<category><![CDATA[filesystems]]></category>
		<category><![CDATA[itm]]></category>
		<category><![CDATA[junkmail]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[linux disk]]></category>
		<category><![CDATA[mail]]></category>
		<category><![CDATA[remount]]></category>
		<category><![CDATA[semicolons]]></category>
		<category><![CDATA[situation]]></category>
		<category><![CDATA[umount]]></category>

		<guid isPermaLink="false">http://www.jdsmedia.net/miscellaneous/itm6-take-action-remount-stale-remote-filesystems-2</guid>
		<description><![CDATA[
 
Situation

An ITM6 Unix (UX) or Linux (LZ) agent detects that its remote filesystems are unavailable, a &#8220;stale&#8221; connection.

Automate an action to remount it if possible

Methodology

Two (2) ITM situations are created where


detects the mount point has become stale

the other is triggered by the &#8220;correlated situation&#8221; condition of #1 being tr


Situation #1 : Detect &#8220;Stale&#8221; remote FS

Simple [...]]]></description>
		<wfw:commentRss>http://www.jdsmedia.net/itm-documentation/itm6x/itm6-take-action-remount-stale-remote-filesystems/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ITM Logs Timestamp Conversion</title>
		<link>http://www.jdsmedia.net/itm-documentation/itm6x/itm-logs-timestamp-conversion-2#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://www.jdsmedia.net/itm-documentation/itm6x/itm-logs-timestamp-conversion-2#comments</comments>
		<pubDate>Thu, 09 Jul 2009 03:45:00 +0000</pubDate>
		<dc:creator>jimsander</dc:creator>
				<category><![CDATA[ITM6.x]]></category>
		<category><![CDATA[foreach]]></category>
		<category><![CDATA[hexadecimal]]></category>
		<category><![CDATA[itm]]></category>
		<category><![CDATA[localtime]]></category>
		<category><![CDATA[perl]]></category>
		<category><![CDATA[printf]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[stdin]]></category>
		<category><![CDATA[time]]></category>
		<category><![CDATA[time print]]></category>
		<category><![CDATA[unnecessary effort]]></category>

		<guid isPermaLink="false">http://www.jdsmedia.net/miscellaneous/itm-logs-timestamp-conversion-2</guid>
		<description><![CDATA[ITM v6 log files use a hexadecimal timestamp (to save space? who the hell knows), which adds unnecessary effort when the reason you&#8217;re looking at the logs is to determine an issue in the first place. In any case&#8230; Here&#8217;s the script I wrote when I first encountered the nonsense in ITM v6 logs a [...]]]></description>
		<wfw:commentRss>http://www.jdsmedia.net/itm-documentation/itm6x/itm-logs-timestamp-conversion-2/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ITM : Testing Windows Event Logs</title>
		<link>http://www.jdsmedia.net/itm-documentation/itm6x/itm-testing-windows-event-logs#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://www.jdsmedia.net/itm-documentation/itm6x/itm-testing-windows-event-logs#comments</comments>
		<pubDate>Wed, 08 Jul 2009 03:40:48 +0000</pubDate>
		<dc:creator>jimsander</dc:creator>
				<category><![CDATA[ITM6.x]]></category>
		<category><![CDATA[WindozeMiscellaneous]]></category>
		<category><![CDATA[Damned]]></category>
		<category><![CDATA[eventcreate]]></category>
		<category><![CDATA[example]]></category>
		<category><![CDATA[issue]]></category>
		<category><![CDATA[itm]]></category>
		<category><![CDATA[L Application]]></category>
		<category><![CDATA[notification script]]></category>
		<category><![CDATA[Problem]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[slashes]]></category>
		<category><![CDATA[T ERROR]]></category>
		<category><![CDATA[test message]]></category>
		<category><![CDATA[unix]]></category>
		<category><![CDATA[unix script]]></category>
		<category><![CDATA[windows command]]></category>

		<guid isPermaLink="false">http://www.jdsmedia.net/itm-documentation/itm6-1/itm-testing-windows-event-logs</guid>
		<description><![CDATA[In a nutshell: use the &#8216;eventcreate&#8216; 
I had an issue with ITM Windows Agent creating events which I was then sending out email alerts via a UNIX script.
The simple problem was backslashes in windows paths where the &#8220;Take Action&#8221; notification script was literalizing characters which might be part of the EventLog Description
For example:
"c:\Damned these\nagging\slashes\argh"
became
c:\Damned these
agging\slashesrgh
Yes, [...]]]></description>
		<wfw:commentRss>http://www.jdsmedia.net/itm-documentation/itm6x/itm-testing-windows-event-logs/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ITMv6 Process string length limitation</title>
		<link>http://www.jdsmedia.net/itm-documentation/itm6x/itmv6-process-string-length-limitation#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://www.jdsmedia.net/itm-documentation/itm6x/itmv6-process-string-length-limitation#comments</comments>
		<pubDate>Wed, 01 Jul 2009 15:20:47 +0000</pubDate>
		<dc:creator>jimsander</dc:creator>
				<category><![CDATA[ITM6.x]]></category>
		<category><![CDATA[ibm]]></category>
		<category><![CDATA[java ibm]]></category>
		<category><![CDATA[line script]]></category>
		<category><![CDATA[name]]></category>
		<category><![CDATA[pattern]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[regex pattern]]></category>
		<category><![CDATA[Rep. Please]]></category>
		<category><![CDATA[Request]]></category>
		<category><![CDATA[request number]]></category>
		<category><![CDATA[server1]]></category>
		<category><![CDATA[STRING]]></category>
		<category><![CDATA[unix os]]></category>

		<guid isPermaLink="false">http://www.jdsmedia.net/miscellaneous/itmv6-process-string-length-limitation</guid>
		<description><![CDATA[My PMR to IBM Tivoli support
I&#8217;d be surprised if there wasn&#8217;t already an ER for this, but if you
don&#8217;t mind, please submit one.
Do you know if anybody else has asked or criticized this major
limitation.
Its hard to believe that there isn&#8217;t something that emulate what a
simple one line script would accomplish.
In the ER, I would expect [...]]]></description>
		<wfw:commentRss>http://www.jdsmedia.net/itm-documentation/itm6x/itmv6-process-string-length-limitation/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IBM Tivoli Monitoring Product Codes</title>
		<link>http://www.jdsmedia.net/itm-documentation/itm6x/ibm-tivoli-monitoring-product-codes#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://www.jdsmedia.net/itm-documentation/itm6x/ibm-tivoli-monitoring-product-codes#comments</comments>
		<pubDate>Mon, 29 Jun 2009 20:41:11 +0000</pubDate>
		<dc:creator>jimsander</dc:creator>
				<category><![CDATA[ITM6.x]]></category>
		<category><![CDATA[Codes]]></category>
		<category><![CDATA[ibm]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[linux system]]></category>
		<category><![CDATA[Obtaining]]></category>
		<category><![CDATA[proddsc]]></category>
		<category><![CDATA[Product]]></category>
		<category><![CDATA[tbl]]></category>
		<category><![CDATA[Tivoli]]></category>
		<category><![CDATA[uniq]]></category>
		<category><![CDATA[unix]]></category>
		<category><![CDATA[unix awk]]></category>
		<category><![CDATA[unix linux]]></category>
		<category><![CDATA[utf 8]]></category>
		<category><![CDATA[wss]]></category>

		<guid isPermaLink="false">http://www.jdsmedia.net/?p=359</guid>
		<description><![CDATA[Obtaining Product Codes for IBM Tivoli Monitoring (ITM v6)
Local method:
Parse the proddsc.tbl file on a UNIX/Linux system to get the list by doing this:
UNIX 
awk -F\&#124; '/^[^*#]/ {print $1,$2}' ${CANDLEHOME}/registry/proddsc.tbl &#124; sort &#124; uniq

Or, IBM&#8217;s site http://www-01.ibm.com/support/docview.wss?rs=2366&#38;context=SSZ8F3&#38;dc=DB520&#38;dc=DB560&#38;uid=swg21265222&#38;loc=en_US&#38;cs=UTF-8&#38;lang=en&#38;rss=ct2366tivoli
]]></description>
		<wfw:commentRss>http://www.jdsmedia.net/itm-documentation/itm6x/ibm-tivoli-monitoring-product-codes/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ITM Logs Timestamp Conversion</title>
		<link>http://www.jdsmedia.net/itm-documentation/itm6x/itm-logs-timestamp-conversion#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://www.jdsmedia.net/itm-documentation/itm6x/itm-logs-timestamp-conversion#comments</comments>
		<pubDate>Mon, 29 Jun 2009 16:36:47 +0000</pubDate>
		<dc:creator>jimsander</dc:creator>
				<category><![CDATA[ITM6.x]]></category>
		<category><![CDATA[foreach]]></category>
		<category><![CDATA[gulfbreeze]]></category>
		<category><![CDATA[hexadecimal]]></category>
		<category><![CDATA[itm]]></category>
		<category><![CDATA[localtime]]></category>
		<category><![CDATA[logs]]></category>
		<category><![CDATA[perl]]></category>
		<category><![CDATA[printf]]></category>
		<category><![CDATA[script]]></category>
		<category><![CDATA[stdin]]></category>
		<category><![CDATA[time]]></category>
		<category><![CDATA[time print]]></category>
		<category><![CDATA[timestamp]]></category>
		<category><![CDATA[unnecessary effort]]></category>

		<guid isPermaLink="false">http://www.jdsmedia.net/?p=353</guid>
		<description><![CDATA[ITM v6 log files use a hexadecimal timestamp (to save space? who the hell knows), which adds unnecessary effort when the reason you&#8217;re looking at the logs is to determine an issue in the first place. In any case&#8230;
Here&#8217;s the script I wrote when I first encountered the nonsense in ITM v6 logs a few [...]]]></description>
		<wfw:commentRss>http://www.jdsmedia.net/itm-documentation/itm6x/itm-logs-timestamp-conversion/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ITM Host Availability (ping attribute)</title>
		<link>http://www.jdsmedia.net/itm-documentation/itm6x/itm-host-availability-ping-attribute#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://www.jdsmedia.net/itm-documentation/itm6x/itm-host-availability-ping-attribute#comments</comments>
		<pubDate>Sun, 28 Jun 2009 17:54:07 +0000</pubDate>
		<dc:creator>jimsander</dc:creator>
				<category><![CDATA[ITM6.x]]></category>
		<category><![CDATA[CANDLEHOME]]></category>
		<category><![CDATA[config]]></category>
		<category><![CDATA[critical servers]]></category>
		<category><![CDATA[input file]]></category>
		<category><![CDATA[kux]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[list]]></category>
		<category><![CDATA[Ping]]></category>
		<category><![CDATA[ping source]]></category>
		<category><![CDATA[target host]]></category>
		<category><![CDATA[unix]]></category>
		<category><![CDATA[unix ping]]></category>

		<guid isPermaLink="false">http://www.jdsmedia.net/?p=345</guid>
		<description><![CDATA[Synopsis
A nice feature which isn&#8217;t publicized too much in ITM for Linux and Unix agents is the ping capability.
They&#8217;re refrerred to as &#8220;Host Availability&#8221; for Linux and &#8220;Ping Attributes&#8221; for Unix
Both will accept an input file containing a list of servers to &#8220;ping&#8221;, and both will return status and response time.
Enabling the ping hosts file
Linux
$CANDLEHOME/config/lz.ini: [...]]]></description>
		<wfw:commentRss>http://www.jdsmedia.net/itm-documentation/itm6x/itm-host-availability-ping-attribute/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ITM v6 Gripes (Missing functionality)</title>
		<link>http://www.jdsmedia.net/itm-documentation/itm6x/itm-v6-gripes-missing-functionality#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://www.jdsmedia.net/itm-documentation/itm6x/itm-v6-gripes-missing-functionality#comments</comments>
		<pubDate>Sat, 27 Jun 2009 01:58:53 +0000</pubDate>
		<dc:creator>jimsander</dc:creator>
				<category><![CDATA[ITM6.x]]></category>
		<category><![CDATA[Agent]]></category>
		<category><![CDATA[best practices]]></category>
		<category><![CDATA[box]]></category>
		<category><![CDATA[directory]]></category>
		<category><![CDATA[fairness]]></category>
		<category><![CDATA[file]]></category>
		<category><![CDATA[Inability]]></category>
		<category><![CDATA[itm]]></category>
		<category><![CDATA[linux oracle]]></category>
		<category><![CDATA[listeners]]></category>
		<category><![CDATA[oracle agent]]></category>
		<category><![CDATA[regular expressions]]></category>
		<category><![CDATA[shortcomings]]></category>
		<category><![CDATA[system windows]]></category>
		<category><![CDATA[Tivoli]]></category>
		<category><![CDATA[unix and linux]]></category>

		<guid isPermaLink="false">http://www.jdsmedia.net/?p=339</guid>
		<description><![CDATA[As a Tivoli consultant, I&#8217;ve had to tweak, torque and tune ITM v6 to fulfill requirements not met out of the box. Several of my clients have felt ripped off by IBM for having paid for a product billed as covering best practices out of the box, only to discover, there is significant development costs [...]]]></description>
		<wfw:commentRss>http://www.jdsmedia.net/itm-documentation/itm6x/itm-v6-gripes-missing-functionality/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Quick and Dirty LAMP</title>
		<link>http://www.jdsmedia.net/miscellaneous/webservices/329#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
		<comments>http://www.jdsmedia.net/miscellaneous/webservices/329#comments</comments>
		<pubDate>Sat, 27 Jun 2009 00:58:28 +0000</pubDate>
		<dc:creator>jimsander</dc:creator>
				<category><![CDATA[webservices]]></category>
		<category><![CDATA[apache php]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[database test]]></category>
		<category><![CDATA[fc4]]></category>
		<category><![CDATA[Fedora Core]]></category>
		<category><![CDATA[GRANT ALL]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[php phpinfo]]></category>
		<category><![CDATA[root]]></category>
		<category><![CDATA[root account]]></category>
		<category><![CDATA[sbin]]></category>
		<category><![CDATA[user]]></category>

		<guid isPermaLink="false">http://www.jdsmedia.net/?p=329</guid>
		<description><![CDATA[Installing a LAMP stack: Linux &#8211; Apache, PHP, and MySQL on Fedora Core
Assuming you already have Linux and Yum installed.
1. Install Apache (httpd), PHP, MySQL (server and client), and the component that allows
php to talk to mysql.
 yum -y install httpd php mysql mysql-server php-mysql
2. Configure the new services to start automatically
  /sbin/chkconfig httpd [...]]]></description>
		<wfw:commentRss>http://www.jdsmedia.net/miscellaneous/webservices/329/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
