From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!JPL-VLSI.ARPA!larry
From: larry@JPL-VLSI.ARPA.UUCP
Newsgroups: comp.lang.ada
Subject: RE: Ada for IBM mainframes under VM/CMS
Message-ID: <870311220037.03t@Jpl-VLSI.ARPA>
Date: Thu, 12-Mar-87 01:00:36 EST
Article-I.D.: Jpl-VLSI.870311220037.03t
Posted: Thu Mar 12 01:00:36 1987
Date-Received: Sat, 14-Mar-87 15:35:09 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
List-Id: <comp.lang.ada>

There is a third validated Ada compiler that produces code for the IBM 370
family: Alsys on ATs and Suns.  Currently the code can only be uploaded 
and run under VM/CMS but Alsys claims they're working on an MVS version.
This is a very cheap way to get started producing Ada code for IBM mainframes, 
but I'd guess that it's only workable for small programs, possibly medium-sized 
ones.  Continuously sending large binary programs over a comm link for test 
runs has obvious problems.

I don't know if the Alsys system allows you to compile and use a linker on 
the mainframe to produce executable code.  If so, and the resulting code is 
of reasonable efficiency, you may be able to use this for large programs.  
However, unless you are very careful, you'll eventually end up spending more 
money trying to do it cheaply than if you spring for a mainframe Ada 
compilation system in the first place.  And if you have several people working 
on a large program the version control and other coordination tools on the 
mainframe will soon pay you back, in saved time and headaches, the high cost 
of the compiler.
                                     Larry @ jpl-vlsi.arpa