Upgrade path from IBM's VisualAge Cobol (was withdrawn)
- From: Graham Hobbs <ghobbs@xxxxxxxxxxx>
- Date: Fri, 20 Apr 2007 22:05:31 -0400
Hello
My third post in four days - is all so exciting and most useful.
Am developing a mainframe software package but I cannot make my 1998
Visualage Cobol V2.2 work on my new XP Pro laptop so am trying to find
out what other people in my situation have done.
The Cobol has to support:
a) CICS commands (my IBM CICS for Windows V3.1 seems to work OK on the
new machine)
b) DB2 'Exec SQL' commands (I have the new DB2 Express-C V9.1),
c) the seeming current VSAM KSDS emulator bTrieve commands (read,
write, etc)(seems this is still the way VSAM KSDS is emulated even
today).
Elementary answers I came up with were:
a) Contact IBM: I did; dreadful experience; after two hours of
transfers, redials, new numbers, one person asked me how to spell
'cobol':-(
b) Try Microfocus (after I hear comments of this group).
Cost is an issue (since I'm retired). So I might as well mention that
whatever Cobol solution arrives, I'm gigantically hoping that my old
CICS will work with the Cobol/CICS .exe programs. Hate to think what
a PC CICS would cost...
Any advice very welcome, please, thanks.
Graham Hobbs
--
Posted via a free Usenet account from http://www.teranews.com
.
- Follow-Ups:
- Re: Upgrade path from IBM's VisualAge Cobol (was withdrawn)
- From: William M. Klein
- Re: Upgrade path from IBM's VisualAge Cobol (was withdrawn)
- Prev by Date: Re: VisualAge Cobol Compiler prob on XP Pro
- Next by Date: Re: Upgrade path from IBM's VisualAge Cobol (was withdrawn)
- Previous by thread: Max integer in an 8 byte COMP field?
- Next by thread: Re: Upgrade path from IBM's VisualAge Cobol (was withdrawn)
- Index(es):
Relevant Pages
|