You didn't tell us, what goes wrong.

Your code is syntactical correct. But:

• Where does $n come from?
• Where does $dump_path come from?

They may contain special shell characters like &, ;, `, ', ", |, *, ?, ~, <, >, ^, (, ), [, ], {, }, $ and \.

Your CGI-script mostly does not run under the same UID as your command line script, so you should think of:

• Is your "CGI"-user able to execute /usr/local/bin/dcm_dump_file?
• Does "he" have enough rights to write into $dump_path.'PCfiles/dumpfile'?

To examine your situation, you should look at possible errors and use backticks with redirecting STDERR to STDOUT:

# see what happens
print `$your command 2>&1 > output`;
[download]

-- Frank

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.