|
Hi Jeff, You can find details and the download here: http://www-1.ibm.com/support/docview.wss?rs=715&context=SSZND2&context=SSKJJP&context=SSBRLP&context=SS2MD7&dc=D400&uid=swg24008100&loc=en_US&cs=utf-8&lang=en This is an update for the Java Virtual Machine that runs the WDSc workbench. You cannot install it via the automated update manager because the virtual machine can't be running when the fix is applied (you have to shutdown WDSc first.) Don Yantzi WebSphere Development Studio Client for iSeries IBM Toronto Lab Phone: (905) 413-4476 IBM internal: IBMCA(yantzi) - Internet: yantzi@xxxxxxxxxx jstevens@mizehous er.com Sent by: To wdsci-l-bounces@m Websphere Development Studio Client idrange.com for iSeries <wdsci-l@xxxxxxxxxxxx> cc 12/08/2004 03:50 Subject PM Re: [WDSCI-L] Re: Problems with DDS source Please respond to Websphere Development Studio Client for iSeries Don, Can you explain more about the JVM fix? Is that a WDSC fix of the JVM or does the fix come from somewhere else? Thanks! Jeff Stevens Mize, Houser & Co. P.A. 913 451 1882 JStevens@xxxxxxxxxxxxxx Don Yantzi <yantzi@xxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 12/08/2004 02:46 PM Please respond to Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx> To "Wdsci-L" <wdsci-l@xxxxxxxxxxxx> cc Subject [WDSCI-L] Re: Problems with DDS source Hi Jon, Do you have the jvm fix applied to these machines? If so, then can you locate the j9.dmp file in the C:\Documents and Settings\%windows user ID% directory and send it to me along with a copy of the DDS source if possible. In the meantime you could try to disable the J9 Java virtual machine. To do this edit the file: D:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1.2\wdsc.ini and remove the -Xj9 from the vmargs line. Don Yantzi WebSphere Development Studio Client for iSeries IBM Toronto Lab Phone: (905) 413-4476 IBM internal: IBMCA(yantzi) - Internet: yantzi@xxxxxxxxxx "Jon Paris" <Jon.Paris@Partne r400.com> To "Wdsci-L" <wdsci-l@xxxxxxxxxxxx> 12/08/2004 02:46 cc PM Don Yantzi/Toronto/IBM@IBMCA, "Susan Gantner" <susan.gantner@xxxxxxxxxxxxxx> Subject Problems with DDS source OK - here's a weird one. Running a class on WDSC for a COBOL customer. All machines running XP and WDSC 5.1.2. All loaded from same image, no install errors reported. All PTFs loaded on the 400 (V5R2) On some machines the whole workbench blows sky high when attempting to open a DDS source member. Error reported is a JVM 3 error I think. It happens during the download phase or thereabouts, because if the member is locked you do get asked "do you want to open in browse" and the error is subsequent to that. All machines can load and edit COBOL and CL programs without problems - only DDS causes the error as far as we know right now. We are going to try applying service pack 2 tonight, but have very little faith that it will make a difference as many of the machines are working just fine. Any ideas on where to even begin to look? Jon Paris Partner400 www.Partner400.com _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l. _______________________________________________ This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-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.