|
Introduction
My name is Gary Peskin. I started this site because I wanted to share what I've learned in working with Java under OS/390. I've searched the web and newsgroups trying to find information about Java under OS/390 but it's been scattered and mixed in with other interesting, but not always helpful, information. The idea of this site is to collect, in one place, all of the relevant information for effective development with Java on OS/390. This site is not a primer on Java or on OS/390. I'll try to place some of those sites on the links page.
Much of my knowledge has come from trial and error and I've recorded it here as a reference for you and for me. I hope that lots of people will visit this site and send me their thoughts and discoveries so that we can be a clearinghouse for this sort of information. I don't pretend to be the world's foremost expert on OS/390 or Java and I don't guaranty that everything on this web site is 100% accurate. This is information that I've gleaned from my experience and the way that I describe things here works for me right now. Please let me know if something needs correcting, adjusting, or just another way of looking at it.
I hope that this web site will grow substantially over time. I am depending on your contributions and your feedback to add content that you find helpful.
There are lots of permutations of OS/390 and Java so things that work in one environment may not work in another. I've also done quite a lot of work using WebSphere Application Server for z/OS and OS/390. I'll include that information as well.
My current interest is in combining Java with existing COBOL and Assembler programs to leverage the existing code which (a) works and (b) contains lots of business rules upon which an enterprise depends. In many cases, the existing code is the only place where these rules reside. They've been in place so long that no one left in the organization really can articulate the rules any more. However, the organization continues to implicitly rely on these rules.
I think that too many new developers unwisely ignore the enormous value in the existing code. In this age of constant rebooting on the desktop, not enough value is given to systems which have stood the test of time and proven themselves as mission-critical systems on which an organization can depend. Just because things are old doesn't mean that they are useless or worse than something which is newer.
In addition, the reliability and servicability of the mainframe is unmatched by other platforms. IBM has done an excellent job in capturing information needed to fix defects, both in user code and in IBM code. This has steadily improved with each release of the JVM and WAS.
I'm a member of IBM's PartnerWorld for Developers and Sun's Java Developer Connection. Also, this site is an IBM affiliate and we earn a small commission if you buy certain IBM products through links on this site. Other than that, I don't have any connection to IBM or Sun except as a user of their tools.
I welcome all comments on this site, including what you think of the site organization, readability of the type face, and anything else.
|