<?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"
	>
<channel>
	<title>Comments on: Number of records in the Flat file</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/number-of-records-in-the-flat-file/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/number-of-records-in-the-flat-file/</link>
	<description></description>
	<pubDate>Sat, 26 May 2012 05:06:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: anettis</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/number-of-records-in-the-flat-file/#comment-48615</link>
		<dc:creator>anettis</dc:creator>
		<pubDate>Thu, 27 Apr 2006 07:18:22 +0000</pubDate>
		<guid isPermaLink="false">#comment-48615</guid>
		<description>L 999999 may not work if the file is too large.  And if it did work I don't see how its performance would be any different than using MAX page down (PF8).  As a flag (QSAM) file the only way to reach the end of the file is to read each record.</description>
		<content:encoded><![CDATA[<p>L 999999 may not work if the file is too large.  And if it did work I don&#8217;t see how its performance would be any different than using MAX page down (PF8).  As a flag (QSAM) file the only way to reach the end of the file is to read each record.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fskovacs</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/number-of-records-in-the-flat-file/#comment-48616</link>
		<dc:creator>fskovacs</dc:creator>
		<pubDate>Thu, 27 Apr 2006 07:07:31 +0000</pubDate>
		<guid isPermaLink="false">#comment-48616</guid>
		<description>If the file is so large that ISPF is problematical, I use SORT with SYSIN as SORT FIELDS=COPY and SORTOUT going to DUMMY. The record count will be in SYSPRINT </description>
		<content:encoded><![CDATA[<p>If the file is so large that ISPF is problematical, I use SORT with SYSIN as SORT FIELDS=COPY and SORTOUT going to DUMMY. The record count will be in SYSPRINT</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DennisW</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/number-of-records-in-the-flat-file/#comment-48617</link>
		<dc:creator>DennisW</dc:creator>
		<pubDate>Wed, 26 Apr 2006 23:53:21 +0000</pubDate>
		<guid isPermaLink="false">#comment-48617</guid>
		<description>Several of the suggestions in previous replys should work. An IDCAMS print would seem the most accurate, just put output to a DD DUMMY or you might never compete the run for a large file.

There may be a message with how many records were written to the file in a the log of the job that wrote it - if still available and the program or utility used displayed this information.

</description>
		<content:encoded><![CDATA[<p>Several of the suggestions in previous replys should work. An IDCAMS print would seem the most accurate, just put output to a DD DUMMY or you might never compete the run for a large file.</p>
<p>There may be a message with how many records were written to the file in a the log of the job that wrote it - if still available and the program or utility used displayed this information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: garth1m</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/number-of-records-in-the-flat-file/#comment-48618</link>
		<dc:creator>garth1m</dc:creator>
		<pubDate>Wed, 26 Apr 2006 07:30:26 +0000</pubDate>
		<guid isPermaLink="false">#comment-48618</guid>
		<description>Goto ISPF browse on the file
L 9999999
Locates the last line
I think it's quicke than using max but haven't tested it
The other space calculation methods may give you approximations.</description>
		<content:encoded><![CDATA[<p>Goto ISPF browse on the file<br />
L 9999999<br />
Locates the last line<br />
I think it&#8217;s quicke than using max but haven&#8217;t tested it<br />
The other space calculation methods may give you approximations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anettis</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/number-of-records-in-the-flat-file/#comment-48619</link>
		<dc:creator>anettis</dc:creator>
		<pubDate>Tue, 25 Apr 2006 09:13:07 +0000</pubDate>
		<guid isPermaLink="false">#comment-48619</guid>
		<description>Simply view the file under ISPF, max to the bottom, and look left to the last line number - BINGO.  Now if you are talking about doing it programatically - that is another story.</description>
		<content:encoded><![CDATA[<p>Simply view the file under ISPF, max to the bottom, and look left to the last line number - BINGO.  Now if you are talking about doing it programatically - that is another story.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jamig77</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/number-of-records-in-the-flat-file/#comment-48620</link>
		<dc:creator>jamig77</dc:creator>
		<pubDate>Mon, 24 Apr 2006 08:56:31 +0000</pubDate>
		<guid isPermaLink="false">#comment-48620</guid>
		<description>the fastest most efficient way is to use idcams with jcl. use the print command, it will return the exact number of records,

sort will work, and is good, but you still use too much system resource
tso editor is again a hog

sql is fine - again the overhead and up front work to run the query against it</description>
		<content:encoded><![CDATA[<p>the fastest most efficient way is to use idcams with jcl. use the print command, it will return the exact number of records,</p>
<p>sort will work, and is good, but you still use too much system resource<br />
tso editor is again a hog</p>
<p>sql is fine - again the overhead and up front work to run the query against it</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wadoman</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/number-of-records-in-the-flat-file/#comment-48621</link>
		<dc:creator>Wadoman</dc:creator>
		<pubDate>Mon, 24 Apr 2006 05:18:03 +0000</pubDate>
		<guid isPermaLink="false">#comment-48621</guid>
		<description>I would use an IDCAMS REPRO.
Using the same space requirements as your original file, repro the file to a new file.
The output from your JCL should give you the exact number of records copied from the one file to the other.
Another way is to use a SELCOPY, but the REPRO will be the quickest of the two.
Hope this helps. </description>
		<content:encoded><![CDATA[<p>I would use an IDCAMS REPRO.<br />
Using the same space requirements as your original file, repro the file to a new file.<br />
The output from your JCL should give you the exact number of records copied from the one file to the other.<br />
Another way is to use a SELCOPY, but the REPRO will be the quickest of the two.<br />
Hope this helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chavan</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/number-of-records-in-the-flat-file/#comment-48622</link>
		<dc:creator>Chavan</dc:creator>
		<pubDate>Mon, 24 Apr 2006 01:50:07 +0000</pubDate>
		<guid isPermaLink="false">#comment-48622</guid>
		<description>I think whether you go for PCSHELL utility you will be get easily and exact result.

Thnks.
</description>
		<content:encoded><![CDATA[<p>I think whether you go for PCSHELL utility you will be get easily and exact result.</p>
<p>Thnks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DDekreon</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/number-of-records-in-the-flat-file/#comment-48623</link>
		<dc:creator>DDekreon</dc:creator>
		<pubDate>Sun, 23 Apr 2006 02:49:24 +0000</pubDate>
		<guid isPermaLink="false">#comment-48623</guid>
		<description>select count(*) from tablename (sql)
</description>
		<content:encoded><![CDATA[<p>select count(*) from tablename (sql)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mikeshor</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/number-of-records-in-the-flat-file/#comment-48624</link>
		<dc:creator>mikeshor</dc:creator>
		<pubDate>Sat, 22 Apr 2006 14:10:11 +0000</pubDate>
		<guid isPermaLink="false">#comment-48624</guid>
		<description>If the file is fixed or fixed block, I would go to ISPF option 3.2, ask for information on the file and divide the space that it takes up by the LRECL</description>
		<content:encoded><![CDATA[<p>If the file is fixed or fixed block, I would go to ISPF option 3.2, ask for information on the file and divide the space that it takes up by the LRECL</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->
