 




<?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: Pointer not set for location referenced</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/pointer-not-set-for-location-referenced/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/pointer-not-set-for-location-referenced/</link>
	<description></description>
	<lastBuildDate>Sat, 25 May 2013 17:28:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: tomliotta</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/pointer-not-set-for-location-referenced/#comment-80236</link>
		<dc:creator>tomliotta</dc:creator>
		<pubDate>Thu, 12 Aug 2010 07:15:04 +0000</pubDate>
		<guid isPermaLink="false">#comment-80236</guid>
		<description><![CDATA[It&#039;s possible that the binding of the C module could be involved, if a procedure in that module has been called before statement 361 in the COBOL module was reached. But without seeing the COBOL CALL statement, the definition of COBOL variables involved in the call and the C prototype that was called, there&#039;s no way for us to tell.

In any case, the &lt;i&gt;reported&lt;/i&gt; error is involved with one of the files used by the COBOL module. The C module could be involved if there was a parameter mismatch and thereby the call into C resulted in corruption of the file interface.

Show some code so we can guess.

Tom]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s possible that the binding of the C module could be involved, if a procedure in that module has been called before statement 361 in the COBOL module was reached. But without seeing the COBOL CALL statement, the definition of COBOL variables involved in the call and the C prototype that was called, there&#8217;s no way for us to tell.</p>
<p>In any case, the <i>reported</i> error is involved with one of the files used by the COBOL module. The C module could be involved if there was a parameter mismatch and thereby the call into C resulted in corruption of the file interface.</p>
<p>Show some code so we can guess.</p>
<p>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.033 seconds using memcached
Object Caching 267/273 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-25 17:47:11 -->