Re: High S/Gs

[Harry Binswanger hb@xxxxxxxx]

Carl,
> There are three obvious possibilities: error in the parent routine,
> error in the daughter routine, or 102 overwritten by a third XPL
> program.
Thanks for confirming my understanding of how high S/Gs ought to work. Thus
emboldened, I dug in and found the error (in the daughter routine).
And would you comment on my underlying strategy? I'm running 4 programs in
succession, some of which are memory hogs. I had my first OOM problem a
couple of days ago. I used to run them in a chain: 1.pgm ends with BX run
2.pgmQ2 and and so on. To release memory, my strategy now is to have one
master program that, along with other bells and whistles, has:

BXrun 1.pgmQ2
BXrun 2.pgmQ2
BXrun 3.pgmQ2
BXrun 4.pgmQ2
The theory is that each program will release its S/Gs when it returns to
the parent program (except for 1 or 2 S/Gs that are numbered over 99).
Is this a good way to go? I tried Clrsgt and U2s KillMem and Remove, but
had problems.

Thanks,
Harry

Harry Binswanger
hb@xxxxxxxx