Talk:NonStop (server computers)

Computing Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by Computer hardware task force (assessed as Low-importance).

Relation to the Category:Computer architecture

Is not clear after reading first paragraph of the article.

Category:Hewlett-Packard products is a correct category; but NonStop (server computers) is not about Computer architecture. Ushkin N (talk) 20:23, 27 July 2016 (UTC)[reply]

incorrect, this is an architecture.

93.104.187.215 (talk) 02:09, 23 January 2018 (UTC)[reply]

Agreed, NonStop is a very unique architecture, but it is indeed a systems architecture concept. How this isn't apparent is beyond me.

And what is up with "citations needed" for customers and applications? That paragraph is a subset, but accurate. The worst application I had ever seen for one was the GTEL NM&C central office software which we had at a military site processing CDR, trouble tickets, and service orders, for/from a NorTel Meridian SL-100 (DMS-100 with PBX functionality) on the Tandem ETX-10. Tom had told that team the VAX->Tandem porting effort would be a failure, Tom having been on the original team (later Sprint Lenexa LDD OSSC). The SeaBees and NSWSES/NSWC-WD had to wait five years AFTER DELIVERY to have it working properly. Interesting that my DOS directory assistance program actually lasted that long...wrote it in a 48 hour Jolt-fueled session, and had it delivered the day of cut-over from the 1944 step-by-step that the '100 replaced.

On the other hand I know of a similar Tandem at a bank in OK that had 30+ year uptime.

GIGO applies, as always.

Here is something I wrote yesterday concerning Tandem: "There is an interesting story about the global economy being saved by a golf match between a cool Irish guy, Tandem, and SGI. Tandem would have had to liquidate, had the Sprint Merged Call Processor (MCP) not happened the way it did. Tandem logo, SGI 12 CPU MIPS iron, Tandem HA under Irix, every switch site, plus Lenexa (directly across from the VAX-7000). If Tandem had failed then, it would have triggered a minimum of a recession...quite possibly a depression. NonStop didn't mean "without maintenance", and Tandem ran the world. Although the MCP didn't require 6530s, the point on Tandem's importance stands. Guardian NonStop ran so much of the world's economy...still does, I'd bet.". (I was on the MCP programming team, 9300 Metcalfe)

73.217.28.14 (talk) 16:35, 22 January 2024 (UTC)[reply]

Lack of content

This article is a disgrace. Citations are are the one thing that it is already flagged for, but this is the far smaller problem. i've never gotten closer than a few footsteps and a glass wall to those systems, but it is beyond doubt one of the holy grails of specialized highly available systems. This is the kind of system you want to rely on if "oh but the cloud failure even affected netflix" is *not* going to get you a free pass. Like those shops that need to notify governments if they got a larger-than-1-minute outage. The fact that this is excellently solved by a 1970s architecture is something to be aware of, and remember, as we try to solve todays more facetted "everyday" issues.

93.104.187.215 (talk) 02:08, 23 January 2018 (UTC)[reply]

Agreed, this article needs expanded. Tandem's importance cannot be understated. IBM has only RECENTLY announced similar FT capabilities...

If you need true fault-tolerance, you can have a one-off or low production volume Frankenputer or Tandem, these are the traditional choices...the former having questionable properties, the latter being stable, mature, extensive support, and decades-uptime proven.

If your bill has a faulty transaction record, that's GIGO, not Guardian...

Still, this article reads like a Christian home-schooler's book report, instead of a discussion of the architecture that makes it unique. My experience is on an old 16 bit ETX-10 mini (hands-on) and FTAM to/from remote Cyclones gathering CDR from all of Sprint's switches in realtime. I am not the best person to write it, and I have too much going on right now with Desktop Cyber to do a deep dive to write a Tandem article. Maybe someone in the Tandem community could oblige? It is a large community.

73.217.28.14 (talk) 16:56, 22 January 2024 (UTC)[reply]

A Commons file used on this page or its Wikidata item has been nominated for speedy deletion

The following Wikimedia Commons file used on this page or its Wikidata item has been nominated for speedy deletion:

HPE NonStop Server.jpg

You can see the reason for deletion at the file description page linked above. —Community Tech bot (talk) 12:22, 19 February 2022 (UTC)[reply]

A Commons file used on this page or its Wikidata item has been nominated for deletion

The following Wikimedia Commons file used on this page or its Wikidata item has been nominated for deletion:

HPE NonStop Server.jpg

Participate in the deletion discussion at the nomination page. —Community Tech bot (talk) 02:22, 20 February 2022 (UTC)[reply]

Picture

The picture isn't of a NonStop server. You can clearly see in the picture that there are some Nimble arrays in the rack and the rest of the rack is empty, populated with blanks in front. You can see the bezels of the devices says, Nimble Storage. I thought photography was prohibited in HPE labs, as well? If you compare this photo with the photo Countercheck keeps adding, you will see they are the same.—Kjsehyrt (talk) 07:35, 28 October 2023 (UTC)[reply]