Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Usesage OO (enterprise) COBOL

2 views
Skip to first unread message

P. Heijne

unread,
Jul 8, 2004, 6:34:31 AM7/8/04
to
I am busy investigating the use and advantages of OO (enterprise) COBOL.
After searching the Internet I got the feeling that OO COBOL isn't used
much.

Which companies already use OO COBOL?

Was the conversion difficult?

How is the interaction between COBOL and JAVA, .NET and other OO languages?

Does the OO COBOL have advantages in practice?

Thanks in advance,

Patrick Heijne


JerryMouse

unread,
Jul 8, 2004, 8:53:59 AM7/8/04
to
> I am busy investigating the use and advantages of OO (enterprise)
> COBOL. After searching the Internet I got the feeling that OO COBOL
> isn't used much.

My observation is that OO COBOL is used almost to the degree that it is
needed.

Perhaps if you told us the goal you're trying to achieve, we could provide a
more concrete case. Surely you're not contemplating conversion to OO COBOL
just for fun?

William M. Klein

unread,
Jul 8, 2004, 3:05:51 PM7/8/04
to
My perception (from limited input is)

OO COBOL is *not* used much (almost not at all) on IBM mainframes

OO COBOL is used more frequently (still not commonly) on Workstation (PC,
Unix, Linux) environments

I don't know about other (non-IBM) mainframes

--
Bill Klein
wmklein <at> ix.netcom.com
"P. Heijne lycos.nl>" <Patrick64 < at > wrote in message
news:40ed22d4$0$37789$e4fe...@news.xs4all.nl...

Scot Nielsen

unread,
Jul 9, 2004, 10:46:14 AM7/9/04
to
WRT interaction with other languages. Yes indeed, OO COBOL has been used
widely to interface between JAVA, COM, .NET etc. Invariably it has been used
as the 'glue'.

With special regard for .NET:

One of the biggest issues for the programmer in .net -- but I'm not talking
about the whole ethos of moving COBOL apps to this environment that's
another story -- is how to present a simple COBOL record to any other
language such as C# or VB or whatever. Simple and very natural to the COBOL
programmer it may be, but to other parties in .NET the COBOL record is quite
mysterious and inaccessible in its raw state so again, OO will be widespread
in its 'glue' form in .NET simply to allow access to COBOL data.

Completely biased as I am about this, I'd like to state that the Micro Focus
implementation of OO COBOL in .NET I feel is one of the finest
implementations of OO COBOL -- as such we hope that it can become much more
than just glue for existing and future COBOL developers.


"P. Heijne lycos.nl>" <Patrick64 < at > wrote in message
news:40ed22d4$0$37789$e4fe...@news.xs4all.nl...

0 new messages