Strange, but:

• Your use statements and global (to the component) variable declarations really should go inside a <%once> block.
• Likewise setting $status should be done in an <%init> block.
• It'd be more Masonic to use <% Dumper( $status ) %> rather than printing.
• A better way to wrap components in a header and footer is to use the autohandler mechanism.

<pre>
<% Dumper($status) %>
</pre>
% $status->RetriveBuildStatus('ASA',\%Table);
<%once>
use strict;
use Data::Dumper;
use ASA::UIC_DBSTATUS;

my %Table;
my $status
</%once>
<%init>
$status = ASA::UIC_DBSTATUS->new();
%Table = ();
</%init>
[download]

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.