How about running your initialization routine from a job or started task
instead of via SSI
definition? You would need a small driver that calls your init routine
from that job
or STC. You could even write a small program to cleanup the environment
before rerunning
the init job/STC.
Once
Whether your assessment is correct correct upon whether you are
willing to make use of EJ's suggestion that you zap (presumably) the
last letter of your routine's name to employ a sequence
'stem'.'A', 'stem'.'B', . . . . ,'stem.'Z', 'stem.'@',
'stem.'#', 'stem'.'$'
of 29 routine names, one per
At 12:02 -0400 on 04/13/2014, you wrote about Re: Testing (was
'Tesing') A SubSystem Initialization Routi:%0D
I'm not quite sure what Robert Rosenberg means by a 'static location',
but a sequence of directed loads to tghe same reused storage obtained
once dynamically would meet your needs.
