|
Hi Diane, Sorry I'm so late getting to this. Are you still experiencing this problem? thanks, Violaine Batthish WebSphere Development Studio Client, IBM Toronto Lab You know you've achieved perfection in design, not when you have nothing more to add, but when you have nothing more to take away. - Antoine de Saint-Exupéry wdsci-l-bounces@xxxxxxxxxxxx wrote on 28/03/2006 01:03:35 PM: > Group, > Last week I downloaded the updates to WDSC, since that time, when I try to > compile a SQLRPGLE program, I receive the following error: > RSEG1003U > java.lang.reflect.InvocationTargetException > java.lang.reflect.InvocationTargetException > at > org.eclipse.jface.operation.ModalContext.runInCurrentThread(Unknown > Source) > at org.eclipse.jface.operation.ModalContext.run(Unknown Source) > at org.eclipse.jface.window.ApplicationWindow$1.run(Unknown > Source) > at org.eclipse.swt.custom.BusyIndicator.showWhile(Unknown Source) > at org.eclipse.jface.window.ApplicationWindow.run(Unknown Source) > at org.eclipse.ui.internal.WorkbenchWindow.run(Unknown Source) > etc, etc, etc, ....... > > > Even with a compile that is good, I still receive the error. When I > compile the program, I view the iSeries Commands Log, the message > displays that program "SQL package MYPROGRAM in MYLIB has been created." > Following the completion message, I then get the RSEG1003U error. > If the compile fails, then the iSeries Commands log gives me a failure > message, and then the RSEG1003U error appears. Because of the failure in > the log, I switch to my 5250 session to study the compile errors. > > If the compile completes or fails, I continually get the RSEG1003U error. > > Is anyone aware of this issue or a fix for it? > > VERSION & BUILD: > Version: 6.0.1 > Build id: 20050725_1800 > > > Diane Mueller
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.