In a previous life, I wrappered CMSSTOR in a pair of C funcs: xxx_malloc() and xxx_free() or some such ... but am going by memory. Whatever C runtime I was using at the time had its own malloc() and free() functions, which were also used, and I did not want to interfere with them. But I could use the custom wrappers when requiring CMS-specific chunks of storage, outside of control of the runtime.
This is probably only tangential to your work, Dave, becaues you are *inventing* a C runtime. I was having to code around one. It is exciting to think of thin shim wrappers around the native CMS functions, especially the LE and BPX suite. I think you'll get a lot of mileage out of that. -- R;
