...please respond to...

I know we've told you before that's not how this site works. Responding in private to questions posted publicly has the following problems:

• Multiple individuals may all waste time working to provide the same solution, repeatedly.
• The work is wasted on just you, whereas posted publicly others might benefit from the knowledge embodied in the responses you get.
• The answers you get don't benefit from the synergistic effect of others reading them, and possibly responding with additional refinements.
• We don't work for you; we contribute to this site. Our answers are intended to benefit users of the site.

Next: Please read Writeup Formatting Tips and fix the formatting of your post. While you're at it, consider that we don't necessarily have the benefit of knowing what you're thinking. We only know what you have written, and what you wrote is neither clear enough nor complete enough for us to have a complete and clear picture of the problem we're trying to solve.

Often it helps to include sample code, sample input, expected output, and sample error messages. When a given post doesn't deal with Perl code, you should do a sanity-check before posting to verify that it is, indeed, a Perl question. Non-Perl questions are generally off-topic here. The fact that you think the solution may include writing a Perl script doesn't turn it into a Perl question until you actually involve Perl.

Finally, if you're having trouble moving files at the OS/shell level, why would it be easier for Perl to do so? If mv fails for you for permissions issues, you lack the permissions necessary to mv the file, and that doesn't change when a Perl script runs in your behalf. You may need to run under elevated privileges, or you might need to contact your server's administrator, because certainly that person is in a better position to help you resolve issues regarding file permissions.