At first glance:-

• $parseblast1 should be $parseblast[1]

• $parseblast{0} should be $parseblast[0]

• $ARGV1 should be $ARGV[1]

• $assemblast1 should be $assemblast[1]

• [doc://each] returns key <b>and</b> value, I suspect you might need [doc://keys]

• each(%assemblast) should be each(%assem)

Further points:-

• You should indent your code to make it easier to determine the logic employed.

• Use the three-argument from of open, lexical file handles and check for success, e.g. open my $fh, '<', '/path/to/file' or die "open failed: $!\n";

They may be other problems but clear up the ones above and the debugging task will get smaller.

Update: OP added code tags, fixed some of the subscripting problems and indented code while I was posting so much of my advice is moot.

---

---

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.