Generally on VMS the way things like this are done is via nonblocking pending locks with callback ASTs on lock aquisition, or monitoring mailboxes for notifications from spawned subprocesses.

VMS fully supports tying the input and output handles to a spawned subprocess simultaneously, though I don't think anyone's gotten around to adding it to VMS perl (The infamous open FOO, "| process |" that doesn't work on Unix).

Probably the right thing to do is to spawn off subprocesses with normal magic open capturing the output of the child process and monitor the return filehandle. Or you could use a threaded perl, I suppose, if you don't want to do that.

In reply to Re: fork() emulation hack for OpenVMS by Elian
in thread fork() emulation hack for OpenVMS by agarsha

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.