The problem may be in the shell that is being used by IIS to run the process -- I'm only guessing here, since I have no contact with any version IIS. If one of the differences between IIS 5 and IIS 6 is the nature of the shell used to run sub-processes, it's conceivable (though stupid) that they would choose to disable pipeline commands.

If you're using sub-shells to run utilities that talk to a general-purpose database (like oracle or some other ODBC-capable server), you might consider using the DBI module and connecting your script directly to the database. It would mean replicating in your perl script the queries that are implemented by the current command line utilities, but this might enable a lot of possibilities...

In reply to Re^3: IIS 6 and perl 5.8 pipes by graff
in thread IIS 6 and perl 5.8 pipes by aquarium

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.