On Tue, Nov 8, 2022 at 04:52 PM, Harold Grovesteen wrote:
can you help me understand how we ended up with two distinct C runtime environments?
It is the dynamic data, not the code.
- a user "kicks" CMS to start EE, EE initializes its runtime data
- EE calls CMS for macro execution
- CMS sees "/*" and starts bREXX, bREXX initializes its very own runtime data
- the macro wants to execute an EE subcommand, EE had setup itself as subcommand handler before
- CMS calls EE's subcommand handler, but has no knowledge about EE's already existing runtime data
IBM had to solve this problem when they made XEDIT, EXEC 2 did the job on VM/SP 1+2
Martin Scheffler