limiting the Spool Size.

[Former Member]

I would like to seek for your expertise regarding limiting the Spool Size.

As to what we have performed, we should be able to limit the Spool size by

activating System Parameter rspo/auth/pagelimit and also an authorization

object (S_SPO_PAGE) to specify the number of pages. However, upon reviewing

again the parameter and auth object, it will just limit the number of

output pages printed and not totally the output queue stored in the spool

server.

I would like to avoid the system performance issues or growth of

TST03 whenever certain users would incorrectly execute a program in

background and generate a very large Spool.

We also suggest that variant SAP_REORT_SPL, under report RSPO0041 (under

job SAP_REORG_SPOOL), be edited, however, this would not also resolve the

problem. Because reducing the spool retention time would mean that ALL

Spools are impacted and business users will not be able to see Friday

nights spools when they return to office on Monday.

>> Is there a way to stop very large spools (eg. 100,000 pages) ever being

generated?

[JPReyes · Accepted solution]

Hi Neehir,

In my opinion, you don't want to limit the amount of spool requests (or the size) been generated as you never know at what point in time they will be actually created by "mistake" or by an actual requirement.

I think this is more a user training issue than an administration problem, also this should not be a real thread on performance if the REORG job is running.

Regards

Juan

[Former Member]

hi,

can you look at this

[http://sapbasisnotes.blogspot.com/2009/06/spool-administration.html]

Regards,

Muralidhar