HP3000-L Archives

May 1999, 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:
Sletten Kenneth W KPWA <[log in to unmask]>
Reply To:
Sletten Kenneth W KPWA <[log in to unmask]>
Date:
Thu, 13 May 1999 12:24:54 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
Lee after Donna,

> > we're thinking about using account limits on our production
> machine and so i've got some questions....

> - it does still work, yes?

AFAIK all Lee said in his response is correct....  A couple more
couple cents again;  on one specific case where we found this
very useful:  OUT.HPSPOOL.   Why ??.....  let me embarrass
myself for a bit:

Many moons ago now we came in one morning and found our
usually faithful HP 3000 was totally unresponsive.  It hadn't
crashed, but it pretty much wouldn't do *anything*.... anyway,
leaving out the intermediate head-scratching, it turned out that
we had a run-away job that was in a very fast, tight loop writing
error messages to a spoolfile.  It turns out that a 959KS/200 can
write a truly *astounding* number of records per second to one
or more spoolfiles if it doesn't have much else to do.  so of course
since DISC LIMIT on OUT.HPSPOOL was = UNLIMITED, in
relatively short order we chewed up all our available permanent
disc space on the SYSVOL.....  which definitely caused MPE to
become unhappy.

Since then we have kept DISC LIMIT on OUT.HPSPOOL big
enough so that during normal operation we will never max out
spoolfile space, but tight enough so that a run-away process will
not bring the system to its knees creating multi-GB spoolfiles....

.....  and now I better get back to real work;  before our faithful
operations staff forms a vigilante committee to hang me for
keeping them waiting...

Ken Sletten

ATOM RSS1 RSS2