Re: High S/Gs

[Carl Distefano cld@xxxxxxxx]

Reply to note from Harry Binswanger  Fri, 03 Sep
2010 11:04:30 -0400

Harry:

> >In your example, 1.PGM, 2.PGM, 3.PGM, and 4.PGM. The idea is
> instead >of running them from a "master" program, you run them
> individually, >one at a time.
>
> I can do that manually, by entering each on the command line

Right. That's the idea.

> but I'd like to automate this, since I do it 6 days a week,
> year in and year out. If I just chain them, I guess each,
> ancestor is still running when the descendant is called:

Yes. That was the gist of the demo I posted yesterday. But you *can*
automate the separate RUN commands, of course. Here's a demo frame.

XPLeNCODE v2.0
b-gin [UNTITLED]
{{;5run4}} Command RUN4 repeatedly to run demo[cr|lf
]{002}{<}IF{<}VA!100{>}<>4{>}{<}SX100,0{>}{<}EI{>}{<}IF{<}PV1
00{>}>3{>}{<}SX100,0{>}{<}EI{>};*;[cr|lf]{<}SX100,{<}PV100{>}
+1{>}[BC_]run {<}PV100{>}.PGM[DO_][FF_][BX_]p[Q2_][BC_]run4{0
02}[cr|lf][cr|lf]
-nd
XPLeNCODE

(To make the above operational, delete "DO FF BX pQ2 " and insert
"XC " in its place.)

> What I'm doing now, with a parent program and daughter programs
> does seem to be working, probably because of the re-using of
> S/G numbers involved.

Well, that's good, then. If you run into trouble again, you'll have
some arrows in your quiver.

--
Carl Distefano
cld@xxxxxxxx