Thanks Chris for answering so many questions. I should have read part 2 before answering part 1.
> Chris Cradock wrote: > I used the z/XDC debugger with c/XDC for the C++ code. I'm still a Dave Cole > fanboy. I couldn't have done it without XDC. Anyone who doesn't express accolades for z/XDC has never used it properly. I couldn't afford it when writing my product which I found traumatizing after using it for so long. You can't say enough good things about z/XDC. > The new "product" is a data server that does z/OS job-monitoring It now makes sense that this isn't actually automation but workload management possibly with scheduling. Very intriguing but a very different concept to automation. > It's safe to say this isn't a typical C++ application. With 40% HLAsm despite C++, it is obviously not a typical application. > It has ECSA control blocks, stacking PCs, RESMGRS, Dynamic Exits, Xmemory > AR-mode etc. For my product, everything privileged occurred during startup with the exception of PC routines. I was forced to use CSA because of 24 bit mode risk but it was only a few hundred bytes. Just needed PC routine number and SSCT entry. Probably unnecessary but I didn't want to risk it for so few bytes. > between the obscurities of C++ classes and the instructions the compiler > emits, I mostly just went "ok, I did the same thing but on Intel and decided it was enough to know it worked. Thanks, Jon.
