Passing in a shell variable to AWK program used as a match pattern

I have a need to get the backlog message of a shareplex replicaton queue based on the queue name, I am not aware that there is a simple command in SharePlex to do it. So I developed a script. I have learned how to pass in a shell variable to the AWK program. This variable will thus be used as a match pattern in the AWK program.

The outoput of the SharePlex command I know to show the backlog messages looks like:

$ sp_ctrl qstatus on myhostname

Queues Statistics for myhostname
  Name:  QueueD (o.prddb-o.rptdb) (MTPost queue)
    Number of messages:      11825 (Age         7 min; Size      21547 mb)
    Backlog (messages):        126 (Age         0 min)

  Name:  QueueA (o.prddb-o.rptdb) (MTPost queue)
    Number of messages:     809345 (Age        48 min; Size     414840 mb)
    Backlog (messages):     806421 (Age        44 min)

  Name:  QueueB (o.prddb-o.rptdb) (MTPost queue)
    Number of messages:      49512 (Age       158 min; Size      71059 mb)
    Backlog (messages):      14425 (Age         4 min)

  Name:  QueueC (o.prddb-o.rptdb) (MTPost queue)
    Number of messages:       9678 (Age         8 min; Size     129632 mb)
    Backlog (messages):        155 (Age         0 min)

  Name:  QueueE (o.prddb-o.rptdb) (MTPost queue)
    Number of messages:          2 (Age         0 min; Size      28042 mb)
    Backlog (messages):          0 (Age         0 min)

My script:

----- script backlog_q.sh -------
#!/bin/ksh
# script bakclog_q.sh
# display backlog of a queuue

qname="QueueB"
sp_ctrl qstatus on myhostname  /usr/xpg4/bin/awk -v pat="$qname" '
begin
{
   if ( $0 ~ pat ) {
     getline
     getline
     print $3
   }
}'  read backlog

echo $backlog

---- end of the script --------

AWK script to analyze statspack report

I have written a small awk script to help to analyze statspack report. The content of the script is as follows:

.

The content of the script is as follows:

$ cat printload.awk
{
  if ( $0 ~ /Load Profile/ ) {
     print "===>"  FILENAME
     print $0
     getline
     print $0
     getline
     print $0
     getline
     print $0
     getline
     print $0
   }
}


Here is an example of its usage:

$ awk -f printload.awk *_1114*.lst

===>sp_P1ROCCS_1114_00:00_01:00.lst
Load Profile
~~~~~~~~~~~~                            Per Second       Per Transaction
                                   ---------------       ---------------
                  Redo size:           -530,710.25        -39,825,381.33
              Logical reads:              5,346.96            401,244.58
===>sp_P1ROCCS_1114_01:00_02:00.lst
Load Profile
~~~~~~~~~~~~                            Per Second       Per Transaction
                                   ---------------       ---------------
                  Redo size:            661,687.44         62,668,765.37
              Logical reads:              5,337.23            505,492.05
===>sp_P1ROCCS_1114_04:00_05:00.lst
Load Profile
~~~~~~~~~~~~                            Per Second       Per Transaction
                                   ---------------       ---------------
                  Redo size:           -261,353.97            -16,558.50
              Logical reads:             34,913.84              2,212.02
===>sp_P1ROCCS_1114_05:00_06:00.lst
Load Profile
~~~~~~~~~~~~                            Per Second       Per Transaction
                                   ---------------       ---------------
                  Redo size:            679,480.45            635,181.85
              Logical reads:              9,648.79              9,019.74
===>sp_P1ROCCS_1114_06:00_07:00.lst
Load Profile
~~~~~~~~~~~~                            Per Second       Per Transaction
                                   ---------------       ---------------
                  Redo size:           -531,582.88        -11,387,897.48
              Logical reads:              7,055.82            151,154.21
===>sp_P1ROCCS_1114_07:00_08:00.lst
Load Profile
~~~~~~~~~~~~                            Per Second       Per Transaction
                                   ---------------       ---------------
                  Redo size:            632,586.85         26,531,869.35
              Logical reads:              6,800.79            285,237.83
===>sp_P1ROCCS_1114_08:00_09:00.lst
Load Profile
~~~~~~~~~~~~                            Per Second       Per Transaction
                                   ---------------       ---------------
                  Redo size:           -535,177.88        -18,857,150.16
              Logical reads:              6,451.35            227,315.36
===>sp_P1ROCCS_1114_09:00_10:00.lst
Load Profile
~~~~~~~~~~~~                            Per Second       Per Transaction
                                   ---------------       ---------------
                  Redo size:            657,449.22         15,364,673.58
              Logical reads:              5,490.71            128,318.66
===>sp_P1ROCCS_1114_10:00_11:00.lst
Load Profile
~~~~~~~~~~~~                            Per Second       Per Transaction
                                   ---------------       ---------------
                  Redo size:            542,321.35            648,839.10
              Logical reads:             14,599.49             17,466.99
===>sp_P1ROCCS_1114_11:00_12:03.lst
Load Profile
~~~~~~~~~~~~                            Per Second       Per Transaction
                                   ---------------       ---------------
                  Redo size:            268,331.93            319,353.99
              Logical reads:             19,272.63             22,937.23
===>sp_P1ROCCS_1114_12:03_13:07.lst
Load Profile
~~~~~~~~~~~~                            Per Second       Per Transaction
                                   ---------------       ---------------
                  Redo size:            316,435.43            342,552.49
              Logical reads:             22,151.92             23,980.23
===>sp_P1ROCCS_1114_14:00_15:00.lst
Load Profile
~~~~~~~~~~~~                            Per Second       Per Transaction
                                   ---------------       ---------------
                  Redo size:            149,285.73            391,643.98
              Logical reads:              6,620.19             17,367.75
===>sp_P1ROCCS_1114_15:00_16:00.lst
Load Profile
~~~~~~~~~~~~                            Per Second       Per Transaction
                                   ---------------       ---------------
                  Redo size:            158,509.15            256,437.01
              Logical reads:              7,857.87             12,712.51
===>sp_P1ROCCS_1114_16:00_16:58.lst
Load Profile
~~~~~~~~~~~~                            Per Second       Per Transaction
                                   ---------------       ---------------
                  Redo size:            197,935.84            243,677.31
              Logical reads:             10,099.65             12,433.60
===>sp_P1ROCCS_1114_16:58_17:00.lst
Load Profile
~~~~~~~~~~~~                            Per Second       Per Transaction
                                   ---------------       ---------------
                  Redo size:            799,700.92            948,216.80
              Logical reads:             37,202.29             44,111.29
===>sp_P1ROCCS_1114_17:00_18:00.lst
Load Profile
~~~~~~~~~~~~                            Per Second       Per Transaction
                                   ---------------       ---------------
                  Redo size:            541,252.15            441,183.58
              Logical reads:             26,538.76             21,632.18

I know under cygwin I can use grep -A option to achieve same goal.
I can do something as follows:
grep -A5 "Load Profile" *_1114*.lst

Note:
-A NUM, --after-context=NUM
Print NUM lines of trailing context after matching lines. Places a line
containing -- between contiguous groups of matches.

However, the version of grep on our server does not have this option.