|
Your situation is interesting: during the last decade IBM efforts have focused on moving iSeries veterans people to Java, but they have forgotten about people like you, coming on the opposite direction.Sure feels like it. Probably they never expected such a thing to happen :)
For starters, I would suggest taking a look to http://search400.techtarget.com/originalContent/0,289142,sid3_gci996499,00.htmlThanks. Will take a thorough look.
Considering your current situation, perhaps it would be better if you post specific questions about your particular problem, and maybe we can help you with that.Sure. This particular problem was a Java 1.3 program doing ftp-transfers which repeatedly got stuck in TIMW. Since this was ancient production code from before my time we could not just throw new versions in there, and I could not attach a debugger (no network access but telnet and ftp) so I could not ask WHERE this happened. Usually I have a stack trace to deal with but I could not figure out how to get one. Well, option 11 on the job gave me a call stack window, and THANKFULLY the stack entries for the java code is very readable so it was very easy to identify the culprit (an accept() waiting for a connection which never came). I believe this is Java 1.3 under V5R1.
For starters, you could post the following information: the description of your problem, the version of operating system you are running, what kind of application server you are using, your version of Java, and so on.
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.