Quote:
Originally Posted by KaleunMarco
not really....an OC7 would generate a foot-high stack of greenbar dump to peruse so that you could actually figure out what went wrong and then fix it and code for the event, should it happen again.
a CTD does nothing of the kind...just leaves you guessing. stupid MS programming technique.
|
And having "learned" programming on Assembler-F, I knew how to read those dumps. That's why when I compiled the "last" version of a COBOL program I included a Dmap and a Pmap to make it easier to plow through those stacks of green bar. And you are right - it was much better than a simple CTD. A real issue could be found and fixed.
One could force an 0C7 as a debug tool by setting up a packed numeric field in storage, redefining it as an Alpha field, and giving it a value of "A". Adding a value of +1 to the Numeric field name would give you an instant 0C7. I got creative once and gave the fields strange names: A field in storage with a constant value of +1 was called "Who-knows-what-evil-lurks", and the redefining Alpha field was named "The-Shadow-Knows". So when I added "Who-knows-what-evil-lurks" to "The-Shadow-Knows" I would get an instant 0C7 from a predictable source. Silly, but fun.
At least it was fun until I had pulled two straight all-nighters on the launch of huge new production system and the Director of Development and his deputy were filling in and trying to debug a production program with said code in it. The deputy almost got fired when he read that source code out loud! Would have been funnier if they hadn't called me out of near-coma to explain the code...
