ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzalu_5.4.0.1/rzalureclaimsplf.htm

100 lines
6.1 KiB
HTML

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="dc.language" scheme="rfc1766" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<meta name="dc.date" scheme="iso8601" content="2005-09-06" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow"/>
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<title>Reclaim spooled file storage</title>
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
<link rel="stylesheet" type="text/css" href="ic.css" />
</head>
<body>
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
<a name="rzalureclaimsplf"></a>
<h4 id="rzalureclaimsplf">Reclaim spooled file storage</h4>
<p>Use the Reclaim Spool Storage (RCLSPLSTG) command or the Automatically
clean up unused printer output storage (QRCLSPLSTG) system value to reclaim
spooled file storage. These are the only allowable ways to remove spooled
database members from the QSPL or QSPLxxxx libraries. Any other way can cause
severe problems. For more information about spooled file storage, see <a href="rzalusplfstorage.htm#rzalusplfstorage">Spooled file library</a>.</p>
<p><span class="bold">Automatically clean up unused printer output storage (QRCLSPLSTG)
system value</span></p>
<p>Use the Automatically clean up unused printer output storage (QRCLSPLSTG)
system value to adjust the desired balance between spool performance and auxiliary
storage. This system value can be used to cleanup unused printer output storage
on system ASPs, basic user ASPs and independent ASPs. For more information
see, <a href="../rzakz/rzakzqrclsplstg.htm">Storage system values: Automatically clean up
unused printer output storage</a> in the System values topic.</p>
<a name="wq220"></a>
<div class="notetitle" id="wq220">Note:</div>
<div class="notebody">System performance is degraded if Automatically clean up unused
printer output storage (QRCLSPLSTG) is set to 0 days.</div>
<p>Assume that one of your application programs had an error and it produced
thousands of spooled files that were of no value to you. When this happened
those spooled files used lots of storage space on your system. To reclaim
the spool storage, do the following:</p>
<ol type="1">
<li>Change the Automatically clean up unused printer output storage (QRCLSPLSTG)
system value to 1.</li>
<li>Delete all the unwanted spooled files that the application program created.
Note the time of day you deleted all the unwanted spooled files.</li>
<li>After 24 hours, provided the empty spooled file members are not reused,
the system reclaims the auxiliary storage that was being used by the empty
spooled files.</li>
<li>Change the Automatically clean up unused printer output storage (QRCLSPLSTG)
system value back to its former value.</li></ol>
<p><span class="bold">Reclaim Spool Storage (RCLSPLSTG) command</span></p>
<p>Another choice is to use the Reclaim Spool Storage (<a href="../cl/rclsplstg.htm">RCLSPLSTG</a>) command with the DAYS parameter set to *NONE to immediately
reclaim all empty spooled file members. This command can be used to cleanup
unused printer output storage on system ASPs and basic user ASPs. This command
cannot be used to cleanup unused printer output storage on independent ASPs.</p>
<a name="wq222"></a>
<div class="notelisttitle" id="wq222">Notes:</div>
<ol type="1">
<li>The database member is immediately deleted after the deletion of a spooled
file. That means that there is no pool of unused members that can be used
when creating spooled files.</li>
<li>Lock contention can occur on output queues or spool database files, resulting
in bottlenecks and severe performance problems.</li>
</ol>
<p>Assume that one of your application programs had an error and it produced
thousands of spooled files that were of no value to you. When this happened
those spooled files used lots of storage space on your system. To reclaim
the spool storage do the following:</p>
<ol type="1">
<li>Delete all the unwanted spooled files that the application program created.</li>
<li>Run the RCLSPLSTG command with the DAYS parameter set to *NONE. The system
immediately reclaims all auxiliary spool storage that was being used by the
unwanted spooled files.</li></ol>
<p><span class="bold">System ASP storage</span></p>
<p>You can reduce the amount of storage taken up by spooled files by moving
or creating spooled files directly into a user ASP or independent ASP. You
can accomplish this by specifying *OUTQASP on the SPLFASP parameter when creating
an output queue in a library that is located in the desired user ASP or independent
ASP.</p>
<p>All spooled files you place in this output queue will have the spooled
file data stored in the user ASP or independent ASP in a library QSPL<span class="italic">xxxx</span> where <span class="italic">xxxx</span> is the user ASP or independent
ASP number.</p>
<a name="wq225"></a>
<div class="notetitle" id="wq225">Note:</div>
<div class="notebody">For files on a user ASP, the links to the job still reside
on the system ASP. If the system ASP is lost, all spooled files in the user
ASPs are lost. If a user ASP is lost, only spooled files in that user ASP
are lost.</div>
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
</body>
</html>