|
Maybe I'm missing here, being a java newbie and all. It seems like the actual file access would be externalized into the driver, JDBC or whatever. Writing the application using JT400 wouldn't necessarily prevent a program from running on a Unix system provided the correct drivers were installed to handle the data requests. Now, if you are referring to AS400 specific functions, signon, data queues, etc. I could see where that wouldn't be portable. Or, maybe I don't understand the toolkit very well. Rick -----Original Message----- From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx]On Behalf Of murali dhar Sent: Monday, January 10, 2005 1:17 PM To: Java Programming on and around the iSeries / AS400 Subject: RE: JAVA400-L Digest, Vol 3, Issue 17 Joe/Paul, I agree Java is write once and run anywhere but if you write a Java application with JT400 classes to read/write from 400 files and run it on the AS400 it will work fine,but next week if you want to run the same code on a UNIX, it wont work because the concept of AS400 objects is not known to other boxes. Regards, Paul Holm <pholm@xxxxxxxxxxxxxxxxx> wrote: Murali, >From my interpretation of your issues: a. As Joe points, out JT400 will run on any java enabled platform. b. If you want database independence, use of the jt400.jar JDBC driver only will enable that. What we typically do is externalize the JDBC connection URL and driver reference in initial parms so that they can be set without code change. I.E. Your application is config at runtime with the JDBC driver and connection URL to use; your classpath includes all JDBC driver jar files that you will use. This enabled database independence while using jt400. c. The remote JDBC Driver will be somewhat slower than native because of the network overhead however the difference is not that big. a. DB Optimization can be critical. Are the correct access paths and indexes there? b. Do you optimally set the jdbc jt400 properties? Extended dynamic, package cache, etc? i. http://publib.boulder.ibm.com/pubs/html/as400/v4r5/ic2924/index.htm?info/jav a/rzahh/jdbcprop.htm HTH Thanks, Paul Holm Business: 760-432-0600 Home: 760-432-6550 Cell: 760-415-8830 PlanetJ - Makers of WOW (AKA... WebSphere on Steroids) -----Original Message----- From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx]On Behalf Of java400-l-request@xxxxxxxxxxxx Sent: Monday, January 10, 2005 10:02 AM To: java400-l@xxxxxxxxxxxx Subject: JAVA400-L Digest, Vol 3, Issue 17 Send JAVA400-L mailing list submissions to java400-l@xxxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit http://lists.midrange.com/mailman/listinfo/java400-l or, via email, send a message with subject or body 'help' to java400-l-request@xxxxxxxxxxxx You can reach the person managing the list at java400-l-owner@xxxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of JAVA400-L digest..." Today's Topics: 1. RE: java-qtemp (Joe Pluta) ---------------------------------------------------------------------- message: 1 date: Mon, 10 Jan 2005 10:46:09 -0600 from: "Joe Pluta" subject: RE: java-qtemp > From: murali dhar > > Hi Joe, > we are not using JT400 as it is specific to AS400,any java code we write > on the AS400 needs to be platform independent,Using JT400 we can never > freely port Java code to run on Unix. This makes no sense to me. You're trying to use QTEMP, but you say that JT400 is platform specific. There is nothing platform specific about JT400, it runs on any platform. If you want your back end to be platform specific as well, you use a factory class and generate a different access object for each platform. Joe ------------------------------ -- This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) digest list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/java400-l or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l. End of JAVA400-L Digest, Vol 3, Issue 17 **************************************** -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.6.9 - Release Date: 1/6/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.6.9 - Release Date: 1/6/2005 -- This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/java400-l or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l. --------------------------------- Do you Yahoo!? Yahoo! Mail - You care about security. So do we. -- This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/java400-l or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l. Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain legally privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.