 




<?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: RUNSQLSTM ALTER TABLE</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/runsqlstm-alter-table/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/runsqlstm-alter-table/</link>
	<description></description>
	<lastBuildDate>Fri, 24 May 2013 12:30:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: hanisadeq</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/runsqlstm-alter-table/#comment-102974</link>
		<dc:creator>hanisadeq</dc:creator>
		<pubDate>Thu, 16 Feb 2012 07:39:31 +0000</pubDate>
		<guid isPermaLink="false">#comment-102974</guid>
		<description><![CDATA[ERRLVL        30
MSG ID       SEV  RECORD  TEXT                                               
SQL0952  30       1                  Position 1 Processing of the SQL statement ended.  
                                                    Reason code 10.]]></description>
		<content:encoded><![CDATA[<p>ERRLVL        30<br />
MSG ID       SEV  RECORD  TEXT<br />
SQL0952  30       1                  Position 1 Processing of the SQL statement ended.<br />
                                                    Reason code 10.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tomliotta</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/runsqlstm-alter-table/#comment-102943</link>
		<dc:creator>tomliotta</dc:creator>
		<pubDate>Wed, 15 Feb 2012 21:06:31 +0000</pubDate>
		<guid isPermaLink="false">#comment-102943</guid>
		<description><![CDATA[That&#039;s much more useful (though you still didn&#039;t show the message identifier, but it probably isn&#039;t needed if the full message data is shown -- it &lt;i&gt;might&lt;/i&gt; still be needed.)

Next, that shows reason code 8, not reason code 10. However, neither case is a problem unless it actually results in data loss that you cannot accept.

By changing the CCSID, you are potentially changing how much space is needed to store the value. If you don&#039;t also change the size of the column, some of the data might be truncated.

It&#039;s up to you to decide if any values in the column will be larger than the size of the column after the CCSID changes.

What is the error severity? What severity did you specify for the ERRLVL() parameter of the RUNSQLSTM command?

Tom]]></description>
		<content:encoded><![CDATA[<p>That&#8217;s much more useful (though you still didn&#8217;t show the message identifier, but it probably isn&#8217;t needed if the full message data is shown &#8212; it <i>might</i> still be needed.)</p>
<p>Next, that shows reason code 8, not reason code 10. However, neither case is a problem unless it actually results in data loss that you cannot accept.</p>
<p>By changing the CCSID, you are potentially changing how much space is needed to store the value. If you don&#8217;t also change the size of the column, some of the data might be truncated.</p>
<p>It&#8217;s up to you to decide if any values in the column will be larger than the size of the column after the CCSID changes.</p>
<p>What is the error severity? What severity did you specify for the ERRLVL() parameter of the RUNSQLSTM command?</p>
<p>Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hanisadeq</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/runsqlstm-alter-table/#comment-102924</link>
		<dc:creator>hanisadeq</dc:creator>
		<pubDate>Wed, 15 Feb 2012 17:03:10 +0000</pubDate>
		<guid isPermaLink="false">#comment-102924</guid>
		<description><![CDATA[Message . . . . : Change to field INAME may result in data loss. 
Cause . . . . . : A change to field INAME in file DWLOAD in library 
TEST may cause data loss. The reason code is 8. The reason codes and 
their meanings are as follows: 
01 - The field will be dropped. 
02 - The new length is shorter than the current length. 
03 - The new precision is shorter than the current precision. 
04 - The new scale is shorter than the current scale. 
05 - The new data type is floating point and the current data type is not
floating point with the same length. 
06 - The current data type is floating point and the new data type is not
floating point with the same length. 
07 - The new attribute is not nullable and the current attribute is 
nullable. 
08 - The new CCSID is different from the current CCSID. 
09 - The new data type is date, time, or timestamp and the current data 
type is character, DBCS-open, or DBCS-either. 
10 - The new data type is character, DBCS-either, or DBCS-only and the 
current data type is DBCS-open, or the new data type is character or 
DBCS-only and the current data type is DBCS-either. 
Recovery . . . : If the changes to field INAME are not desired, change 
the specified attributes of field INAME and try the function again]]></description>
		<content:encoded><![CDATA[<p>Message . . . . : Change to field INAME may result in data loss.<br />
Cause . . . . . : A change to field INAME in file DWLOAD in library<br />
TEST may cause data loss. The reason code is 8. The reason codes and<br />
their meanings are as follows:<br />
01 &#8211; The field will be dropped.<br />
02 &#8211; The new length is shorter than the current length.<br />
03 &#8211; The new precision is shorter than the current precision.<br />
04 &#8211; The new scale is shorter than the current scale.<br />
05 &#8211; The new data type is floating point and the current data type is not<br />
floating point with the same length.<br />
06 &#8211; The current data type is floating point and the new data type is not<br />
floating point with the same length.<br />
07 &#8211; The new attribute is not nullable and the current attribute is<br />
nullable.<br />
08 &#8211; The new CCSID is different from the current CCSID.<br />
09 &#8211; The new data type is date, time, or timestamp and the current data<br />
type is character, DBCS-open, or DBCS-either.<br />
10 &#8211; The new data type is character, DBCS-either, or DBCS-only and the<br />
current data type is DBCS-open, or the new data type is character or<br />
DBCS-only and the current data type is DBCS-either.<br />
Recovery . . . : If the changes to field INAME are not desired, change<br />
the specified attributes of field INAME and try the function again</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tomliotta</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/runsqlstm-alter-table/#comment-102893</link>
		<dc:creator>tomliotta</dc:creator>
		<pubDate>Tue, 14 Feb 2012 22:58:58 +0000</pubDate>
		<guid isPermaLink="false">#comment-102893</guid>
		<description><![CDATA[&lt;i&gt;i have error Reason code 10 &lt;/i&gt;

The reason code is not useful unless we have the error message identifier. Please post the error message including the message identifier.

Tom]]></description>
		<content:encoded><![CDATA[<p><i>i have error Reason code 10 </i></p>
<p>The reason code is not useful unless we have the error message identifier. Please post the error message including the message identifier.</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/8 queries in 0.036 seconds using memcached
Object Caching 311/312 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-24 12:48:38 -->