Re: Microfocus COBOL 3.2.43 (16bit)

Tsk tsk... not so. There is such a thing as a virtual machine image that
allows remote access. See for example:
http://www.vmware.com/solutions/desktop/vdi.html. It's even cost effective.

However, a company making that kind of move would probably already have
accounted for this and have a plan in place to deal with it. This smells a
lot like a company wanting to keep that application running for 'just a
little while longer'.

-Paul

"Richard" <riplin@xxxxxxxxxxxx> wrote in message
news:1166670160.307778.99640@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

P. Raulerson wrote:

New PC Hardware: $4K - $11K. Depending upon the needs. $11K = new
dual-core
dual processor IBM LS20 blade with dual fibre connections & eight gigs of
RAM on board.

VM software (Free to about $4K).

NT Software, Compiler, etc. Already in place.

So cost (in the U.S. you are on your own in the U.K.) is anywhere from
$4K
to $15K, a very reasonable cost to extend the life of a critical system.
And
yes, you could host it on a Windows Server or Windows Vista machine
without
any trouble.

It is possible that the application may just be running on a single
machine, the compiler is, but it is likely that the production program
is running on every desktop machine in the company, or a significant
number of them. $15K * several hundreds or thousands of PCs may be a
bit steep.



.

Relevant Pages

  • Re: Microfocus COBOL 3.2.43 (16bit)
    ... dual processor IBM LS20 blade with dual fibre connections & eight gigs of ... RAM on board. ... NT Software, Compiler, etc. ... you could host it on a Windows Server or Windows Vista machine without ...
    (comp.lang.cobol)
  • Re: C4239 - why here?
    ... > void f ... In fact, i would expect the compiler to refuse this outright, it ... like this, tsk, tsk, naughty compiler... ...
    (microsoft.public.dotnet.languages.vc)
  • Re: C4239 - why here?
    ... In fact, i would expect the compiler to refuse this outright, it ... like this, tsk, tsk, naughty compiler... ... to get polymorphic behaviour in F depending on the calling context). ...
    (microsoft.public.dotnet.languages.vc)