|
I think Java was only intended for the RISC Processor. If you have a RISC processor, and maybe an updated OS/400, yea, why not Java?!! Mike Everidge, Network Engineer / AS/400 Programmer / Systems Programmer >>> <mtanveer@friedmancorp.com> 11/15/99 10:39PM >>> I HAVE A AS/400 9402 AT HOME JUST FOR LEARNING PURPOSE. I HAVE V3R1 ON IT. JUST WONDERING I CAN USE THIS MACHINE FOR JAVA. ANY IDEA. Thanks -----Original Message----- From: owner-java400-l@midrange.com [mailto:owner-java400-l@midrange.com]On Behalf Of Alex Garrison Sent: Friday, November 12, 1999 4:33 PM To: JAVA400-L@midrange.com Subject: Fw: Fw: forcing native access with websphere and toolbox Joe, It definitely does have a huge impact on our dasd utilization for just the reason you stated. However, 8.5gb drives for our as/400 are only $1600 installed, so dasd is cheap. Legacy impact: again definitely a concern. We had to recompile/modify all rpg programs that use these files. All the rpg code is ile sql rpg. We found the evals still were ok, but moves had to account for the fields being twice as many bytes. It took about a day to fix all that. However, we were very fortunate in that our design isolated the web system from the main body of our legacy system (millions of lines of rpg and thousands of files) through a series of data queues. Any data in/out of the web systems move through these data queues, so we really only had to fix the legacy code that interfaced the web databases to the dataqueues. When you are desperate for performance, you will try almost anything. In balance conversion to unicode was rather painless, and a 25% performance gain is nothing to sneeze at. ----- Original Message ----- From: <Pluta@nexgensoftware.com> To: <JAVA400-L@midrange.com> Sent: Friday, November 12, 1999 1:01 PM Subject: Re: Fw: forcing native access with websphere and toolbox Alex Garrison wrote: One of the things the performance guide recommends is to change your physical files to use ccsid 13488 (unicode) for all character data. This is supposed to speed things (...) ---------------- While I see how the conversion would benefit your Java programs, I do have a certain concern... unicode requires two physical bytes of storage for each character. If you have large character fields, this could significantly increase your DASD requirements. Also, what's the legacy system downside? Doesn't this actually ADD conversion requirements to legacy systems? There is a certain sense of "baby with the bathwater" in switching the storage technique for character data in order to improve performance. Joe +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +--- +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +--- +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +--- +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +---
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.