 




<?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: AS400 Cleanup QRCL QRECOVERY QRPLOBJ</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/as400-cleanup-qrcl-qrecovery-qrplobj/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/as400-cleanup-qrcl-qrecovery-qrplobj/</link>
	<description></description>
	<lastBuildDate>Sat, 25 May 2013 23:02:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: tomliotta</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/as400-cleanup-qrcl-qrecovery-qrplobj/#comment-99836</link>
		<dc:creator>tomliotta</dc:creator>
		<pubDate>Mon, 05 Dec 2011 22:03:46 +0000</pubDate>
		<guid isPermaLink="false">#comment-99836</guid>
		<description><![CDATA[&lt;i&gt;...that would definately NOT be a ‘Best Practice’.&lt;/i&gt;

Yet at least one widely used commercial app has been said to do exactly that. Internet searches provide a couple comments. Regardless, yes, it&#039;s probably not a good practice. It&#039;s too easy to create a library of your own with appropriate ownership/authority.

Tom]]></description>
		<content:encoded><![CDATA[<p><i>&#8230;that would definately NOT be a ‘Best Practice’.</i></p>
<p>Yet at least one widely used commercial app has been said to do exactly that. Internet searches provide a couple comments. Regardless, yes, it&#8217;s probably not a good practice. It&#8217;s too easy to create a library of your own with appropriate ownership/authority.</p>
<p>Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nickhutcheson1</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/as400-cleanup-qrcl-qrecovery-qrplobj/#comment-99814</link>
		<dc:creator>nickhutcheson1</dc:creator>
		<pubDate>Mon, 05 Dec 2011 14:13:37 +0000</pubDate>
		<guid isPermaLink="false">#comment-99814</guid>
		<description><![CDATA[&lt;i&gt;if you have applications creating things in QRECOVERY or QRCL&lt;/i&gt;

That sounds like something that would definately NOT be a &#039;Best Practice&#039;.
Thanks Tom.
Nick]]></description>
		<content:encoded><![CDATA[<p><i>if you have applications creating things in QRECOVERY or QRCL</i></p>
<p>That sounds like something that would definately NOT be a &#8216;Best Practice&#8217;.<br />
Thanks Tom.<br />
Nick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tomliotta</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/as400-cleanup-qrcl-qrecovery-qrplobj/#comment-99753</link>
		<dc:creator>tomliotta</dc:creator>
		<pubDate>Sat, 03 Dec 2011 08:33:09 +0000</pubDate>
		<guid isPermaLink="false">#comment-99753</guid>
		<description><![CDATA[Of course, if you have applications creating things in QRECOVERY or QRCL, then deleting the objects is no different from deleting them from any other library. They&#039;re not libraries that should be used, though.

Tom]]></description>
		<content:encoded><![CDATA[<p>Of course, if you have applications creating things in QRECOVERY or QRCL, then deleting the objects is no different from deleting them from any other library. They&#8217;re not libraries that should be used, though.</p>
<p>Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tomliotta</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/as400-cleanup-qrcl-qrecovery-qrplobj/#comment-99752</link>
		<dc:creator>tomliotta</dc:creator>
		<pubDate>Sat, 03 Dec 2011 08:29:07 +0000</pubDate>
		<guid isPermaLink="false">#comment-99752</guid>
		<description><![CDATA[&lt;i&gt;Am I correct in saying that the objects in QRCL, QRECOVERY, QRPLOBJ libraries can be deleted?&lt;/i&gt;

Yes and no.

QRPLOBJ objects can often be deleted once you no longer need them. It clears during every IPL. These are generally objects that have been replaced by new versions. When you compile a program and replace the existing version, the original one is moved to QRPLOBJ. By doing such a library-to-library move, any pointers that are currently resolved to the object can remain valid. That&#039;s why you can often recompile programs even while they are being used. Other objects are also moved to QRPLOBJ, like user spaces created with the &#039;Create if already exists&#039; parameter set as &#039;*YES&#039;.

Delete QRPLOBJ objects that you can recognize. Be aware that objects might actually be in use.

QRCL will contain recovered results from RCLSTG. Common objects will probably be some that were temporary and the the system was improperly shut down, e.g., without going to restricted state first. But needed objects might be reclaimed into that library under some circumstances. If the objects are clearly not going to be put back wherever they belong, i.e., they&#039;re not permanents objects that you want to keep, there&#039;s no reason not to delete them.

QRECOVERY -- leave everything in it alone. Stuff in there is system stuff, not for you.

Tom]]></description>
		<content:encoded><![CDATA[<p><i>Am I correct in saying that the objects in QRCL, QRECOVERY, QRPLOBJ libraries can be deleted?</i></p>
<p>Yes and no.</p>
<p>QRPLOBJ objects can often be deleted once you no longer need them. It clears during every IPL. These are generally objects that have been replaced by new versions. When you compile a program and replace the existing version, the original one is moved to QRPLOBJ. By doing such a library-to-library move, any pointers that are currently resolved to the object can remain valid. That&#8217;s why you can often recompile programs even while they are being used. Other objects are also moved to QRPLOBJ, like user spaces created with the &#8216;Create if already exists&#8217; parameter set as &#8216;*YES&#8217;.</p>
<p>Delete QRPLOBJ objects that you can recognize. Be aware that objects might actually be in use.</p>
<p>QRCL will contain recovered results from RCLSTG. Common objects will probably be some that were temporary and the the system was improperly shut down, e.g., without going to restricted state first. But needed objects might be reclaimed into that library under some circumstances. If the objects are clearly not going to be put back wherever they belong, i.e., they&#8217;re not permanents objects that you want to keep, there&#8217;s no reason not to delete them.</p>
<p>QRECOVERY &#8212; leave everything in it alone. Stuff in there is system stuff, not for you.</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.037 seconds using memcached
Object Caching 309/315 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-26 01:24:22 -->