× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Semiha,

I wouldn't bother to do this. If you look at the system value (WRKSYSVAL)
QRCLSPLSTG this has a default value of 8 days, and the system will clear it
for you (it used to only clear it every 7 IPLs.)
But you need to know that this does NOT clear any spool files. It only
clears the empty space left after you manually delete spool files.

There is also an option on GO ASSIST that does a cleanup periodically, but
this only does message queues and joblogs etc, it does not clear spool
files.

You should have a procedure for manually cleaning up spool files, otherwise
not only do they eat up disk space, but they may make the system slow down.
The system has to maintain entries for them in work control block tables
(initial size is set in system values QTOTJOB and increment in QADLTOTJ) and
may have to resize periodically.

Users probably will not clean up their own spool files, so you may consider
telling them that anything not either printed or moved to a 'Hold' Outq and
more than say 3 days old will be removed.
Obviously you don't want to delete invoices or other important documents.

A good tool for clearing spool files is DLTOLDSPLF where you can set the
number of days old, and any exception outqs. This tool comes in the TAATOOL
package which you can find on the Internet at www.taatool.com. These tools
were written by Jim Sloan who used to work inside IBM Rochester.
You can also use tools like ROBOT (from HelpSystems) to do the job, but that
is more expensive.
One warning on the TAATOOL tools - they work fine if you have primary
language English (QSYS2924), but not if you have Turkish etc.If you have
primary Turkish you may need to do a CHGSYSLIBL to QSYS2924 first.

Hope this helps,

Clare

Clare Holtham
Director, Small Blue Ltd - Archiving for BPCS
Web: www.smallblue.co.uk
IBM Certified AS/400 Systems Professional
E-Mail: Clare.Holtham@xxxxxxxxxxxxxx
Mobile: +44 (0)7960 665958
----- Original Message -----
From: "Semiha Balkaya" <sbalkaya@xxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, March 20, 2003 1:16 PM
Subject: Reclaim Spool Storage Command


hi all

i want to get some information about RCLSPLSTG (Reclaim Spool Storage).
when i looking commands on system i found this command and i wonder about
should i issue this command periodically? When i  get  help for this command
i learned that spool files stored with database members (may be it will be
funny for you but i learned now ) . In which library these files resides?
And is there anything i should  take into consideration before issuing this
command e.g does it increase CPU usage and users's job waits long or how
long does it take this command's completion?
And i saw there are a lot of reclaim commands i wait advice from you that
should i use these command and how can i use these commands? As i say before
these questions will be foolish but i need your help to learn about these
commands....

Thanks to all


Semiha BALKAYA
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.