Re: RDi 9.1 does not save source members -- WDSCI-L

Thomas,

At least creating a new work space beats doing a complete re-install...
<smirk>

Just looking at the bright side!

Using RDi and it's processors' for the last 8-years, I am really learn the Preference really well!
Just looking at the Silver lining in re-doing my workspace occasionally... <grin>

Just glad it working correctly now!

PS. I love the filter in the outline view in RDi 9.1. Probably my favorite new feature that I know about in this release. We need a "What is new this release", like other releases... <smirk>

http://www.ibm.com/developerworks/rational/library/rational-developer-power-systems-software-8-0-3/index.html?ca=drs

https://www.ibm.com/developerworks/community/forums/html/topic?id=a130d76d-4d0a-474f-95ea-5ff0834cd7ae&ps=25

Now we need "What is new for RDi 9.1", which I guess isn't too many new things...

Tried the code coverage, but I don't yet follow it that well... (Using it on old programs...)

-Ken Killian-

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of thomas.raddatz@xxxxxx
Sent: Tuesday, July 15, 2014 7:46 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] RDi 9.1 does not save source members

Ken,

I already created a new workspace and now the member is saved to the i again.

I just added "Workkspace Mechanic" a couple of weeks ago. That helps to create a new workspace. I just figured out that I can at least export my RSE connections along with my object filters. Unfortunately I cannot do that with my TurnOver connections.

At the end creating a new workspace on a RDi upgrade seems to be "strongly recommended".

Thomas.

wdsci-l-bounces@xxxxxxxxxxxx schrieb am 15.07.2014 13:30:37:

Von: kkillian@xxxxxxxxxxxx
An: wdsci-l@xxxxxxxxxxxx,
Datum: 15.07.2014 13:31
Betreff: Re: [WDSCI-L] RDi 9.1 does not save source members Gesendet
von: wdsci-l-bounces@xxxxxxxxxxxx

Thomas,

If your workspace possible got corrupt, try creating a brand new
workspace, just to eliminate that possibility...

I personally, always create a new workspace on an RDI upgrade myself.
Although, I must admit it is sort of pain to re-apply all of my
customization...
Also, by having different workspaces, I can compare my old RDI 9.0.1
with the newer RDi 9.1.

OH well, a text file with notes of my changed setting helps me set it
up for a new workspace...

-Ken Killian-
IBM i running on Power-System, Mobile Comm Developer Back-End.
http://angustheitchap.com/familytreedates.jpg
(423) 510-3129

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of
thomas.raddatz@xxxxxx
Sent: Tuesday, July 15, 2014 7:23 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] RDi 9.1 does not save source members

Ken,

Thank you for jumping in and trying to help.

I already checked the error log with no success. The error log does
not contain anything regarding to the "save" problem. I strongly
assume that my workspace got messed up, because with the corrupted
workspace I get error messages that I do not get with a fresh one.
Of course both workspaces are used by the same installation of RDi
9.1. Furthermore the plugin (iSphere Core) mentioned in the error log,
is installed by the "dropins" folder and hence the same for both
workspaces.

Here is the error log:

!ENTRY com.ibm.etools.stacktool 0 0 2014-07-15 13:10:44.995 !MESSAGE
plugin is stopped and cleaned up the stack tool properties file.
!SESSION 2014-07-15 13:11:00.621
-----------------------------------------------
eclipse.buildId=unknown
java.fullversion=JRE 1.7.0 IBM J9 2.6 Windows 7 x86-32
20140313_192258 (JIT enabled, AOT enabled) J9VM -
R26_Java726_SR6_20140313_1318_B192258
JIT - r11.b05_20131003_47443.02
GC - R26_Java726_SR6_20140313_1318_B192258
J9CL - 20140313_192258
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en Command-
line arguments: -os win32 -ws win32 -arch x86 -data workspace_kaputt

!ENTRY org.eclipse.e4.ui.workbench 4 0 2014-07-15 13:11:01.940 !
MESSAGE Unable to retrieve the bundle from the URI:
bundleclass://org.eclipse.e4.tools.emf.liveeditor/
org.eclipse.e4.tools.emf.liveeditor.OpenLiveDialogHandler

!ENTRY org.eclipse.rse.ui 4 0 2014-07-15 13:11:03.292 !MESSAGE
CommunicationsDaemon, IOException occured during communications daemon
request !STACK 0
java.net.BindException: Address already in use: JVM_Bind
at java.net.DualStackPlainSocketImpl.bind0(Native Method)
at
java.net.DualStackPlainSocketImpl.socketBind
(DualStackPlainSocketImpl.java:117)
at
java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:406)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:209)
at java.net.ServerSocket.bind(ServerSocket.java:453)
at java.net.ServerSocket.<init>(ServerSocket.java:257)
at java.net.ServerSocket.<init>(ServerSocket.java:148)
at

com.ibm.etools.iseries.subsystems.qsys.api.SystemCommunicationsDaemon.run

(SystemCommunicationsDaemon.java:161)

!ENTRY org.eclipse.jface 4 0 2014-07-15 13:11:03.525 !MESSAGE Unable
to resolve plug-in "platform:/plugin/biz.isphere.core/icons/
message_file_search.png".
!STACK 0
java.io.IOException: Unable to resolve plug-in "platform:/plugin/
biz.isphere.core/icons/message_file_search.png".
at
org.eclipse.core.internal.runtime.PlatformURLPluginConnection.parse
(PlatformURLPluginConnection.java:64)
at
org.eclipse.core.internal.runtime.PlatformURLPluginConnection.resolve
(PlatformURLPluginConnection.java:75)
at
org.eclipse.core.internal.boot.PlatformURLHandler.openConnection
(PlatformURLHandler.java:67)
at

org.eclipse.osgi.framework.internal.protocol.URLStreamHandlerProxy.openConnection

(URLStreamHandlerProxy.java:112)
at java.net.URL.openConnection(URL.java:983)
at
org.eclipse.core.internal.runtime.PlatformURLConverter.toFileURL
(PlatformURLConverter.java:33)
at
org.eclipse.core.runtime.FileLocator.toFileURL(FileLocator.java:206)
at
org.eclipse.jface.resource.URLImageDescriptor.getFilePath
(URLImageDescriptor.java:137)
at
org.eclipse.jface.resource.URLImageDescriptor.createImage
(URLImageDescriptor.java:157)
at
org.eclipse.jface.resource.ImageDescriptor.createImage
(ImageDescriptor.java:227)
at
org.eclipse.jface.resource.ImageDescriptor.createImage
(ImageDescriptor.java:205)
at
org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.getImage
(SWTPartRenderer.java:178)
at
org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.createTab
(StackRenderer.java:767)
at

org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer.processContents

(LazyStackRenderer.java:134)
at