Re: COBOL Compiler for Windows
- From: Thane <thaneh@xxxxxxxxxxxxxxxxxx>
- Date: Fri, 2 May 2008 13:18:50 -0700 (PDT)
This might be a useful top post reply.
Graham - have you tried right clicking on the setup executable and
setting Windows Compatibility mode to NT?
If it does install but just doesn't work - have you tried right
clicking the Icon that starts it and setting Windows compatibility
mode?
Please let us know here on the newsgroup if this helps.
On Apr 30, 10:30 am, Graham Hobbs <gho...@xxxxxxxxxxx> wrote:
Hello,
Thanks for the responses. Learning all the time.
Not only 'not like the price', 'havent got the money'.
Hercules! For me, a whole new line of research, maybe later.
MF not MS, sorry.
Pete, thanks for the history.
Bill Klein asked for more explanation so ..
Bill,
Am retired so have no EMPLOYER and cost is a serious factor especially
for a project that today might be dubious saleability.
Until a year ago I had an old IBM compiler (VA Cobol V2.2) that runs
on an old laptop under Windows NT plus DB2 V7.2, CICS for Windows 3.1
and VSAM KSDS via Pervasive's bTrieve, all 1990's vintage. On this
laptop I'm developing a software package written in batch Cobol that
generates Cobol/CICS programs (dinosaurial as it may seem, have gone
too far to stop). The package is aimed at any platform that runs CICS,
especially these days it seems, z/OS.
So the V2.2 compiler I have performs two functions, a) compile/produce
executables of the batch pgms of my software, b) compile/produce
executables for the online Cobol/CICS pgms that my software generates.
The old NT laptop grew old, slow and full so I bought a new one. It
won't accept NT so I opted for Windows XP. My CICS and DB2 work fine
thereon. The Cobol fails horribly and no fixes available.
Today the XP laptop has NT running under Microsoft's Virtual PC thus
some of my development can continue on the NT side.
But the ultimate intent is to email pgms between myself and clients.
Technically this must be done on the XP side while compilations etc
must be done on the NT side - is labour intensive and 'almost'
impractical.
Thus the need for a free/cheap XP Cobol compiler that accepts CICS and
DB2 commands and produces working executables - in essence goodbye NT.
As you said mainframe emulators are expensive (unless my government
will give me a grant :-000)))(still choice 1), PWD might be amenable
(choice 2), a Cobol compiler NT to XP fix was available (choice 3),
whatelse?.
So In contacting the group, I am really looking at the 'whatelse'
scenario. Hope that better explains my situation.
Any help appreciated. Thanks
Graham
On Tue, 29 Apr 2008 19:01:56 GMT, "William M. Klein"
<wmkl...@xxxxxxxxxxxxxxxxx> wrote:
There have been lots of replies - with varying levels of "helpfulness".
It would SEEM to me that you are asking for a PC (Windows) based mainframe
emulation environment. These exist but are not cheap. (IBM and Micro Focus
both sell extensive and expensive products for this). However, I am a little
confused as to WHY you would want this. If you want this in order to do Windows
development for applications intended for mainframe deployment, then I would
expect that your mainframe EMPLOYER would provide such tools (and they often can
afford them).
If you are actually trying to develop (or even "play with") programs that are
just intended for the PC/Windows environment, then you are looking for the wrong
tools.
Can you tell us WHY you want DB2, CICS, VSAM support? What do you plan on doing
with this compiler/product? With that information, we may be able to better
help you.
** Posted fromhttp://www.teranews.com**
.
- Follow-Ups:
- Re: COBOL Compiler for Windows
- From: Graham Hobbs
- Re: COBOL Compiler for Windows
- Prev by Date: Re: COBOL Compiler for Windows
- Next by Date: Re: COBOL Compiler for Windows
- Previous by thread: Re: COBOL Compiler for Windows
- Next by thread: Re: COBOL Compiler for Windows
- Index(es):
Relevant Pages
|
