<?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 &#187; itm</title>
	<atom:link href="http://www.jdsmedia.net/tag/itm/feed" rel="self" type="application/rss+xml" />
	<link>http://www.jdsmedia.net</link>
	<description>Tivoli deployment and integration</description>
	<lastBuildDate>Fri, 25 Nov 2011 00:46:10 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>ITM Situation Rename &#8212; BEWARE</title>
		<link>http://www.jdsmedia.net/miscellaneous/itm-situation-rename-beware#utm_source=feed&#038;utm_medium=feed&#038;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 [...]]]></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&#038;utm_medium=feed&#038;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 [...]]]></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&#038;utm_medium=feed&#038;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&#038;utm_medium=feed&#038;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: [...]]]></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>ITM Logs Timestamp Conversion</title>
		<link>http://www.jdsmedia.net/itm-documentation/itm6x/itm-logs-timestamp-conversion#utm_source=feed&#038;utm_medium=feed&#038;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 [...]]]></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 v6 Gripes (Missing functionality)</title>
		<link>http://www.jdsmedia.net/itm-documentation/itm6x/itm-v6-gripes-missing-functionality#utm_source=feed&#038;utm_medium=feed&#038;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>ITM Agent(aka:TEMA) for Omnibus fails to install in $CANDLEHOME</title>
		<link>http://www.jdsmedia.net/itm-documentation/itm-agentakatema-for-omnibus-fails-to-install-in-candlehome#utm_source=feed&#038;utm_medium=feed&#038;utm_campaign=feed</link>
		<comments>http://www.jdsmedia.net/itm-documentation/itm-agentakatema-for-omnibus-fails-to-install-in-candlehome#comments</comments>
		<pubDate>Fri, 22 May 2009 15:50:17 +0000</pubDate>
		<dc:creator>jimsander</dc:creator>
				<category><![CDATA[ITM]]></category>
		<category><![CDATA[Omnibus72x]]></category>
		<category><![CDATA[Agent]]></category>
		<category><![CDATA[alternate path]]></category>
		<category><![CDATA[attempt]]></category>
		<category><![CDATA[CANDLEHOME]]></category>
		<category><![CDATA[course]]></category>
		<category><![CDATA[enhancement]]></category>
		<category><![CDATA[enhancement request]]></category>
		<category><![CDATA[FITS]]></category>
		<category><![CDATA[ibm]]></category>
		<category><![CDATA[itm]]></category>
		<category><![CDATA[link]]></category>
		<category><![CDATA[ncagent]]></category>
		<category><![CDATA[netcool]]></category>
		<category><![CDATA[Omnibus]]></category>
		<category><![CDATA[Par]]></category>
		<category><![CDATA[path]]></category>
		<category><![CDATA[PMR]]></category>
		<category><![CDATA[Problem]]></category>
		<category><![CDATA[problem description]]></category>
		<category><![CDATA[Request]]></category>
		<category><![CDATA[solution]]></category>
		<category><![CDATA[support]]></category>
		<category><![CDATA[symbolic link]]></category>
		<category><![CDATA[target]]></category>
		<category><![CDATA[Tivoli]]></category>
		<category><![CDATA[uid]]></category>
		<category><![CDATA[workaround]]></category>

		<guid isPermaLink="false">http://www.jdsmedia.net/?p=229</guid>
		<description><![CDATA[Par for the course with IBM Tivoli&#8217;s porting of aqcuired products and their attempt at integrating them together, the ITM Agent for the a Netcool&#8217;s Omnibus  does not install in the expected $CANDLEHOME. IBM has opened an enhancement request based on the PMR I opened. My workaround below. Problem title TEMA for Omnibus does support [...]]]></description>
		<wfw:commentRss>http://www.jdsmedia.net/itm-documentation/itm-agentakatema-for-omnibus-fails-to-install-in-candlehome/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ITM62 T/EC Rulebase Changes</title>
		<link>http://www.jdsmedia.net/miscellaneous/itm62-tec-rulebase-changes#utm_source=feed&#038;utm_medium=feed&#038;utm_campaign=feed</link>
		<comments>http://www.jdsmedia.net/miscellaneous/itm62-tec-rulebase-changes#comments</comments>
		<pubDate>Thu, 02 Oct 2008 19:02:09 +0000</pubDate>
		<dc:creator>jimsander</dc:creator>
				<category><![CDATA[Non-Tivoli]]></category>
		<category><![CDATA[baroc]]></category>
		<category><![CDATA[base]]></category>
		<category><![CDATA[class]]></category>
		<category><![CDATA[class changes]]></category>
		<category><![CDATA[databases]]></category>
		<category><![CDATA[ec]]></category>
		<category><![CDATA[file]]></category>
		<category><![CDATA[file pattern]]></category>
		<category><![CDATA[fp1]]></category>
		<category><![CDATA[itm]]></category>
		<category><![CDATA[JDS]]></category>
		<category><![CDATA[kux]]></category>
		<category><![CDATA[New]]></category>
		<category><![CDATA[None]]></category>
		<category><![CDATA[number]]></category>
		<category><![CDATA[Omegamon]]></category>
		<category><![CDATA[omnux]]></category>
		<category><![CDATA[Replace]]></category>
		<category><![CDATA[Replaced]]></category>
		<category><![CDATA[segment]]></category>
		<category><![CDATA[Sentry]]></category>
		<category><![CDATA[session details]]></category>
		<category><![CDATA[slot]]></category>
		<category><![CDATA[slots]]></category>
		<category><![CDATA[STRING]]></category>
		<category><![CDATA[table]]></category>
		<category><![CDATA[table space]]></category>
		<category><![CDATA[time]]></category>
		<category><![CDATA[time engine]]></category>
		<category><![CDATA[universal messages]]></category>
		<category><![CDATA[value]]></category>

		<guid isPermaLink="false">http://www.jdsmedia.net/miscellaneous/itm62-tec-rulebase-changes/</guid>
		<description><![CDATA[ITM 6.2 FP1 contains several new and changed T/EC class changes, ranging from new classes, new slots, and only ONE new slot (omnux_value replacing kux_value). **I have not seen an ITM event containing kux_value nor omnux_value, but to be safe, I added the old &#8216;kux_value&#8217; slot to the kux.baroc file. TOTAL: 22 baroc files Baroc [...]]]></description>
		<wfw:commentRss>http://www.jdsmedia.net/miscellaneous/itm62-tec-rulebase-changes/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ITM6.2 : TEPS reconfigure overwrites kfwenv variable</title>
		<link>http://www.jdsmedia.net/miscellaneous/itm62-teps-reconfigure-overwrites-kfwenv-variable#utm_source=feed&#038;utm_medium=feed&#038;utm_campaign=feed</link>
		<comments>http://www.jdsmedia.net/miscellaneous/itm62-teps-reconfigure-overwrites-kfwenv-variable#comments</comments>
		<pubDate>Thu, 04 Sep 2008 02:11:00 +0000</pubDate>
		<dc:creator>jimsander</dc:creator>
				<category><![CDATA[Non-Tivoli]]></category>
		<category><![CDATA[cnb]]></category>
		<category><![CDATA[CNPSJ]]></category>
		<category><![CDATA[default values]]></category>
		<category><![CDATA[Documentation]]></category>
		<category><![CDATA[EWAS]]></category>
		<category><![CDATA[ibm]]></category>
		<category><![CDATA[itm]]></category>
		<category><![CDATA[ITMProfile]]></category>
		<category><![CDATA[kfw]]></category>
		<category><![CDATA[kfwenv]]></category>
		<category><![CDATA[N
	KFW]]></category>
		<category><![CDATA[numerical values]]></category>
		<category><![CDATA[PID]]></category>
		<category><![CDATA[TEPS]]></category>

		<guid isPermaLink="false">http://www.jdsmedia.net/?p=200</guid>
		<description><![CDATA[Not all of them mind you, but some important ones none-the-less: KFW_STARTJVM=N KFW_USE_EMBEDDED=Y KFW_EWAS_SERVER_PID_FILE=C:\IBM\ITM\CNPSJ\profiles\ITMProfile\logs\ITMServer\ITMServer.pid KFW_EWAS_STARTSERVER_SCRIPT=C:\IBM\ITM\CNPSJ\profiles\ITMProfile\bin\startServer.bat KFW_EWAS_STOPSERVER_SCRIPT=C:\IBM\ITM\CNPSJ\profiles\ITMProfile\bin\stopServer.bat I verified the following by modifying all the variables in my %CANDLEHOME%\CNB\kfwenv file where numerical values like ports and max where incremented by one, and the string vlaues had _XXX_ inserted The modified kfwenv was backed up, then I [...]]]></description>
		<wfw:commentRss>http://www.jdsmedia.net/miscellaneous/itm62-teps-reconfigure-overwrites-kfwenv-variable/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ITM6 &#8211; MTEMS Hangs</title>
		<link>http://www.jdsmedia.net/miscellaneous/itm6-mtems-hangs#utm_source=feed&#038;utm_medium=feed&#038;utm_campaign=feed</link>
		<comments>http://www.jdsmedia.net/miscellaneous/itm6-mtems-hangs#comments</comments>
		<pubDate>Thu, 04 Sep 2008 01:03:27 +0000</pubDate>
		<dc:creator>jimsander</dc:creator>
				<category><![CDATA[Non-Tivoli]]></category>
		<category><![CDATA[annoyance]]></category>
		<category><![CDATA[box]]></category>
		<category><![CDATA[caption]]></category>
		<category><![CDATA[configuration window]]></category>
		<category><![CDATA[connector]]></category>
		<category><![CDATA[Enterprise]]></category>
		<category><![CDATA[enterprise portal]]></category>
		<category><![CDATA[hang]]></category>
		<category><![CDATA[ibm]]></category>
		<category><![CDATA[itm]]></category>
		<category><![CDATA[MTEMS]]></category>
		<category><![CDATA[portal server]]></category>
		<category><![CDATA[TEPS]]></category>
		<category><![CDATA[Tivoli]]></category>
		<category><![CDATA[tivoli enterprise]]></category>
		<category><![CDATA[window]]></category>

		<guid isPermaLink="false">http://www.jdsmedia.net/?p=193</guid>
		<description><![CDATA[This is a brain-dead situation, but I&#8217;ve been bit by the &#8220;ITM Connector&#8221; dialog box hiding behind the MTEMS configuration window. Anytime you reconfigure the TEPS (Tivoli Enterprise Portal Server) via MTEMS (Manage Tivoli Enterprise Monitoring), sometimes that little box just hangs back there until you move the MTEMS window. Very innocuous problem that isn&#8217;t [...]]]></description>
		<wfw:commentRss>http://www.jdsmedia.net/miscellaneous/itm6-mtems-hangs/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

