Hi Paul,

On Thu 2037-Jun-11 15:49, Paul Quinn (3:640/384) wrote to Richard Webb:

PQ> On 11 Jun 09 15:29, I wrote to you:

 PQ> You could do it this way:

 PQ> [ ... ]
 PQ> find /v /c "39f2dbb9" lognum.txt | nset /L2 lognum=$3
 PQ> [ ... ]

PQ> Mmm... I might have outsmarted myself there.  Which file are you
PQ> counting lines in, again?  :)

cOunting lines in the input file, lognum.sem was just where
we stowed a pointer i.e. the asterisk.

wHen we get the file from alternate source, first step is
edit out all the internet header and mime junk.  tHen a few
edits to clean up whatever search/replace automation didn't
clean up.  Makes one entry per line.
THen, when we exit qedit the main batch is created which
invokes our reconciliation batch I posted for each line of
the input file.

sO, if our first line of the file is:

06/06/2009 22:08 KJ4IXK KI4MMZ 30-14.9N 080-54.7W5 025 Charlston SC ETA 34 Hrs.

we're using first four "words on that line to stuff into the batch we
create, invoking poastrec.bat as follows:

call postrec.bat KJ4IXK 06/06/2009 22:08  KI4MMZ

OF course, HOrst's listmod helps us create this master batch .
SO, this is first line, so we're stuffing a * in lognum.sem
to indicate that this is line 1 of input file.  IN this way, line we're
processing is always correct.

Regards,
           Richard
--- timEd 1.10.y2k+