Jeff Kell ([log in to unmask]) wrote:

[...]

: * Finally, a "maximum number of spoofles" can affect you if you have
:   many batch jobs generating spool files that remain in the queue.

There are two separate aspects to this:
o   On a classic system, the spool file directory is the ODD, a system
    data segment.  It is limited to roughly 600-800 spool file entries,
    depending on your hardware configuration (which shares ODD space
    with the spool file directory entries).  This is due to the size
    limitations of all classic MPE extra data segments.  If no entry
    is available when needed, the user trying to FOPEN a spooled
    devicefile gets DEVICE UNAVAILABLE (FSERR 55).

o   There is also the Maximum Number of Open Spoolfiles configuration
    item in Sysdump.  Due to the way virtual (spooled) devices are
    implemented in MPE V/E, this configuration is actually specifying
    the size (number of entries) in the LDT and LPDT (two other system
    data segments).  Again, if an entry is not available in these
    tables, you also get FSERR 55.  This applies only to spool files
    that are being created by their user.  Once the user FCLOSEs the
    spooled devicefile and it enters the READY state, the entry used
    while the file was being created is returned to the pool for use
    by another user.

Hope that helps.

-Larry "haven't thought about MPE V/E spooling in awhile" Byler-