<?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: DB2/400</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/db2400/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/db2400/</link>
	<description></description>
	<lastBuildDate>Wed, 19 Jun 2013 16:59:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: tjgm88</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/db2400/#comment-56164</link>
		<dc:creator>tjgm88</dc:creator>
		<pubDate>Thu, 04 Sep 2008 22:55:30 +0000</pubDate>
		<guid isPermaLink="false">#comment-56164</guid>
		<description><![CDATA[Just to add to the discussion.
Logical Files are just a set of indixes providing an ordered access as per the key(s) defined. The data still resides in the physical that the logical is built over.
Howerever, any updates/deletes done via the logical updates teh physical.
Logical files are very useful to reorder the data, but bead in mind the response implications when too many logicals are built ove the same physical.  Any update to the physical will trigger updates to all the logicals (especially if *IMMED is specified) and can have an impact on response times.
Cheers!]]></description>
		<content:encoded><![CDATA[<p>Just to add to the discussion.<br />
Logical Files are just a set of indixes providing an ordered access as per the key(s) defined. The data still resides in the physical that the logical is built over.<br />
Howerever, any updates/deletes done via the logical updates teh physical.<br />
Logical files are very useful to reorder the data, but bead in mind the response implications when too many logicals are built ove the same physical.  Any update to the physical will trigger updates to all the logicals (especially if *IMMED is specified) and can have an impact on response times.<br />
Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: philpl1jb</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/db2400/#comment-56157</link>
		<dc:creator>philpl1jb</dc:creator>
		<pubDate>Thu, 04 Sep 2008 17:30:25 +0000</pubDate>
		<guid isPermaLink="false">#comment-56157</guid>
		<description><![CDATA[Logical files with the default setting for MAINT(*IMMEDIATE) provide an up-to-date map of the data by updating the map with every add/delete or key change in the file(s).  

Logical file with maint(*REBUILD) is very much like a view, it contains the rules and when used will build the required index on the fly.  No overhead when it&#039;s not in use, significant when it is.  The logical file can be keyed which is useful in native languages, the view can be sorted.

An SQL Index resembles the logical file MAINT(*IMMEDIATE) in that it maintains a map of the data, however, an index does not provide alternate formats or joins.

I&#039;m sure there is more.

Phil]]></description>
		<content:encoded><![CDATA[<p>Logical files with the default setting for MAINT(*IMMEDIATE) provide an up-to-date map of the data by updating the map with every add/delete or key change in the file(s).  </p>
<p>Logical file with maint(*REBUILD) is very much like a view, it contains the rules and when used will build the required index on the fly.  No overhead when it&#8217;s not in use, significant when it is.  The logical file can be keyed which is useful in native languages, the view can be sorted.</p>
<p>An SQL Index resembles the logical file MAINT(*IMMEDIATE) in that it maintains a map of the data, however, an index does not provide alternate formats or joins.</p>
<p>I&#8217;m sure there is more.</p>
<p>Phil</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 6/9 queries in 0.012 seconds using memcached
Object Caching 282/285 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-06-19 17:46:20 -->