1) Same here but using BPXBATCH. The z/OS R7 version is close to AOPBATCH. One large application and a small one.
2) DB2 via JDBC Type2 driver. 3) No not yet. Run some tests on CTS 2.3 in the past without any problem. Need to verify on CTS 3.1 current release 4) Same here code once runs everywhere except GUI stuff 5) Comparing apples and oranges. It can be done it works and Cobol and invoke Java. Just be open. Roland -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Jan MOEYERSONS Sent: Thursday, June 01, 2006 7:18 AM To: [email protected] Subject: Re: Using Java in batch on z/OS? >1) Do you use Java as a BATCH language? That is, in a normal JOB? Yes. Yes. Using AOPBATCH to launch a shell that sets the environment (CLASSPATH, etc.) and then invokes the Java program. > >2) If so, what sort of processing does it do? Any VSAM? DB2? Other >database system? DB2 access using SQLJ, so static SQL. Also accessing sequential files both on HFS and in regular MVS datasets. It is a bit tricky to get to the DD statements, though. > >3) Do you use Java for CICS transactions? No, not yet. > >4) If so, the same question about what you use it for, as opposed to >say COBOL. It came about because we wanted to share the code base between batch and on- line (WAS). No opposition, just avoiding to have to maintain two code sets. > >5) In any case, how does Java compare to "legacy" languages such as >COBOL? Especially in ease of programming, debugging, efficiency of >processing (CPU time)? It does save development time and effort in our case. As to ease of programming: I am convinced that it is not the programming language that makes if one can program or not... As we use Log4j to do all the logging and tracing, debugging is really a matter of specifying the right level of logging and wading through a few megabytes of log files. A bit tedious at times, but not really difficult. CPU time is sometimes a bit of an issue. Java still does take a little more than a well-written COBOL equivalent, then again, the JIT makes that it all boils down to have well-written Java... The quality of the design is much, much more important than the programming language. >What I'm trying to determine is if it is worth my while to even bother >with learning more about this IMHO it is definitely worth while. > and, if so, perhaps how to "sell" it to >management. My team leader starts yawning when I discuss any of these >things. He is convincend that Java is not really worth while on the >zSeries. You should not do Java on zSeries because you want to do Java. But if there is a business case for doing Java, you better do it on zSeries! Experience shows that the mainframe is still _the_ platform where RAS means something. Again, independently of what programming language you use. And you better make sure you pass all that Java through your mainframe change & configuration management procedures, because that is what makes the difference. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
