To elaborate on what choroba said, the sub can see variables in the scope in which it is declared, not the scope in which it is called. In this case, printjob can only see variables that are either declared in the sub itself or in the outer scope of the file.

The "quick fix" would be to move those variable declarations outside the loops. However, as choroba said, the preferred solution is to pass everything that is needed into the sub.

In this case, it is not clear why %rtoa and @alljobs need to exist outside of runsingle. I would declare them there, then pass them in to printjob by reference:

sub runsingle {
my %rtoa;
my @alljobs;   
... some code that actually populates the declared variables...
printjob($fh,$h,\@foo,\%rtoa,\@alljobs);
...
}

sub printjob {
    my $fh=$_[0];
    my $h=$_[1];
    my $keys = $_[2];
    my $rtoa = $_[3];
    my $alljobs $_[4];

    foreach my $key (@{$keys})
    {
        ...
[download]

Also, the new style of filehandles is to use lexical variables directly. This eliminates the need for \*OUT:

    open my $out_file, '>', 'filename.txt' or die "Ouch, $!";
[download]