%hash only has one key (how useless!), so

@HoH{keys %hash} = values %hash
is the same as
$HoH{$unit_num} = $hash{$unit_num};

As you can clearly see now, you completely replace all existing data for $unit_num every time you find a new record for $unit_num.

Change

%hash = ( $unit_num => { $event_nm => [ $event_date ], }, ); @HoH{keys %hash} = values %hash
to
push @{ $HoH{$unit_num}{$event_nm} }, $event_date
Thanks to autovivification, the above is short for
$HoH{$unit_num} ||= {}; $HoH{$unit_num}{$event_nm} ||= []; push @{ $HoH{$unit_num}{$event_nm} }, $event_date;

Tip: Don't pass hashes and arrays to Dumper. Pass references to them:

print Dumper( \%HoH );

In reply to Re: Using a hash to store complex data by ikegami
in thread Using a hash to store complex data by TJRandall

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.