 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: DYNSLT Omit</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/dynslt-omit/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/dynslt-omit/</link>
	<description></description>
	<lastBuildDate>Tue, 21 May 2013 20:11:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: TomLiotta</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/dynslt-omit/#comment-109892</link>
		<dc:creator>TomLiotta</dc:creator>
		<pubDate>Wed, 08 Aug 2012 00:23:15 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/itanswers/dynslt-omit/#comment-109892</guid>
		<description><![CDATA[&lt;EM&gt;This is for a JLF…using one instead of an MQT…&lt;/EM&gt;
&#160;
How did a MQT get involved in this? Why would you want a MQT? Why not a simple view (supported by appropriate indexes)?
Tom]]></description>
		<content:encoded><![CDATA[<p><em>This is for a JLF…using one instead of an MQT…</em><br />
&nbsp;<br />
How did a MQT get involved in this? Why would you want a MQT? Why not a simple view (supported by appropriate indexes)?<br />
Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bogeybetsy</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/dynslt-omit/#comment-109877</link>
		<dc:creator>bogeybetsy</dc:creator>
		<pubDate>Tue, 07 Aug 2012 14:47:45 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/itanswers/dynslt-omit/#comment-109877</guid>
		<description><![CDATA[Hi,Thanks for the answers. &#160;I did it byA &#160;S &#160; &#160; X.A &#160; &#160; COMP(NE &#160;Y.A)A &#160; &#160; &#160; &#160; X.B &#160; &#160; &#160;COMP(NE &#160;Y.B)A &#160; &#160; &#160; &#160; X.C &#160; &#160; &#160;COMP(NE &#160;Y.C)The dot notation is just to inform you that the field comes from a different file. &#160;This is for a JLF...using one instead of an MQT...to be used by a subfile scroll program. &#160;With the MQT, users would have to wait, 40 seconds to 2 minutes waiting for it to &quot;refresh&quot;. &#160;The JLF, although slower, performs better because each page only has to show 13 records - and retrieving 13 records from the JLF is much faster than a &quot;refresh&quot; of the MQT which will show data that is not &quot;real-time&quot;.]]></description>
		<content:encoded><![CDATA[<p>Hi,Thanks for the answers. &nbsp;I did it byA &nbsp;S &nbsp; &nbsp; X.A &nbsp; &nbsp; COMP(NE &nbsp;Y.A)A &nbsp; &nbsp; &nbsp; &nbsp; X.B &nbsp; &nbsp; &nbsp;COMP(NE &nbsp;Y.B)A &nbsp; &nbsp; &nbsp; &nbsp; X.C &nbsp; &nbsp; &nbsp;COMP(NE &nbsp;Y.C)The dot notation is just to inform you that the field comes from a different file. &nbsp;This is for a JLF&#8230;using one instead of an MQT&#8230;to be used by a subfile scroll program. &nbsp;With the MQT, users would have to wait, 40 seconds to 2 minutes waiting for it to &#8220;refresh&#8221;. &nbsp;The JLF, although slower, performs better because each page only has to show 13 records &#8211; and retrieving 13 records from the JLF is much faster than a &#8220;refresh&#8221; of the MQT which will show data that is not &#8220;real-time&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: philpl1jb</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/dynslt-omit/#comment-109791</link>
		<dc:creator>philpl1jb</dc:creator>
		<pubDate>Fri, 03 Aug 2012 10:38:32 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/itanswers/dynslt-omit/#comment-109791</guid>
		<description><![CDATA[These look very much like the join&#160;fields.&#160; If these are the join fields, they shoud&#160;be used in the join section of the logical not the select/omit section.Phil&#160;]]></description>
		<content:encoded><![CDATA[<p>These look very much like the join&nbsp;fields.&nbsp; If these are the join fields, they shoud&nbsp;be used in the join section of the logical not the select/omit section.Phil&nbsp;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TomLiotta</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/dynslt-omit/#comment-109779</link>
		<dc:creator>TomLiotta</dc:creator>
		<pubDate>Thu, 02 Aug 2012 21:13:32 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/itanswers/dynslt-omit/#comment-109779</guid>
		<description><![CDATA[Note that it&#039;s not clear exactly which records you want to process. By showing a WHERE clause and then asking about &#039;Omit&#039;, it&#039;s not clear if you want to process or skip the records from the WHERE clause.
&#160;
Tom]]></description>
		<content:encoded><![CDATA[<p>Note that it&#8217;s not clear exactly which records you want to process. By showing a WHERE clause and then asking about &#8216;Omit&#8217;, it&#8217;s not clear if you want to process or skip the records from the WHERE clause.<br />
&nbsp;<br />
Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TomLiotta</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/dynslt-omit/#comment-109778</link>
		<dc:creator>TomLiotta</dc:creator>
		<pubDate>Thu, 02 Aug 2012 21:06:53 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/itanswers/dynslt-omit/#comment-109778</guid>
		<description><![CDATA[First, you need to have all six of those fields defined in the record format, so three of them will have to be renamed. Second, your WHERE clause is designed for &#039;select&#039;, so its logic&#160;will have to be reversed to give an &#039;omit&#039; result.
Assuming that you RENAME the three fields from file Y to YA, YB and YC, the logical form would be &quot;Omit records with A COMP(NE YA) or with B COMP(NE YB) or with C COMP(NE YC). Select ALL other records.&quot;
&#160;
Does that sound like the logic that you need? What is the actual difficulty you are having?
&#160;
You would probably be better off using SQL to do the work.
&#160;
Tom]]></description>
		<content:encoded><![CDATA[<p>First, you need to have all six of those fields defined in the record format, so three of them will have to be renamed. Second, your WHERE clause is designed for &#8216;select&#8217;, so its logic&nbsp;will have to be reversed to give an &#8216;omit&#8217; result.<br />
Assuming that you RENAME the three fields from file Y to YA, YB and YC, the logical form would be &#8220;Omit records with A COMP(NE YA) or with B COMP(NE YB) or with C COMP(NE YC). Select ALL other records.&#8221;<br />
&nbsp;<br />
Does that sound like the logic that you need? What is the actual difficulty you are having?<br />
&nbsp;<br />
You would probably be better off using SQL to do the work.<br />
&nbsp;<br />
Tom</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/10 queries in 0.036 seconds using memcached
Object Caching 323/329 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-21 21:34:56 -->