HP3000-L Archives

July 2001, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Atwood, Tim (DVM)" <[log in to unmask]>
Reply To:
Atwood, Tim (DVM)
Date:
Mon, 9 Jul 2001 12:01:28 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
We had a program go into a loop on a write to a spool file over the weekend.
The spool file got so large it eventually shut down the spoolers and more or
less hung the system.

Does anyone have any suggestions for how to limit spool file size? I thought
I had figured this out before, but the dreaded CRS disease must be taking
it's toll (Can't Remember S...).

Apparently DISC= is ignored on spool files since the following did not limit
the size.

IP1080P1;DEV=SPCLS99;DISC=25000;ENV=SLPL132F.PRTENV.SYS

Any other suggestions? Anything I can do globally? I can not imagine any
legitimate reason why anything should ever create a spool file over 100,000
sectors.

(MPE/iX 6.0 PP 2)

Timothy Atwood
Holtenwood Computing
for Domtar Vancouver Mill
http://www.holtenwood.bc.ca/computing/

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2