Replacement of HP Non Stop Tandem

[dwived...@gmail.com]

What could be the best possible target system if someone wants to move out from HP Non Stop Tandem.

Quick response will be appreciated.

Thanks
Sujit

[red floyd]

The quick response is, "it depends upon your requirements".

That sort of migration is not one where you make snap decisions.

[dwived...@gmail.com]

This one is about few Cobol programs running on HP Blade System. Since its limited to the programs..looking for replacement to the new system which will be cost effective as compared to NS Tandem.

Looking for suggestions for new system where we can do the transition of the cobol programs and get the same outcome.

[red floyd]

On 5/10/2017 1:45 PM, dwived...@gmail.com wrote:
>
>
> This one is about few Cobol programs running on HP Blade System. Since its limited to the programs..looking for replacement to the new system which will be cost effective as compared to NS Tandem.
>
> Looking for suggestions for new system where we can do the transition of the cobol programs and get the same outcome.
>

And again, that kind of migration is not one where you make snap
decisions ("Quick response will be appreciated").

[dwived...@gmail.com]

Seems quick reponse made my question wrong :)

Looking for answer if someone plan to opt out HP NS Tandem, what would be the best possible target system where we can host/transform existing programs into the new system.

Thanks
Sujit

[wbreidbach]

If you want to use COBOL with Linux you do not have many choices concerning compilers and as far as I know those compilers are not cheap at all. Usually the license costs depend on the hardware the compiler is installed on. That means, if you install you Linux on a box with 20 cores you have to pay for the 20 cores even if the whole thing is virtualized and you are only using 1 core for the application. And if you are using Pathway on the NonStop ... good luck! And if you really find something verify that there is support available!

[Pierre]

My suggestion from HP Non Stop Tandem is moving to a HPE NonStop ;-) And it also a quick move!!

[Randall]

Moving off "Tandem" can be problematic. The operational discipline and capabilities of the HPE NonStop are not easily reproduced on other platforms. If you look at cost of ownership, you will find that competitor production Linux database licenses can exceed the entire cost of the NonStop platform (hardware and software) and you won't get the same performance at the high-end database sizes. Many companies have tried and died making this move. Few have succeeded.

Cheers,
Randall
P.S. I am not an HPE employee or contractor.

[Bruce Holenstein]

Dear Sujit,
The “HP Non Stop Tandem” system that you are using is likely very old. You should consider migrating to a brand new HPE NonStop system. The Total Cost of Ownership includes hardware and software licensing costs. Yet, ongoing personnel costs often dwarf the HW and SW costs in the TCO. A small NonStop system may be managed part-time by a single individual. But, the corresponding Unix or Win system likely will take multiple Ops/DBAs and be off-line for updates hours or days per year. Then there are the costs of unplanned outages which drive away customers. Give your HPE sales team a call.
Kind regards,
Bruce H

[Henrik Paludan-Mørk]

How many programs, what data storage facility (sql or flat files)?
how much data?
how many screens?
how well documented?
is business knowledge at hand?

all this goes into the equation. generally you face 3 options:

- total manual rewrite (expensive, slow, risky)
- re-hosting, where you recompile the code on a different platform.
to my knowledge, not existing for tandem/hp ns. sorry!
- generative rewrite - analyze/generating into terrible java code - hit and run by indian consulting firms. VERY dangerous.

none of them are great. they are all terrible. looking for the "best" exposes your lack of experience. there is no best, just the one with the seemingly smallest downsides.

[Dave]

On Wednesday, May 10, 2017 at 3:55:51 PM UTC-4, dwived...@gmail.com wrote:

You might take a look at going virtual: https://www.hpe.com/us/en/product-catalog/detail/pip.hpe-virtualized-nonstop-software.1009703816.html

[hamm...@gmail.com]

short answer: most companies move to MicroFocus on Linux.
Fortunately, plain COBOL is very portable.

[Henrik Paludan-Mørk]

You clearly have not seen tandem cobol applications. Your answer is generic and therefore outright dangerous to follow.

[Randall]

NonStop COBOL supports ENSCRIBE structured files, SQL/MP, SQL/MX, not to mention "ENTER TAL" constructs. The same comment can be made about C, which is easily as portable, but the library calls are not guaranteed. Just because a language is portable does not mean that the program is.

Cheers,
Randall

[wbreidbach]

As far as I know MicroFocus Cobol is pretty expensive and from the experiences of other companies moving to Unix/linux from NonStop will not save any money. You need more patching, move service, more people and so on and from what I know you would not even save license costs.

[Pranas Baliuka]

If it's well documented transaction processing in 21st century is not very expensive exercise with modern technologies e.g. https://nuodb.com/ just to mention one reasonable of alternatives.
BUT nobody talked about requirements and documentation 30+ years ago only IBM consultants ...

[Willie Whittaker is a Putin Cock Sucker <NoEmail@void.net>]

There is no such thing as

HP Non Stop Tandem


Those disappeared in 1995 .

Everything HP touches DIED .

Maybe the mgtment went to Trump Univ