× 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.


  • Subject: RE: Max spool entries 10,000 per JOB??
  • From: "Allen, Mark" <ALLENMA1@xxxxxxxxxx>
  • Date: Thu, 4 Feb 1999 05:12:28 -0800

We have an automated production reporting system.  As each finished good
item travels on a conveyor from final assembly to the distribution center it
is scanned.  That record is then processed against the bill of material to
relieve component inventory (among other things).  When the program that
relieves component inventory runs it produces a report showing what was
relieved.  This report goes to an outq that is not attached to a printer.
This outq is cleared weekly.  The only time the report is looked at is if
there is a perceived inventory relief problem.  So for each finished good
item produced there is a spool file.  We will make anywhere from 5000 to
25000 finished good items per 24 hour period.

-----Original Message-----
From: Bob Larkin [mailto:blarkin@wt.net]
Sent: Wednesday, February 03, 1999 11:38 PM
To: MIDRANGE-L@midrange.com
Subject: Re: Max spool entries 10,000 per JOB??


don't want to sound like a smart a**, but 10,000 seperate printouts is a
LOT.
What are you doing with so many dpool files in one job? If you are actually
driving a printer, consider setting the printer file to *IMMED, instead of
the
default which is *JOBEND or *FILEEND (can't remember which). THis will allow
the
stuff to begin printing immediately, even if you are still writing to the
printer
file. This might work with of the Fax packages also.

So, what are these spool files for Tim?
Bob

Allen, Mark wrote:

> We have the same problem in a job that processes transactions from a
> conveyor.  What we did was have the job end and resubmit itself every 2
> hours, thus creating a new job
>
> -----Original Message-----
> From: mcrump@ballfoster.com [mailto:mcrump@ballfoster.com]
> Sent: Wednesday, February 03, 1999 7:17 AM
> To: MIDRANGE-L@midrange.com
> Subject: Re: Max spool entries 10,000 per JOB??
>
> Tim, you have hit the wall of a long standing OS/400 limitation.  This
> limitation has been in place for as long as I know.  The limit is for how
> many
> spooled files a job can create.  The print file attribute you mentioned is
> for
> the maximum number of records that a given spool file can contain.
>
> There is no way to modify this limit via job or system attributes.  It
comes
> down to job structure and arbitrary limits I believe.  Nice idea for
COMMON.
>
> Tim Truax <truax@usaor.net> on 02/03/99 05:37:28 AM
>
> Please respond to MIDRANGE-L@midrange.com
>
> To:   MIDRANGE-L list <MIDRANGE-L@midrange.com>
> cc:    (bcc: Mike Crump/IS/Ball-Foster)
>
> Subject:  Max spool entries 10,000 per JOB??
>
> Hello All,
> We have a job that runs daily and sends individual prints (spool
> entries) to an OUTQ which is directed to a Faxing utility to perform the
> Fax.  Lately this job will exceed 10,000 spool entries during its daily
> run, and error out.
> I am getting this message (CPF4167 below) that says the number of spool
> entries cannot exceed 10,000 per job.  I have checked the QSYSPRT *prtf
> and it says *NOMAX,  what am I missing?
> Thanks in advance,
>
> ===== error message. ======================
>
> CPF4167    Escape                  40
> 02/01/99   08:33:49   QSPIERRS       QSYS        0028     BIL023RL
> IMP
> Message . . . . :   Job cannot create any more spooled files.
>
> Cause . . . . . :   An attempt was made to create more than the maximum
> number (9,999) of spooled files for the job, or there is no room
> remaining in the job structure to create the file. Recovery  . . . :
> For a job in an interactive environment, sign off and then sign on
> again. For a job in a batch environment, divide the job so that fewer
> files are opened in one job.
>
> +---
> | 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
> +---
> +---
> | 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
> +---


+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.