While your problem has already been solved by the comments above, another approach could be to use a hash as a translation table for your file names. This way you would not need to iterate through parallel arrays but have the mapping between the IDI and PLL name stored in one structure:

#!/usr/bin/perl use warnings; use strict; use diagnostics; use File::Copy; # Set up hash with original name and new name with unique ISBN my %names = ( 'I:\Production\TEST\P001.txt' => 'I:\Production\TEST\ISBN_Text +.txt', 'I:\Production\TEST\P002.txt' => 'I:\Production\TEST\ISBN2_Tex +t.txt' ); # Walk through hash and copy with new filename while( my( $IDI_name, $PLL_name ) = each %names ) { copy( $IDI_name, $PLL_name ); }

In reply to Re: Renaming multiple files with unique identifiers by hdb
in thread Renaming multiple files with unique identifiers by reedkm

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.