My thanks to all who offered advice. Here is the solution now put into practice (most of the irrelevant code omitted). Note I had to use a homegrown alternative to FileHandle because its documentation didn't mention support of Open3. That was just an array of self-numbering filehandles for easy deletion. 
package jiloader;

use Parallel::ForkManager;
use IPC::Open3;
use Fcntl qw(:flock SEEK_END);

sub new {
...
        $opt { MAXFORKS } ||= 31;
        $opt{ PM } = new Parallel::ForkManager( $opt{ MAXFORKS } );

        $opt{ PMFH } = []; # filehandle pool
...
        # example of one of four files that track things
        unlink $opt{REJFILE};
        open my $rejh, ">>$opt{REJFILE}"
          or die "$!: $opt{REJFILE}\n";
        $opt{ REJH } = $rejh;
...
        bless \%opt;
}

...


sub put {
        # batch changes by outer box
        # for submission to fork scheduler

        my $self = shift;

        if ( $self -> { REST } ) {
                if ( $self -> { TOPBOX } ) {
                        $self -> { BATCH } and $self -> sched;
                }
                $self -> { BATCH } .= $self -> { CHG };
        }
        else {
                $self -> { BATCH } .= $self -> { CHG };
                $self -> sched;
        }
}
sub sched {
        my $self = shift;
        my $pm = $self -> { PM };

        my $rh = $self -> getfh;
        my $wh = $self -> getfh;
        my $eh = $self -> getfh;

        # parent has allocated fh's so has to
        # free them when child exits
        # child cannot do this whatever the fh pooling solution

        $pm -> run_on_finish( sub { $self -> killfh( $rh, $wh, $eh ); 
+} );

        unless( $pm -> start ) {

                open3 $wh, $rh, $eh,  $self -> { JILCOMMAND };
                print $wh $self -> { BATCH };
                close $wh;
                unless ( $self -> jiloutparse( $rh, $eh ) ) {
                        my $errh = $self -> { ERRH };
                        flock $self -> { ERRFILE }, LOCK_EX;
                        print $errh $self -> { LASTOUT };
                        print $errh $self -> { LASTERR };
                        flock $self -> { ERRFILE }, LOCK_UN
                }
                close $rh;
                close $eh;
                $pm -> finish;
        }
        $self -> { BATCH } = '';

}
...

[download]

One world, one people

In reply to Re: fixed set of forked processes by anonymized user 468275
in thread fixed set of forked processes by anonymized user 468275

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.