In
657782070-1374708772-cardhu_decombobulator_blackberry.rim.net-1833732610-@b28.c1.bise6.blackberry,
on 07/24/2013
at 11:32 PM, Ted MacNEIL eamacn...@yahoo.ca said:
Yes, but the article blames COBOL.
There are two kinds of fools:
For large values of two.
3. Those who say this is old,
In ce167d3d.ad740%gary.shimin...@doit.nh.gov, on 07/25/2013
at 11:20 AM, Shiminsky, Gary gary.shimin...@doit.nh.gov said:
COBOL is not at fault in this issue. It is incompetence.
It is institutional contempt for low ranking soldiers. I guaranty that
if the chairman of the chief joints had
In 51f16d8d.5070...@valley.net, on 07/25/2013
at 02:25 PM, Gerhard Postpischil gerh...@valley.net said:
And some happened due to C.E. errors - in the seventies we had an
extra 2MiB of slow memory on one machine, but the C.E. forgot to
enable memory protection, so any errant program could
On 07/26/2013 08:34 AM, Shmuel Metz (Seymour J.) wrote:
In ce16e718.ad880%gary.shimin...@doit.nh.gov, on 07/25/2013
at 06:36 PM, Shiminsky, Gary gary.shimin...@doit.nh.gov said:
When I was in the Army in Korea we ran on Univac 1004 card
processors.
ITYM 1005.
Occasionally the
Shmuel,
My Dad serviced them for a long time among other systems
Scott ford
www.identityforge.com
from my IPAD
'Infinite wisdom through infinite means'
On Jul 26, 2013, at 9:34 AM, Shmuel Metz (Seymour J.)
shmuel+...@patriot.net wrote:
In ce16e718.ad880%gary.shimin...@doit.nh.gov, on
In 51f28f5e.8080...@acm.org, on 07/26/2013
at 10:01 AM, Joel C. Ewing jcew...@acm.org said:
But according to wikipedia, one of the commonly-used plugboard
programs for the Univac 1004 was an emulator that allowed you
to read and store a program from cards that was then executed.
Apparently
On Wed, 24 Jul 2013 16:34:50 -0400, Phil Smith III li...@akphs.com wrote:
So the reason the payroll system is broken is because COBOL is �old�?
No, the payroll system is broken because the documentation is lost, the code is
corrupt and 7mio+ lines of code have not been updated in 20+ years...
-MAIN@LISTSERV.UA.EDU
Subject: Blame the COBOL, how cliché
http://preview.reuters.com/2013/7/9/wounded-in-battle-stiffed-by-the-penta
go
n
So the reason the payroll system is broken is because COBOL is ³old²?
Sheesh. That¹s really weakŠ
Oy, and they tried PeopleSoft as a replacementŠ
Shiminsky, Gary wrote:
The excuse that some of the COBOL code was corrupted is stupid. Really, has
anyone ever seen decay or rust in any code?
Hmmm, after scanning my ancient COBOL progs, they're still rust free! ;-)
HSM can do wonders to package your libraries in rust-free migrated
IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU wrote on
07/24/2013 10:48:55 PM:
From: scott svet...@ameritech.net
The problem isn't the code, it's 1) The documentation for it -
explaining how it was built, what was in it, and how it works -
disappeared long ago. 2) Significant
the COBOL, how cliché
http://preview.reuters.com/2013/7/9/wounded-in-battle-stiffed-by-the-penta
go
n
So the reason the payroll system is broken is because COBOL is ³old²?
Sheesh. That¹s really weak?
Oy, and they tried PeopleSoft as a replacement
IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU wrote on
07/25/2013 12:24:26 PM:
From: Frank Swarbrick frank.swarbr...@yahoo.com
I wonder, exactly, how code is corrupted. Does it start fading
away as it ages? :-(
While we cannot read the mind of the author of that statement, code
On 7/25/2013 11:53 AM, Kirk Talman wrote:
Every bug I have ever seen has been actually some programmer's
mistake.
Then you just haven't been around long enough g Back in the fifties
and sixties, plenty of failures occurred due to machine errors.
And some happened due to C.E. errors - in
: Gerhard Postpischil gerh...@valley.net
Reply-To: IBM List IBM-MAIN@LISTSERV.UA.EDU
Date: Thursday, July 25, 2013 2:25 PM
To: IBM List IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Blame the COBOL, how cliché
On 7/25/2013 11:53 AM, Kirk Talman wrote:
Every bug I have ever seen has been actually some
http://preview.reuters.com/2013/7/9/wounded-in-battle-stiffed-by-the-pentago
n
So the reason the payroll system is broken is because COBOL is old?
Sheesh. Thats really weak
Oy, and they tried PeopleSoft as a replacement
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Phil Smith III
Sent: Wednesday, July 24, 2013 2:35 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Blame the COBOL, how cliché
http://preview.reuters.com/2013/7/9/wounded-in-battle-stiffed
: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
Date: Wed, 24 Jul 2013 21:54:10
To: IBM-MAIN@LISTSERV.UA.EDU
Reply-To: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Blame the COBOL, how cliché
Hmm. In 1988 my military pay got messed up and it took more
Discussion List IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Blame the COBOL, how cliché
Hmm. In 1988 my military pay got messed up and it took more than a year
and several letters to my congressman before it finally got resolved. It's
not the COBOL that's at issue; it's the incompatible systems
Discussion List IBM-MAIN@LISTSERV.UA.EDU
Date: Wed, 24 Jul 2013 21:54:10
To: IBM-MAIN@LISTSERV.UA.EDU
Reply-To: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Blame the COBOL, how cliché
Hmm. In 1988 my military pay got messed up and it took more than a year
The problem isn't the code, it's 1) The documentation for it -
explaining how it was built, what was in it, and how it works -
disappeared long ago. 2) Significant parts of the code have been
“corrupted.” 3) “As time passes, the pool of COBOL expertise dwindles.”
4) The political will and
20 matches
Mail list logo
