|
No, there was nothing else that would be factually wrong. Actually, http://www-1.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/ docs/as400v35std/docs/dbgsetup.html is the most helpful page of them all, for it mentions both DEBUGSOURCEPATH and WebSphere command line property parameter. But, personally, I find it exasperating having to roam loosely linked IBM sites in search of what traditionally could be found in a just couple of IBM manuals available from a single online documentation page. Hyperlink documentation, in my view, is infinitesimally inferior to the good old set of BookManager manuals. By the way, Info Center 5.1 contains yet another page on servlets debugging. It suggests storing compiled classes in /QIBM/ProdData/Java400 which does not work for packages - at least, I could not make it work. Very confusing. Thank you again, Lo -----Original Message----- From: Frances Stewart [mailto:francess@us.ibm.com] Sent: Monday, November 26, 2001 10:17 PM To: java400-l@midrange.com Subject: RE: STRDBG/followup Glad you got it working. I have asked that the inaccurate info in step 1 be corrected - it should say "javac -g MyServlet.java" Apart from the misinformation in step 1, what was not useful on that page or would make it more useful? We are always trying to improve our docs. Frances Stewart WebSphere Application Server for iSeries 400 IBM Rochester "Raikov, Lo" <Lo.Raikov@MISYS.C To: "'java400-l@midrange.com'" <java400-l@midrange.com> OM> cc: Sent by: Subject: RE: STRDBG/followup java400-l-admin@mi drange.com 11/25/01 08:06 PM Please respond to java400-l It's the -classpath command line property for the WebSPhere instance that did the trick. STRDBG seems to do a bit of handshaking with the WebSphere server instance job and, in doing so, find out where to look for the classes to be debugged. A separate STRDBG job environment variable DEBUGSOURCEPATH is used to locate the java source. Info on http://www-1.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/ docs/as400v35std/docs/dbgsetup.html is not particularly helpful. For instance, I was not able to run javac in the recommended form: javac -g mycompany.myproduct.MyServlet.java The source just would not be found. Thanks for your your help, Lo -----Original Message----- From: Frances Stewart [mailto:francess@us.ibm.com] Sent: Saturday, November 24, 2001 4:14 AM To: java400-l@midrange.com Subject: RE: STRDBG/followup You are supposed to specify the package scoped class name. I.e. if MyClass.java has package staement: package com.mycompany.mystuff; you would specify STRDBG CLASS(com.mycompany.mystuff.MyClass) You might want to see if this info helps: http://www-1.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/ docs/as400v35std/docs/dbgas400.html Some of the information is specific to WebSphere but most is not. Frances Stewart WebSphere Application Server for iSeries 400 External: (507) 253-2795 Tie-line: 8-553-2795 IBM Rochester "Raikov, Lo" <Lo.Raikov@MISYS.C To: "'java400-l@midrange.com'" <java400-l@midrange.com> OM> cc: Sent by: Subject: RE: STRDBG/followup java400-l-admin@mi drange.com 11/22/01 11:25 PM Please respond to java400-l A follow-up: it does seem to work for unpackaged servlets, but not for packages or jar files. Lo -----Original Message----- From: Raikov, Lo [mailto:Lo.Raikov@MISYS.COM] Sent: Friday, November 23, 2001 4:10 PM To: java400-l@midrange.com Subject: STRDBG I'm trying to use STRDBG command in the servlet debugging scenario. I followed Info Center instructions word for word, but STRDBG command just would not find my class files. Given that on STRDBG I'm only supposed to specify the name of the class, not the full path name, where does STRDBG look for the class to debug? Lo _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l. _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l. _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l. _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l. _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l.
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.