Which queuing system are you using? I have used SGE, which requires a shell script for submission, but it is easy enough to write a single shell script wrapper, effectively:

--wrap.sh--
#!/bin/sh

"$@"
[download]

---------

If you look at the shell docs, you will see that the $@ expands to all the arguments, and putting it in quotes ensures that any spaces in any of the argument values will still be quoted (i.e. they won't cause arguments to be split on spaces).

Then one can submit thusly:

qsub -o <log> -q <queue> [other qsub args] wrap.sh perl scriptname scr
+iptargs
[download]

If you have a submitting job and the sub jobs that need to communicate, you can still use pipes if that makes sense. And obviously if you have the proper shebang line in your perl script you don't need to call perl explicitly.

Perhaps this trick will help you think of other ways to solve your issue.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.