Gnarly Error Messages
Veeru writes "In my career, I have run across some whopper error messages, but a call from the mainframe sysop one night beat them all: 'We are experiencing MVS processor spin loops, the programs are running while holding a disabled CPU. This is causing XCF communication delays to the point where we are losing VTAM RTP routing, are suffering OSPF adjacency failures on TCP/IP dynamic routing and MIM VCF failures. Whatever this code is, it should NOT be propagated to production or we run the risk of losing the development plex if XCF signaling is adversely impacted by processor disabled spin loops'. My friend once got an error message 'Error 2 while trying to report error 2'. I would be curious to hear from the Slashdot community on encounters with other bizarre error messages."
Anybody that's used C++ templates a lot would know that compile errors can easily be 10-20 lines long (per error).
I don't remember who said it, but C++ templates are clearly the work of the devil.
Yep. You gotta love people who either a) mess with things they don't understand or b) deliberately try to break things...and then find that they're broken.
Granted, there exists an argument that even when apparently working correctly most MS products are badly broken, but that's for another post...
~Idarubicin
Changing a bunch of configuration settings in a GUI should not be something that's unrecoverable through normal, documented means.