My first impulse would be to call that subroutine 3 times in one run: 
if ( $page eq 'x1a.html' ) {
    $re_type = "a2";
    $Q = ($prod) ? 'a0' : 'a0';
    $send=$sec.$account.$year.$view;
    got_send();  # first "page"

    $re_type = "x2";
    $Q = ($prod) ? 'p0' : 'w0';
    $send=$sec.$account.$year.$view;
    got_send();  # second "page"

    $req_type = "y1";
    $Q = ($prod) ? 'p0' : 'w0';
    $send=$sec.$account.$year.$view.$action;
    got_send();  # third "page"
}

[download]
(That's the "quickest" thing, though some rearrangement -- possibly using a loop over a data structure of call parameters -- would be worthwhile.)

But I suppose there might be something you haven't shown us in your "got_send()" sub that makes this impractical?

The way out would be to refactor the "got_send" sub to make it more modular: pass parameters to it on each call, instead of having it refer to global variables; have it return a string (or something), which the caller will know what to do with, based on the caller's knowledge of the context for each call, rather than trying to do everything inside of "got_send()".

Perhaps I'm misunderstanding the question? Or maybe you've left out some useful details...

In reply to Re: Combining calls to a subroutine issue. by graff
in thread Combining calls to a subroutine issue. by Anonymous Monk

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.