|
Hi Hak, many thanks for the reply and for your time and help. All the dates on the files matched - it was the CLASSPATH that was causing the problem. Paul. haklui@ca.ibm.com wrote: > Paul: > I think the feature was added AS IS during SP2 time. Since then there > has been no updated/rebuild of the download version. > Following was in the mailing list previously. Could you check if these > files matched with yours? > > >******************************************************************************************************************************************** > For problems I saw posted in this discussion seem to indicate that the CL > GUI files have not been properly installed. > > I used the WinZip program to unzip the file "clguiprompting.zip" and then > extract all files to "x:\wdt400\". > > Please check for dates of these files: > > Archive: clguiprompting.zip > Length Date Time Name > ------ ---- ---- ---- > 53184 06-27-01 08:40 codeprmt.exe > 3277069 05-15-01 09:30 java/jt400.jar > 1698 07-18-01 11:51 java/LpexPromptAS400Command.class > 3435 07-18-01 11:51 java/PromptAS400Command.class > 304157 07-18-01 15:17 java/util400.jar > > 26112 07-18-01 15:04 system/L4clprs.dll > 156672 07-19-01 16:10 system/L4code.dll > > 53184 06-27-01 08:40 codebrws.exe > 53184 06-27-01 08:40 codeedit.exe > 53184 06-27-01 08:40 codeevnt.exe > 53696 06-27-01 08:40 codefstr.exe > > 2040 07-10-01 16:34 extras/clguif4.lx > 2734 06-20-01 10:46 extras/profsys.lxu > > ------ ------- > > >*********************************************************************************************************************************************** > > Hak Lui > AS/400 AD, IBM Canada Ltd. > e-mail: haklui@ca.ibm.com > > tuohyp@attglobal.net@midrange.com on 12/05/2001 03:48:26 AM > > Please respond to code400-l@midrange.com > > Sent by: code400-l-admin@midrange.com > > To: code400-l@midrange.com > cc: > Subject: Re: Problem with CL GUI Prompting > > Hi Hak, > > Still no luck, I'm afraid. > > The only difference in your instructions was to > ensure that the communications daemon was ended. I > re-booted, closed the communications daemon from > the toolbar, did a CODEEDIT /C EXIT from a DOS > window, extracted from the .ZIP file (to WDT400), > restarted communications, edited an existing CL > program (from a project list), made sure that CL > GUI prompting was selected on Extras, and I still > get "Unable to find required classes". > > I have a full install of WDT, so nothing should be > missing. > > I have SP3 installed, could this be a problem (FAQ > and web page say download is for SP1/SP2)? > > I noted when extracting the files that one of them > - L4CODE.DLL had an earlier date then the one it > was replacing, 19/07/2001 replacing 26/09/2001. > > I had downloaded the zip from > http://www-4.ibm.com/software/ad/wdt400/support/co > desupport.html. > > As always, all help greatly appreciated. > > TIA > > Paul Tuohy > > _______________________________________________ > This is the CODE/400 Discussion & Support (CODE400-L) mailing list > To post a message email: CODE400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l > or email: CODE400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/code400-l. > > _______________________________________________ > This is the CODE/400 Discussion & Support (CODE400-L) mailing list > To post a message email: CODE400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l > or email: CODE400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/code400-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.