On Sat, 4 May 2024 21:53:59 GMT "esst...@juno.com" wrote:
:>In developing an SSI initialization routine, it would be useful to backout
any changes made.
:>i can release Storage in an ESTAE routine, but I can't "undo' any changes
made using IEFSSI macro -
:>I cant remove the SSVT ect . To me it would be helpful during development
if there was IEFSSI TYPE=BACKOUT,
:>so that any changes made in the SSI initialization routine relating to define
and initializing a subsystem would be backed out.
:>This would also be useful in a ESTAE routine.
:>Also being able to COMMIT the changes might also be useful.
Once you kill the SSVT the subsystem will not affect anything.
There is no way the system can know what your SSI did to be able to back it
out.
If you allocated storage and hung it off of the SSCT, you can free it. You can
hang new storage off of the SSCT. You can reestablish the SSVT.
I believe that you can even change the name in the SSCT w/o bad effects (if
you no longer wish for the SSCT to be matched)
I fail to see a business case for your request.
--
Binyamin Dissen
http://www.dissensoftware.com
Director, Dissen Software, Bar & Grill - Israel
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
