 




<?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: Finding source physical files</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/finding-source-physical-files/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/finding-source-physical-files/</link>
	<description></description>
	<lastBuildDate>Thu, 23 May 2013 05:15:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: TomLiotta</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/finding-source-physical-files/#comment-113134</link>
		<dc:creator>TomLiotta</dc:creator>
		<pubDate>Tue, 06 Nov 2012 23:52:45 +0000</pubDate>
		<guid isPermaLink="false">#comment-113134</guid>
		<description><![CDATA[&lt;EM&gt;HOW TO CHANGE THE ATTRIBUTES...&lt;/EM&gt;
&#160;
Can you explain how this relates to finding source files? If not, then you will be better off opening your own question. When you open your question, you need to include a list of &quot;attributes&quot; that you want to change.
&#160;
Tom]]></description>
		<content:encoded><![CDATA[<p><em>HOW TO CHANGE THE ATTRIBUTES&#8230;</em><br />
&nbsp;<br />
Can you explain how this relates to finding source files? If not, then you will be better off opening your own question. When you open your question, you need to include a list of &#8220;attributes&#8221; that you want to change.<br />
&nbsp;<br />
Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: venky41561</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/finding-source-physical-files/#comment-113124</link>
		<dc:creator>venky41561</dc:creator>
		<pubDate>Tue, 06 Nov 2012 18:30:19 +0000</pubDate>
		<guid isPermaLink="false">#comment-113124</guid>
		<description><![CDATA[HOW TO CHANGE THE ATTRIBUTES OF A PF WITHOUT LOOSING THE DATA]]></description>
		<content:encoded><![CDATA[<p>HOW TO CHANGE THE ATTRIBUTES OF A PF WITHOUT LOOSING THE DATA</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Featured Member: PGMBOB - ITKE Community Blog</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/finding-source-physical-files/#comment-87020</link>
		<dc:creator>Featured Member: PGMBOB - ITKE Community Blog</dc:creator>
		<pubDate>Tue, 25 Jan 2011 06:51:34 +0000</pubDate>
		<guid isPermaLink="false">#comment-87020</guid>
		<description><![CDATA[[...] Finding source physical files [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Finding source physical files [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tomliotta</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/finding-source-physical-files/#comment-69813</link>
		<dc:creator>tomliotta</dc:creator>
		<pubDate>Sun, 01 Nov 2009 07:53:07 +0000</pubDate>
		<guid isPermaLink="false">#comment-69813</guid>
		<description><![CDATA[Note that file QSYS/QADBXREF is a physical system file that is in constant use by DB2 itself and technically should not be accessed directly. Unusual interruptions of system activity against this file can be troublesome causes of database catalog inconsistencies. The RCLSTG SELECT(*DBXREF) can help correct such inconsistencies, but database operation is somewhat unpredictable until corrections are done.

It is better to use any of the logical files and SQL views that IBM has provided to review the info. For example, logical file QADBXATR provides field DBXTYP to expose &#039;D&#039;=Data or &#039;S&#039;=Source physical file.

A full list of LFs/views can be seen from DSPDBR QADBXREF.

Tom]]></description>
		<content:encoded><![CDATA[<p>Note that file QSYS/QADBXREF is a physical system file that is in constant use by DB2 itself and technically should not be accessed directly. Unusual interruptions of system activity against this file can be troublesome causes of database catalog inconsistencies. The RCLSTG SELECT(*DBXREF) can help correct such inconsistencies, but database operation is somewhat unpredictable until corrections are done.</p>
<p>It is better to use any of the logical files and SQL views that IBM has provided to review the info. For example, logical file QADBXATR provides field DBXTYP to expose &#8216;D&#8217;=Data or &#8216;S&#8217;=Source physical file.</p>
<p>A full list of LFs/views can be seen from DSPDBR QADBXREF.</p>
<p>Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: waltz400</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/finding-source-physical-files/#comment-44591</link>
		<dc:creator>waltz400</dc:creator>
		<pubDate>Thu, 18 Aug 2005 12:44:35 +0000</pubDate>
		<guid isPermaLink="false">#comment-44591</guid>
		<description><![CDATA[DSPOBJD finds all physical files in a library with an object type of *FILE and an object attribute of PF. Both source and physical data files are tagged this way. So unless your shop only uses Q* default names for source files and follows the IBM recommendation that you don&#039;t name any user objects starting with Q, I don&#039;t see how a DSPOBJD will find only source files. 

File QADBXREF is built by the operating system and is constantly updated as new files are added, changed or deleted. And the data on this file knows the difference between a data or source PF. ]]></description>
		<content:encoded><![CDATA[<p>DSPOBJD finds all physical files in a library with an object type of *FILE and an object attribute of PF. Both source and physical data files are tagged this way. So unless your shop only uses Q* default names for source files and follows the IBM recommendation that you don&#8217;t name any user objects starting with Q, I don&#8217;t see how a DSPOBJD will find only source files. </p>
<p>File QADBXREF is built by the operating system and is constantly updated as new files are added, changed or deleted. And the data on this file knows the difference between a data or source PF. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mcsick</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/finding-source-physical-files/#comment-44592</link>
		<dc:creator>mcsick</dc:creator>
		<pubDate>Wed, 17 Aug 2005 21:41:02 +0000</pubDate>
		<guid isPermaLink="false">#comment-44592</guid>
		<description><![CDATA[You can also use the Display Object Description command to locate Source Physical Files:
DSPOBJD OBJ(*ALL/*ALL)             
        OBJTYPE(*FILE)             
        OUTPUT(*OUTFILE)           
        OUTFILE(YOURLIB/DSPOBJDFLE)
then use WRKQRY if you have it to query the file for PF-SRC files.]]></description>
		<content:encoded><![CDATA[<p>You can also use the Display Object Description command to locate Source Physical Files:<br />
DSPOBJD OBJ(*ALL/*ALL)<br />
        OBJTYPE(*FILE)<br />
        OUTPUT(*OUTFILE)<br />
        OUTFILE(YOURLIB/DSPOBJDFLE)<br />
then use WRKQRY if you have it to query the file for PF-SRC files.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: waltz400</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/finding-source-physical-files/#comment-44593</link>
		<dc:creator>waltz400</dc:creator>
		<pubDate>Tue, 16 Aug 2005 12:27:51 +0000</pubDate>
		<guid isPermaLink="false">#comment-44593</guid>
		<description><![CDATA[In QSYS library there is a file named QADBXREF that contains a record for every DB file on the system. There are codes on the file that say whether the file is an LF or PF and if a PF whether it is a data or source file. To get a list of source files, in SQL execute the following: 

SELECT * FROM qadbxref WHERE DBXATR = &#039;PF&#039; and 
DBXTYP = &#039;S&#039; 

This will get you a list of all source physical files on your iSeries. If you want just those in a particular library add selection to your WHERE. ]]></description>
		<content:encoded><![CDATA[<p>In QSYS library there is a file named QADBXREF that contains a record for every DB file on the system. There are codes on the file that say whether the file is an LF or PF and if a PF whether it is a data or source file. To get a list of source files, in SQL execute the following: </p>
<p>SELECT * FROM qadbxref WHERE DBXATR = &#8216;PF&#8217; and<br />
DBXTYP = &#8216;S&#8217; </p>
<p>This will get you a list of all source physical files on your iSeries. If you want just those in a particular library add selection to your WHERE. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cyates</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/finding-source-physical-files/#comment-44594</link>
		<dc:creator>cyates</dc:creator>
		<pubDate>Tue, 16 Aug 2005 11:45:07 +0000</pubDate>
		<guid isPermaLink="false">#comment-44594</guid>
		<description><![CDATA[The PDM option is best if you want to find a source member so you can change it. If you just want a list of where the files are you can do the following:
DSPFD FILE(library to check/*ALL) TYPE(*BASATR) OUTPUT(*OUTFILE) OUTFILE(library/file to hold output)
If the field ATFILA = *PHY and field ATDTAT = S it is a source physical file.
You can use the outfile created from the command in a query, RPG, or CL program.                     ]]></description>
		<content:encoded><![CDATA[<p>The PDM option is best if you want to find a source member so you can change it. If you just want a list of where the files are you can do the following:<br />
DSPFD FILE(library to check/*ALL) TYPE(*BASATR) OUTPUT(*OUTFILE) OUTFILE(library/file to hold output)<br />
If the field ATFILA = *PHY and field ATDTAT = S it is a source physical file.<br />
You can use the outfile created from the command in a query, RPG, or CL program.                     </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.010 seconds using memcached
Object Caching 366/369 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-23 05:29:35 -->