tags:

views:

474

answers:

8
+4  Q: 

Java on OpenVMS?

We run batch files on our OpenVMS Alpha and Integrity servers. Up until now they have been written in COBOL. As you can imagine there are many reasons why will not be able to maintain that process.

At the same time we have a team of developers that use Eclipse and know Java very well. Is there away to use Eclipse with OpenVMS?

+1  A: 

Don't leave Cobol yet - call a-cobol-programmer-thinking-about-switching-to-the-modern-world and make a trade: you teach him Java, He maintains your legacy.

gimel
A: 

You want to run Java on OpenVMS? Have you asked the google?

Tom Hawtin - tackline
+2  A: 

Maybe it's because I don't keep up with COBOL, but I am not sure why you're convinced you have to abandon it. I realize it's not the "in" thing, but if you already have a large code base I'd think at least twice before switching to another language. If it's a lack of developers, I don't think you're going to run out that soon.

That said, googling Eclipse & OpenVMS gave this link: http://www.sdtimes.com/SearchResult/32973 So it looks like you can still get Eclipse for OpenVMS from eCube. If I'm reading that article correctly, HP seems to want you to go the NetBeans directions. Personally, I'm still using Emacs (and not currently doing any Java), so won't make a recommendation; I just wanted to point out that there are other ways to develop Java than Eclipse.

I didn't find Java for VMS on Sun's site (someone feel free to correct me if you find it), but it looks like you can get the JDK from HP/Compaq at: http://www.compaq.com/java/download/ovms/1.5.0/index.html

Edit: I meant, but forgot to say: Assuming you're using a JVM on the VMS side, you should be able to development with Eclipse on another platform, and copy the byte code to the Alphas.

PTBNL
+1  A: 

Shell scripts and java usually aren't a great mix. You may want to consider installing a JVM on your VMS servers, and using one of the JVM-hosted languages that handle that case better- jython, jruby, or groovy might be candidates to consider.

Tim Howland
+2  A: 

Speaking from experience, if you do decide to rewrite your batch processes in Java I'd suggest you use a third party batching framework like Spring Batch instead of 'growing your own'.

Using a framework also constrains you to work within a standard and should provide non-functional requirements like re-runability, transactions and error handling.

We've (re)built a number of batch processes from various technologies to Java using a home-grown framework and I find we end up spending time on fixing/optimizing the framework rather than just focusing on the business logic.

Kevin Williams
Speaking from the same experience, I completely agree. Of course, experience isn't as useful if it's all good.
Don Kirkby
+1  A: 

Eclipse relies on native Java extensions that do not appear to have been ported to OpenVMS. Don't give up though. Java runs on OpenVMS (at least 1.5 according to a Google search).

NetBeans has a Java only edition that should work on OpenVMS. On the NetBeans Download Page select the OS Independent Zip option for the platform.

John Meagher
+1  A: 

Are you running the batch files on your OpenVMS system? If so, HP makes Java available for OpenVMS, not SUN; you will have to look at their site. You can develop your java code on a windows/linux machine and test it on your VMS system; you must be aware of the native extensions that you cannot use on the VMS implementation of Java.

MGoDave
+1  A: 

Speaking with some experience in this area, I suggest developing with Eclipse on your Windows/Linux/Mac desktop, and pushing the code out to OpenVMS for testing/deployment. Eclipse won't run on OpenVMS because of some platform-specific components of its GUI.

Some caveats:

  • Make sure that you are using the same version JVM on your desktop as on OpenVMS.
  • The case insensitivity in OpenVMS can be a problem when using inherently case-sensitive Java .class files. Package everything in a .jar and deploy it that way.
  • The attributes on .jar files have to be set correctly or the OpenVMS JVM can't open them. The following command should do the trick: SET FILE *.jar /ATTR=(RFM:STMLF,RAT:CR)
  • HP provides both a "fast" JVM and a "classic" JVM. Use the fast VM unless your memory needs are highly variable.
Travis Beale