On Sat, 12 Feb 2011 00:27:16 +0100, Rob wrote:
>Somehow it sounds like you could do with your detail and master
>reversed and feed the references back in as masters instead, but your
>description is vague enough that one does the design on a beer coaster
Yeah, it's vague because my lookups are actually done not with LOOKUP but
with an external program reading the bizarre, undocumented file format.
The flow is basically like this:
(end /) *: | feedback: elastic | not lookup autoadd
| found: magic file reader | out: fanout | *:
/ found: | *..1:
/ out: | specs ... | feedback:
The magic file reader finds records with the key field matching the
input, and SPECS picks out other fields of the record to feed back as
more keys to match. Then I feed the nonmatches on the alternate output
to the input of the next similar pipeline, and so on.
Oh! Now that I've laid that much out this simply, I think I see what I
need to do. Instead of wrapping the whole cascade inside another ELASTIC
feedback loop like this:
(end /) ... | top: elastic | 1: magicstuff file1 ...
/ 1: | 2: magicstuff file2 ...
/ 2: | 3: magicstuff file3 ...
/ 3: | top:
I can hook the alternate inputs of my REXX stage right back into the
first ELASTIC:
(end /) *: | feedback: elastic | not lookup autoadd
| found: magic file reader | out: fanout | *:
/ found: | *..1:
/ out: | specs ... | alt: faninany | feedback:
/ *..1: | alt:
/ *..2: | alt:
and then for my outer loop I'll just have:
(end /) ... | 1: magicstuff file1 ...
/ 1: | 2: magicstuff file2 ...
/ 2: | 3: magicstuff file3 ...
/ 3: | 1:
¬R "I love Blip just because it's the absolute opposite of fun"
http://users.bestweb.net/~notr/travelog/19990710.html --Kibo
