Which is why I keep recommending Object Orientation: An Introduction for COBOL Programmers, by Ray Obin, Micro Focus Press. It's not so long of a journey as it appears, and this book takes one more than half of the way to understanding. As for designing and writing, I am probably not qualified to have an opinion yet. But if you are a COBOLer, whether you care to learn Object COBOL or not, I think that this book gives a useful introduction to the ideas, the majority of which are already known by other names in structured programming. As for replacing, well, peaceful co-existence would be welcome. There's a pretty good chance that I will look at Java for my socketing needs, since I understand that it handles that rather well. insert std disclaimers > -----Original Message----- > From: Gavin Scott [SMTP:[log in to unmask]] > Sent: Thursday, April 16, 1998 4:50 PM > To: [log in to unmask] > Subject: [HP3000-L] Java/iX > <snip> > Unfortunately we're not yet to the point that you can just throw > out all your COBOL and replace it with Java. Also don't forget > that learning to design and write Object Oriented systems is not > a skill that's trivial to acquire.