Re-starting RDi did not resolve the problem. What did work was opening a second member and compiling that, and then compiling the problem child (without any changes) again.
------------------------------
message: 2
date: Thu, 19 May 2016 18:40:46 +0000
from: Ken Killian <kkillian@xxxxxxxxxxxx>
subject: Re: [WDSCI-L] SQLRPGLE compile error
Just to ask, does a "restart of RDI", fix this error?
-Ken Killian-
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Terry Hertel
Sent: Thursday, May 19, 2016 1:50 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] SQLRPGLE compile error
I just started getting this error when compiling an SQLRPGLE member. The program compiled fine earlier when I commented out two lines in the SQL statement. Now I removed the double slashes and am recompiling. The program compiles successfully but I get a pop-up window with the following:
RSEG1003U An unexpected exception has occurred
Details:
java.lang.IllegalArgumentException: Comparison method violates its general contract!
java.lang.IllegalArgumentException: Comparison method violates its general contract!
at java.util.TimSort.mergeHi(TimSort.java:910)
at java.util.TimSort.mergeAt(TimSort.java:527)
at java.util.TimSort.mergeForceCollapse(TimSort.java:468)
at java.util.TimSort.sort(TimSort.java:265)
at java.util.Arrays.sort(Arrays.java:1772)
at org.eclipse.jface.viewers.ViewerComparator.sort(ViewerComparator.java:189)
at org.eclipse.jface.viewers.StructuredViewer.getSortedChildren(StructuredViewer.java:1061)
at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:667)
at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:615)
at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:607)
at org.eclipse.jface.viewers.StructuredViewer$7.run(StructuredViewer.java:1500)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1436)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1397)
at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1497)
at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:521)
at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1456)
at com.ibm.etools.iseries.rse.ui.view.errorlist.QSYSErrorListViewPart.refresh(QSYSErrorListViewPart.java:1199)
at com.ibm.etools.iseries.rse.ui.view.errorlist.QSYSErrorListViewPart.retrieveTable(QSYSErrorListViewPart.java:1067)
at com.ibm.etools.iseries.rse.ui.view.errorlist.QSYSErrorListViewPart.configure(QSYSErrorListViewPart.java:932)
at com.ibm.etools.iseries.rse.util.ShowEventsFileInErrorListView.openErrorListView(ShowEventsFileInErrorListView.java:145)
at com.ibm.etools.iseries.rse.util.ShowEventsFileInErrorListView.<init>(ShowEventsFileInErrorListView.java:83)
at com.ibm.etools.iseries.rse.ui.view.errorlist.QSYSErrorListTriggerListener$DisplayEventsFileRunnable.run(QSYSErrorListTriggerListener.java:73)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4147)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3764)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
I'm on RDi version 9.5.03 and just applied the java patch from IBM this week using the Installation Manager.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & 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.
------------------------------
message: 3
date: Thu, 19 May 2016 16:22:35 -0500
from: Booth Martin <booth@xxxxxxxxxxxx>
subject: Re: [WDSCI-L] Multi-line comments
ctrl-\ uncomments selected lines.
On 5/19/2016 8:47 AM, dlclark@xxxxxxxxxxxxxxxx wrote:
then, what if you were temporarily commenting out those lines of code
and needed to later uncomment them?
------------------------------
message: 4
date: Fri, 20 May 2016 09:13:26 -0400
from: MichaelQuigley@xxxxxxxxxx
subject: Re: [WDSCI-L] Multi-line comments (was: Any change to RDI
settings to edit **FREE totally free RPG?)
"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 05/19/2016 09:50:10 AM:
----- Message from dlclark@xxxxxxxxxxxxxxxx on Thu, 19 May 2016 09:
47:47 -0400 -----
To:
Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject:
Re: [WDSCI-L] Multi-line comments (was: Any change to RDI settings to
edit **FREE totally free RPG?)
"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 05/18/2016 09:24:00
PM:
Try inserting your first line comment so everyone knows what you've
done
and why you've done it. Then cursor to the first line, press Alt+L
to
mark
the first line of the block, go to the last line and hit Alt+L (or
simply
cursor down with the shift key held), then press Ctrl+/ The block is
commented out--i.e., each line is marked as a comment. Oh, then you
need
to press Alt+U to unmark the block.
Yes, I'm passing familiar with all that and I don't like it.
I'm
a bit particular at times and I make no excuses for it. I'm not
strictly
OCD (just a little CDO, if you catch my drift), but I do like things a
certain way. In this case, I don't like all the shifted lines. And,
then, what if you were temporarily commenting out those lines of code
and
needed to later uncomment them? Is that anticipated by RDi
keystrokes, too? No, I like my block comments in JavaScript, etc. We
are supposed
to
be a color-coded, context-sensitive world. ;-)
In your Preferences, you can configure the block comment to 'Overwrite blanks' or 'shift' so you don't have to change the indentation of your code--provided you don't start your code in column 7 or earlier. You can also choose to comment with either '//' or '*'.
Navigation to preferences:
Windows, Preferences, Remote Systems, Remote Systems LPEX Editor, ILE RPG
- Block comment behavior is toward the bottom.
Sincerely,
Dave Clark
Michael Quigley
Computer Services
The Way International
www.TheWay.org
419 753-1222
------------------------------
message: 5
date: Fri, 20 May 2016 13:38:51 +0000
from: Kurt Anderson <Kurt.Anderson@xxxxxxxxxxxx>
subject: Re: [WDSCI-L] Error in Outline view processing?
I don't have an answer, but I do have a question.
What do you mean by: " internal subprocedure with only a PI"
Are you saying you don't have a dcl-proc and end-proc? (Doesn't compile for me.) Or are you saying that your subprocedure is empty aside from the dcl-pi? (Shows up in outline for me.) Or something else I'm missing entirely.
Thanks,
Kurt Anderson
Lead iSeries Developer ? Application Development, Service Delivery Platform
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Wednesday, May 18, 2016 6:18 PM
To: Wdsci-L <wdsci-l@xxxxxxxxxxxx>
Subject: [WDSCI-L] Error in Outline view processing?
Before I go to the trouble of opening a PMR can someone else please confirm this for me to make sure it is not just me.
It seems that when the compiler rules re Prototypes were changed, the code that builds the Outline view was not updated.
If I have an internal subprocedure with only a PI definition then it simply doesn?t appear in the outline view at all. In my case this particular subproc was used as the handler for XML-SAX so I thought that might be the cause - but I have since checked with another ordinary subproc and the result ins the same.
Interestingly the same outline view has also ?lost? at least one stand-alone field. It just isn?t there despite being used in a number of places.
P.S. The code compiles just fine.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & 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.
------------------------------
message: 6
date: Fri, 20 May 2016 08:50:49 -0500
from: "Kevin Bucknum" <Kevin@xxxxxxxxxxxxxxxxxxx>
subject: Re: [WDSCI-L] Error in Outline view processing?
Of course Jon and Susan have a great article that explains the changes that went in with 7.1. You don't always need a prototype now.
http://www.ibmsystemsmag.com/ibmi/developer/rpg/prototyping-best-practices/
Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Kurt Anderson
Sent: Friday, May 20, 2016 8:39 AM
To: Rational Developer for IBM i / Websphere Development Studio Client forSystem i & iSeries
Subject: Re: [WDSCI-L] Error in Outline view processing?
I don't have an answer, but I do have a question.
What do you mean by: " internal subprocedure with only a PI"
Are you saying you don't have a dcl-proc and end-proc? (Doesn't compile for me.) Or are you saying that your subprocedure is empty aside from the dcl-pi? (Shows up in outline for me.) Or something else I'm missing entirely.
Thanks,
Kurt Anderson
Lead iSeries Developer ? Application Development, Service Delivery Platform
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Wednesday, May 18, 2016 6:18 PM
To: Wdsci-L <wdsci-l@xxxxxxxxxxxx>
Subject: [WDSCI-L] Error in Outline view processing?
Before I go to the trouble of opening a PMR can someone else please confirm this for me to make sure it is not just me.
It seems that when the compiler rules re Prototypes were changed, the code that builds the Outline view was not updated.
If I have an internal subprocedure with only a PI definition then it simply doesn?t appear in the outline view at all. In my case this particular subproc was used as the handler for XML-SAX so I thought that might be the cause - but I have since checked with another ordinary subproc and the result ins the same.
Interestingly the same outline view has also ?lost? at least one stand-alone field. It just isn?t there despite being used in a number of places.
P.S. The code compiles just fine.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & 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 Rational Developer for IBM i / Websphere Development Studio Client for System i & 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.
------------------------------
Subject: Digest Footer
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) digest 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.
------------------------------
End of WDSCI-L Digest, Vol 14, Issue 259
****************************************
midrange.com
