RE: QSPL question/limit

["Shaw, David" <dshaw@xxxxxxxxxxx>]

Bob,

That's funky.  I've never seen that, but of course I've never worked with a
system big enough to have that many spool files lying around.  Have you
considered turning on job accounting to see if it would record whatever's
killing your spool files?

Dave Shaw
Spartan International, Inc.
Spartanburg, SC

> -----Original Message-----
> From: Marion, Bob [mailto:Bob.Marion@ps.net]
> 
> Greetings:
> 
> I may have hit a another system limit or a system bug and 
> wanted to see if
> anyone else has experienced this situation(V4R4).  In April 
> and May (15th) a
> large number of spool files just disappeared without the 
> deletion logging in
> DSPLOG, SST, DSPJOLOG, Performance tools or auditing log and 
> no job came out
> of job scheduler at that time.  We are doing a large back 
> file project for a
> customer for COLD, in April one outq  went from about 150,000 
> Spoolfiles to
> 105,000 without a trace, at the time I chalked it up to some 
> undeterminable
> human error.  I then created an outq in a private library(not 
> in*LIBL) and
> moved the spoolfiles there and added more spooolfiles and was 
> up to 180,000,
> then on 5/15 within 5 mins the total number went from about 180,000 to
> 105,000 and the spoolfiles that disappeared were the 80,000 
> most current
> spoolfiles.  QSPL is about 63GB and currently about 311 PFs 
> in QSPL.  It
> looks like the system maintains a maximum of 1001 members per 
> PF file in
> QSPL..  DSPLIB shows no damaged object.  Profile QSPL is 54% full.
> 
> My logic says for some reason the system is deleting active 
> members in the
> PF, the other common fact is both times the outq went down to 
> about 105,000.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---