Migrating from Tandem Cobol to IBM Cobol for OS/390 & VM
Robert M. Pritchett
have mostly IBM mainframe including Cobol/390, plus lots of other mini
Cobols, and we have almost 20 people; I'd love to help.
Robert M. Pritchett, President - RMP Consulting Partners LLC
http://rmpcp.com - rm...@pobox.com - Dallas, TX - Member ICCA
"Quality means doing it right the first time!"
Craig Harris wrote in message <370CC491...@dcn.davis.ca.us>...
>I am looking for information about migrating a financial application from
Tandem Cobol to Cobol for OS/390 and VM. Y2K compliance is not part of the
migration. I think it is Tandems ANSI85 and SCOBOL (Screen Cobol) on the
workstations.
>Replies here or to my personal id ok.
>Craig Harris cha...@dcn.davis.ca.us
>
>
Don Nelson
>
> I have some Tandem Cobol exposure (VisCobol)
There never has been a Tandem COBOL with that name. There was COBOL
74, COBOL85, and NMCOBOL. SCOBOL (or Screen COBOL) is a special case
and is like the screen section in other cobols with limited procedure
division stuff.
--
Don Nelson
COBOL Development, Compaq Computer Corp.
Member, NCITS J4 and ISO/IEC JTC1/SC22 WG4 COBOL Committees
don.n...@compaq.com
No clever quotes here
Robert M. Pritchett
or of course, I could've been misunderstood - I wasn't talking about a
Cobol compiler/implementation written by Tandem per se, just one that ran
on one. VISystems developed a CICS-on-Unix type of product with Cobol
compiler, debugger, VISAM, etc. that ran on several Unix platforms
including Tandem (whose Unix implementation didn't seem to really work out,
at least as far as I saw). I suppose for that matter that MicroFocus Cobol
or any other Unix Cobol could've also been ported to Tandem Unix.
Unfortunately, like QuadStar and probably many other firms that didn't care
about their people and their software quality and didn't listen to their
people, VISystems went out of business.
Robert M. Pritchett, President - RMP Consulting Partners LLC
http://rmpcp.com - rm...@pobox.com - Dallas, TX - Member ICCA
"Quality means doing it right the first time!"
See http://www.headhunter.net/jobstv/0j/j04651mjxt8trch80j.htm?ShowJob
Contractors: tired of hearing "W-2 only"? Join us and let us help you get
that same contract on a 1099 as a self-employed independent contractor!
Don Nelson wrote in message <37137E...@compaq.com>...
Don Nelson
>
> Just goes to show what happens when people make blanket generalizations -
> or of course, I could've been misunderstood - I wasn't talking about a
> Cobol compiler/implementation written by Tandem per se, just one that ran
> on one. VISystems developed a CICS-on-Unix type of product with Cobol
> compiler, debugger, VISAM, etc. that ran on several Unix platforms
> including Tandem (whose Unix implementation didn't seem to really work out,
> at least as far as I saw). I suppose for that matter that MicroFocus Cobol
> or any other Unix Cobol could've also been ported to Tandem Unix.
Actually, the generalization was mine - I should have been more
explicit - mea culpa. He was talking about the Tandem (now Compaq)
NSK platform (I know this because he mentioned SCOBOL, which exists
only on NSK). This one never had anything other than Tandem's COBOL.
What you were talking about was the Tandem Unix boxes, which would run
any Unix COBOL, Including Micro Focus. I had nothing to do with those
systems.