Slashdot Mirror

← Back to Stories (view on slashdot.org)

Gnarly Error Messages

Posted by michael on from the abnormal-termination dept.

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."

2 of 1,218 comments (clear)

  1. Use Of Gnarly not giving credit! by DrPascal · · Score: 0, Troll

    The correct headline should be written as:

    GNU/Gnarly Error Messages?

    Come on people...

    -1 Flamebait, +1 Lame, +1 Funny = +2! Not bad.

    --
    DrPascal: Not the language, the mathematician.
  2. Re:error message by cygnus · · Score: 1, Troll
    "You need help. Please call 1-800-xxx-xxxx for assistance."
    do you get that one if you're horny?

    ... get caught watching too much of the Spice channel?

    --
    Just raise the taxes on crack.