Hi,
please use <code> tags for your code examples and <c></c> for your inline code. Also using perltidy to tidy up your longer code is very much recommended. This makes your posts much more readable.

To access the read server and location use $servers{$server} and $locs{$loc} as shown below. You can - and should - also check if the given server and location really exists, which can be done with if (exists $servers{$server}) { } etc. 

my %locs = (
    one   => '\c$\files',
    two   => '\d$\stuff',
    three => '\d$\things'
);
my %servers = (
    ksl => '\\server1',
    krf => '\\server2'
);

my $server = <STDIN>;
chomp $server;

my $loc = <STDIN>;
chomp $loc;

print $servers{$server}, "\n";
print $locs{$loc}, "\n";

[download]

In reply to Re: pulling value based on input by mscharrer
in thread pulling value based on input by kwn

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.