wdw@aucs.UUCP (12/04/87)
At Acadia University we are considering a project that would require a
good stable COBOL environment running on the Unix operating system. If
anyone has experience (good or bad) that they would like to share we
would be very appreciative. Please provide specifics as to which COBOL
environment you've tried and on which variant of UNIX it was running.
Thanks very much.
--
UUCP: {uunet|watmath|utai|garfield}!dalcs!aucs!wdw
BITNET: WDW@Acadia
Internet: WDW%Acadia.BITNET@WISCVM.WISC.EDUjal@auspyr.UUCP (Joe Longo) (01/23/88)
John M. Ritter (jmr@motown.Allied.COM) writes:
"I've been trying to find a COBOL compiler for about 2 years to run
on AT&T System V. Unfortunately, there doesn't seem to bee (sic)
such a thing."
Austec has had a COBOL available for System V since early 1985. The
product is called ACECOBOL, is GSA Certified High for Cobol 74 and
generates interpretive code, with an option to compile into native (a.out).
"Next major attempt was with Austec. Same deal -- nothing for System V.
This is the company that bought Ryan-McFarland. Their COBOL
supposedly also runs on BSD and Ultrix. The main problem with the
company is a complete lack of cooperation. ...."
I'm not sure why you had this problem when you called us -- no-one here
recalls talking to Allied Signal, so either that person is gone or you
called a long time ago. When people call and ask about ACECOBOL for
SystemV, they're usually asked to nominate the system they want it on.
ACECOBOL runs on a long list of machines, including
AT&T 3B's, VAX/Ultrix, Gould Powernode, Pyramid, Edge,
Xenix 286, Xenix 386, NCR Tower, IBM 9370/IX370,
etc..
ACECOBOL also runs on VAX/VMS, IBM PC/DOS and Stratus/VOS.
As well as that, it has a number of networking capabilities that make it
unique, allowing just about all of the above systems to be connected using
simple RS232 lines, or, in some cases, a LAN.
If you like, you can call me direct with your COBOL questions.
My number of (408) 279 5303. Ask for Joe Longo, VP Technical Services.
---------------------------------------------- -----=-----
Regards, ----===----
---=====---
Joe Longo, --=== ===--
San Jose. -==== ====--
...!amdahl!aussjo!jal, jal@auspyr.UUCP austec - rmcntm1458@dsacg3.UUCP (John Darby) (01/29/88)
in article <1673@auspyr.UUCP>, jal@auspyr.UUCP (Joe Longo) says: > John M. Ritter (jmr@motown.Allied.COM) writes: > "I've been trying to find a COBOL compiler for about 2 years to run > on AT&T System V. Unfortunately, there doesn't seem to bee (sic) > such a thing." > ACECOBOL runs on a long list of machines, including > AT&T 3B's, VAX/Ultrix, Gould Powernode, Pyramid, Edge, > Xenix 286, Xenix 386, NCR Tower, IBM 9370/IX370, > etc.. > If you like, you can call me direct with your COBOL questions. > My number of (408) 279 5303. Ask for Joe Longo, VP Technical Services. > ...!amdahl!aussjo!jal, jal@auspyr.UUCP austec - rmc We have a Gould 9050 runing UTX/32 4.3BSD with some System V. We have ACECOBOL. We also have UNIFY. Our situation is: ACECOBOL only works under SYSTEM V. UNIFY works under 4.3 BSD. ACECOBOL does not work with UNIFY. All of our routines for UNIFY are therefore presently being written in C. We have a large number of COBOL programmers who use our IBM mainframe and use COBOL to access the TIS database there. These COBOL programmers and others want to port some smaller applications to UNIX.(GOULD) We presently cannot do this. Noone uses ACECOBOL presently because of these drawbacks. My personal impression is that our organization is not pleased with ACECOBOL and the various problems we have encountered. -- John T. Darby, (DLA Systems Automation Center, DSAC-TMM, P.O. Box 1605 Columbus, OH, ntm1458, 614 238-9174) UUCP: {...cbosgd!osu-cis}!dsacg1!jdarby Any opinions expressed are my own, not those of my employer.
jal@auspyr.UUCP (Joe Longo) (02/02/88)
In article <628@dsacg3.UUCP > you write: > We have a Gould 9050 runing UTX/32 4.3BSD with some System V. We have > ACECOBOL. We also have UNIFY. Our situation is: > ACECOBOL only works under SYSTEM V. UNIFY works under 4.3 BSD. > ACECOBOL does not work with UNIFY. > All of our routines for UNIFY are therefore presently being written in C. You should be aware that Gould has contracted us to port Acecobol to BSD, specifically so that it will work with Unify. This port was completed and handed over to Gould in January, this year. A port to their new processor was handed over in December. Please contact Gould if you require this new release. Otherwise, if you have problems with Acecobol in areas other than the Unify interface, please contact me directly. ---------------------------------------------- -----=----- Regards, ----===---- ---=====--- Joe Longo, --=== ===-- San Jose. -==== ====-- ...!amdahl!aussjo!jal, jal@auspyr.UUCP austec - rmc