× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. WDSCI-L
  3. February 2016

Outline view and old code

" spend SOME time each day on conversion, even 15 minutes can accomplish a lot. Make a plan and stick to it as much as possible" .... Our company has to abide by JSOX rules and regulations (the Japanese equivalent of Sarbanes Oxley). Unless something is broken, no changes can be made without an approved request from a user, and all changes have to be approved by the requestor/owner of the process before putting into production, so no program can be converted unless it is being modified for another purpose. That doesn't preclude the developer from converting the program in their personal library for analysis however.

----------------------------------------------------------------------

message: 1
date: Wed, 24 Feb 2016 18:23:04 +0000
from: Duane Scott <dscott@xxxxxxxxxxx>
subject: Re: [WDSCI-L] Outline view and old code

Exactly right.

So many rules I could tell you, but bottom line is do only what is needed, each time it's needed. The old adage "if it ain't broke..." doesn't exactly apply, because being as old as it is, it COULD be considered "broke". But that's a philosophy for later.

1) if you have to change it, convert it first. I am pretty sure that RPGIII conversion to RPGIV (CVTRPGSRC) still works for a vast percentage of code. If it can't be converted by that, then don't spend too much time figuring it out unless you have the time. After that, you'll at least have the outline available, even if you don't use the converted code. Finding your way back into the original isn't that hard.

2) spend SOME time each day on conversion, even 15 minutes can accomplish a lot. Make a plan and stick to it as much as possible. But don't bother unless the program is used.

3) Don't do wholesale conversion. That's and elephant to be sure.

4) I'm not familiar with change management systems, but if you can, go outside of it and start over with a new program name. Keep the old stuff so you can refer to it, and if the CM system will allow, link it to the new name for referral.

5) Consider it a "5 year plan". As Bridgitta quotes "Shoot for the moon, even if you miss, you'll land among the stars." (Les Brown) So what if you don't get every last stinkin' line of code rewritten, you'll be farther along than you were if you never took another step.

I'll almost guarantee you will save time on programming later if you do it. Now whether or not you save as much as you spend, that's unknown, and I wouldn't recommend trying to keep track. However, my estimates are that totally free format saves about 40% on keystrokes alone. Not having to figure out RPGIII, "priceless".


Duane


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Wednesday, February 24, 2016 12:57 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Outline view and old code

Man, did I ever have to hunt for that one!!

Do I take it rightly that you refer to tackling things 1 small bite at a time?

If so, I would say we have a pretty large code base, some written 25 or more years ago. There's no way to justify eating even a little of THAT elephant, seems to me - we have too many current requests to fulfill.

Now I know some strategies - convert CLP to CLLE, maybe. (Of course, CLLE is also not well-supported in the outline.) And one COULD do an RPG conversion, I suppose. But that can really mess up change-management stuff, the history gets pretty lost in some of those products.

So it's just not always practical to make a wholesale change just for the sake of the change.

Now ask me about stuff in code that I've not seen in those 25 years, maybe hardly when I was in computer school!!

Cheers
Vern

On 2/24/2016 11:35 AM, Duane Scott wrote:
"Eat an elephant"

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Terry
Hertel
Sent: Wednesday, February 24, 2016 12:24 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] Outline view and old code

" Now if it would work with CL and RPGIII, etc." ..... I agree. Our third-party ERP and financial systems were written in RPGIII and have been heavily modified. There is no way we would spend the time or money to convert those systems to RPGIV.
------------------------------

message: 4
date: Tue, 23 Feb 2016 22:11:52 -0600
from: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
subject: Re: [WDSCI-L] Outline view and old code

I use the outline a lot. Yes, I could use the filter view to see only the procedure starts & ends, but the outline is better.

I find the usage bits to be very helpful - I mean the lists of which lines the procedures, fields, etc., are used. For fields, some are marked with M or D (I think the latter is done), which is very like what the listing would have. In addition, it is easy to tell when some element is not being used. I've been known to have an extra parameter or 2, and this helps me clean up things.

I do find I can move about more quickly - much faster than searching for a name of a procedure or whatever else.

Now if it would work with CL and RPGIII, etc.

Vern

--
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.

________________________________
________________________________
CONFIDENTIALITY NOTICE: This electronic message transmission is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. If you have received this transmission, but are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this information is strictly prohibited. If you have received this e-mail in error, please contact NALC Health Benefit Plan at 703-729-4677 and delete and destroy the original message and all copies.





--
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.

________________________________
________________________________
CONFIDENTIALITY NOTICE: This electronic message transmission is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. If you have received this transmission, but are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this information is strictly prohibited. If you have received this e-mail in error, please contact NALC Health Benefit Plan at 703-729-4677 and delete and destroy the original message and all copies.






------------------------------

message: 2
date: Wed, 24 Feb 2016 13:27:00 -0500
from: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
subject: Re: [WDSCI-L] Resistance to using RDi

Agreed.

I also find that outline is invaluable when a large number of /Copy protos and contestants are in the mix. One project I?m working on has literally hundreds of protos, DS templates, and constants. Even though the code I?m writing may only be a couple of hundred lines it is still useful to know which functions I need, what the DS comprise and what parms are needed. Similarly for field from external print files etc.

Only time I _don?t_ need it is when writing a simple proof-of-concept or snippet for a magazine article etc.


On Feb 23, 2016, at 4:38 PM, Sam_L <lennon_s_j@xxxxxxxxxxx> wrote:

There is a lot of ancient, hard-to-decipher code out there that has to be maintained. This is where, in my experience anyway, RDi, and the outline view, really help. If you have such code, IMHO you need RDi.

(Though I also like it for new code...)

Sam

On 2/23/2016 3:10 AM, Scott Klement wrote:

People gush about stuff like the outline view, ... I think it's mainly useful if you're
stuck in a shop that writes ancient, hard-to-decipher, code.

--
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.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com



------------------------------

message: 3
date: Wed, 24 Feb 2016 13:38:16 -0500
from: "Mike Hockings" <hockings@xxxxxxxxxx>
subject: Re: [WDSCI-L] Password issue on Windows 10


Try creating a new workspace?


Mike Hockings, M.Eng., P.Eng.
IBM Rational Developer for System z and Power Systems Software Technical
Support
IBM Canada Ltd. Laboratory




From: Bob Schuch <bschuch@xxxxxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date: 2016-02-24 12:19
Subject: [WDSCI-L] Password issue on Windows 10
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



Hoping the community may be able to point me in the right direction. The
internal support staff has not been able to resolve this for at least two
weeks now. It is forcing me to re-enter my password EVERY day for EVERY
connection even though I check the "Remember me" box every time. Getting
the following errors in RDi when attempting to use/save my connection
passwords:

Unexpected error updating password.
org.eclipse.equinox.security.storage.StorageException: No password
provided.
at
org.eclipse.equinox.internal.security.storage.SecurePreferences.put
(SecurePreferences.java:237)
at
org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.put
(SecurePreferencesWrapper.java:110)
at org.eclipse.rse.core.PasswordPersistenceManager.basicPut
(PasswordPersistenceManager.java:471)
at
org.eclipse.rse.core.PasswordPersistenceManager.updatePassword
(PasswordPersistenceManager.java:550)
at org.eclipse.rse.core.PasswordPersistenceManager.add
(PasswordPersistenceManager.java:615)
at
org.eclipse.rse.core.subsystems.AuthenticatingConnectorService.savePassword
(AuthenticatingConnectorService.java:171)
at
org.eclipse.rse.ui.subsystems.StandardCredentialsProvider.acquireCredentials
(StandardCredentialsProvider.java:236)
at
org.eclipse.rse.core.subsystems.AuthenticatingConnectorService.acquireCredentials
(AuthenticatingConnectorService.java:210)
at org.eclipse.rse.core.subsystems.SubSystem.promptForPassword
(SubSystem.java:2660)
at org.eclipse.rse.core.subsystems.SubSystem$1.run
(SubSystem.java:2554)
at org.eclipse.swt.widgets.Synchronizer.syncExec
(Synchronizer.java:187)
at org.eclipse.ui.internal.UISynchronizer.syncExec
(UISynchronizer.java:156)
at org.eclipse.swt.widgets.Display.syncExec(Display.java:4734)
at org.eclipse.rse.core.subsystems.SubSystem.connect
(SubSystem.java:2550)
at
com.ibm.etools.iseries.subsystems.qsys.QSYSAbstractSubSystem.checkIsConnected
(QSYSAbstractSubSystem.java:177)
at
com.ibm.etools.iseries.subsystems.qsys.QSYSAbstractSubSystem.verifyConnected
(QSYSAbstractSubSystem.java:228)
at
com.ibm.etools.iseries.subsystems.qsys.objects.QSYSObjectSubSystem.internalResolveFilterString
(QSYSObjectSubSystem.java:222)
at
com.ibm.etools.iseries.subsystems.qsys.api.IBMiConnection.internalResolveList
(IBMiConnection.java:492)
at
com.ibm.etools.iseries.subsystems.qsys.api.IBMiConnection.listMembers
(IBMiConnection.java:788)
at
com.ibm.etools.iseries.subsystems.qsys.api.IBMiConnection.getMember
(IBMiConnection.java:953)
at
com.ibm.etools.iseries.subsystems.qsys.api.IBMiConnection.getMember
(IBMiConnection.java:945)
at
com.ibm.etools.iseries.rse.ui.dialogs.QSYSOpenMemberDialog.processOK
(QSYSOpenMemberDialog.java:198)
at org.eclipse.rse.ui.dialogs.SystemPromptDialog.buttonPressed
(SystemPromptDialog.java:926)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected
(Dialog.java:619)
at org.eclipse.swt.widgets.TypedListener.handleEvent
(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent
(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent
(Display.java:4353)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061)
at org.eclipse.swt.widgets.Display.runDeferredEvents
(Display.java:4172)
at org.eclipse.swt.widgets.Display.readAndDispatch
(Display.java:3761)
at org.eclipse.jface.window.Window.runEventLoop
(Window.java:832)
at org.eclipse.jface.window.Window.open(Window.java:808)
at
com.ibm.etools.iseries.rse.ui.actions.QSYSOpenMemberAction.run
(QSYSOpenMemberAction.java:75)
at
com.ibm.etools.iseries.rse.ui.actions.QSYSOpenMemberActionWindowDelegate.run
(QSYSOpenMemberActionWindowDelegate.java:59)
at
org.eclipse.ui.internal.handlers.ActionDelegateHandlerProxy.execute
(ActionDelegateHandlerProxy.java:299)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute
(E4HandlerProxy.java:90)
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:507)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute
(MethodRequestor.java:55)
at
org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass
(InjectorImpl.java:247)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke
(InjectorImpl.java:229)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke
(ContextInjectionFactory.java:132)
at
org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute
(HandlerServiceHandler.java:149)
at org.eclipse.core.commands.Command.executeWithChecks
(Command.java:499)
at
org.eclipse.core.commands.ParameterizedCommand.executeWithChecks
(ParameterizedCommand.java:508)
at
org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler
(HandlerServiceImpl.java:210)
at
org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand
(KeyBindingDispatcher.java:286)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press
(KeyBindingDispatcher.java:507)
at
org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent
(KeyBindingDispatcher.java:558)
at
org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings
(KeyBindingDispatcher.java:378)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.access
$0(KeyBindingDispatcher.java:324)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher
$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:86)
at org.eclipse.swt.widgets.EventTable.sendEvent
(EventTable.java:84)
at org.eclipse.swt.widgets.Display.filterEvent
(Display.java:1262)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1060)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1070)
at org.eclipse.swt.widgets.Widget.sendKeyEvent
(Widget.java:1112)
at org.eclipse.swt.widgets.Widget.sendKeyEvent
(Widget.java:1108)
at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1529)
at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4722)
at org.eclipse.swt.widgets.Tree.WM_CHAR(Tree.java:6028)
at org.eclipse.swt.widgets.Control.windowProc
(Control.java:4610)
at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:6024)
at org.eclipse.swt.widgets.Display.windowProc
(Display.java:5036)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native
Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage
(OS.java:2549)
at org.eclipse.swt.widgets.Display.readAndDispatch
(Display.java:3759)
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:507)
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)

Secure storage was unable to retrieve the master password. If secure
storage was created using a different Windows account, you'll have to
switch back to that account. Alternatively, you can use the password
recovery, or delete and re-create secure storage.
org.eclipse.equinox.security.storage.StorageException: Secure storage was
unable to retrieve the master password. If secure storage was created using
a different Windows account, you'll have to switch back to that account.
Alternatively, you can use the password recovery, or delete and re-create
secure storage.
at
org.eclipse.equinox.internal.security.win32.WinCrypto.getPassword
(WinCrypto.java:62)
at
org.eclipse.equinox.internal.security.storage.PasswordProviderModuleExt.getPassword
(PasswordProviderModuleExt.java:35)
at
org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getModulePassword
(SecurePreferencesRoot.java:259)
at
org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getPassword
(SecurePreferencesRoot.java:224)
at
org.eclipse.equinox.internal.security.storage.SecurePreferences.put
(SecurePreferences.java:224)
at
org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.put
(SecurePreferencesWrapper.java:110)
at org.eclipse.rse.core.PasswordPersistenceManager.basicPut
(PasswordPersistenceManager.java:471)
at
org.eclipse.rse.core.PasswordPersistenceManager.updatePassword
(PasswordPersistenceManager.java:550)
at org.eclipse.rse.core.PasswordPersistenceManager.add
(PasswordPersistenceManager.java:615)
at
org.eclipse.rse.core.subsystems.AuthenticatingConnectorService.savePassword
(AuthenticatingConnectorService.java:171)
at
org.eclipse.rse.ui.subsystems.StandardCredentialsProvider.acquireCredentials
(StandardCredentialsProvider.java:236)
at
org.eclipse.rse.core.subsystems.AuthenticatingConnectorService.acquireCredentials
(AuthenticatingConnectorService.java:210)
at org.eclipse.rse.core.subsystems.SubSystem.promptForPassword
(SubSystem.java:2660)
at org.eclipse.rse.core.subsystems.SubSystem$1.run
(SubSystem.java:2554)
at org.eclipse.swt.widgets.Synchronizer.syncExec
(Synchronizer.java:187)
at org.eclipse.ui.internal.UISynchronizer.syncExec
(UISynchronizer.java:156)
at org.eclipse.swt.widgets.Display.syncExec(Display.java:4734)
at org.eclipse.rse.core.subsystems.SubSystem.connect
(SubSystem.java:2550)
at
com.ibm.etools.iseries.subsystems.qsys.QSYSAbstractSubSystem.checkIsConnected
(QSYSAbstractSubSystem.java:177)
at
com.ibm.etools.iseries.subsystems.qsys.QSYSAbstractSubSystem.verifyConnected
(QSYSAbstractSubSystem.java:228)
at
com.ibm.etools.iseries.subsystems.qsys.objects.QSYSObjectSubSystem.internalResolveFilterString
(QSYSObjectSubSystem.java:222)
at
com.ibm.etools.iseries.subsystems.qsys.api.IBMiConnection.internalResolveList
(IBMiConnection.java:492)
at
com.ibm.etools.iseries.subsystems.qsys.api.IBMiConnection.listMembers
(IBMiConnection.java:788)
at
com.ibm.etools.iseries.subsystems.qsys.api.IBMiConnection.getMember
(IBMiConnection.java:953)
at
com.ibm.etools.iseries.subsystems.qsys.api.IBMiConnection.getMember
(IBMiConnection.java:945)
at
com.ibm.etools.iseries.rse.ui.dialogs.QSYSOpenMemberDialog.processOK
(QSYSOpenMemberDialog.java:198)
at org.eclipse.rse.ui.dialogs.SystemPromptDialog.buttonPressed
(SystemPromptDialog.java:926)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected
(Dialog.java:619)
at org.eclipse.swt.widgets.TypedListener.handleEvent
(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent
(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent
(Display.java:4353)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061)
at org.eclipse.swt.widgets.Display.runDeferredEvents
(Display.java:4172)
at org.eclipse.swt.widgets.Display.readAndDispatch
(Display.java:3761)
at org.eclipse.jface.window.Window.runEventLoop
(Window.java:832)
at org.eclipse.jface.window.Window.open(Window.java:808)
at
com.ibm.etools.iseries.rse.ui.actions.QSYSOpenMemberAction.run
(QSYSOpenMemberAction.java:75)
at
com.ibm.etools.iseries.rse.ui.actions.QSYSOpenMemberActionWindowDelegate.run
(QSYSOpenMemberActionWindowDelegate.java:59)
at
org.eclipse.ui.internal.handlers.ActionDelegateHandlerProxy.execute
(ActionDelegateHandlerProxy.java:299)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute
(E4HandlerProxy.java:90)
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:507)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute
(MethodRequestor.java:55)
at
org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass
(InjectorImpl.java:247)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke
(InjectorImpl.java:229)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke
(ContextInjectionFactory.java:132)
at
org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute
(HandlerServiceHandler.java:149)
at org.eclipse.core.commands.Command.executeWithChecks
(Command.java:499)
at
org.eclipse.core.commands.ParameterizedCommand.executeWithChecks
(ParameterizedCommand.java:508)
at
org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler
(HandlerServiceImpl.java:210)
at
org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand
(KeyBindingDispatcher.java:286)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press
(KeyBindingDispatcher.java:507)
at
org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent
(KeyBindingDispatcher.java:558)
at
org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings
(KeyBindingDispatcher.java:378)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.access
$0(KeyBindingDispatcher.java:324)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher
$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:86)
at org.eclipse.swt.widgets.EventTable.sendEvent
(EventTable.java:84)
at org.eclipse.swt.widgets.Display.filterEvent
(Display.java:1262)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1060)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1070)
at org.eclipse.swt.widgets.Widget.sendKeyEvent
(Widget.java:1112)
at org.eclipse.swt.widgets.Widget.sendKeyEvent
(Widget.java:1108)
at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1529)
at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4722)
at org.eclipse.swt.widgets.Tree.WM_CHAR(Tree.java:6028)
at org.eclipse.swt.widgets.Control.windowProc
(Control.java:4610)
at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:6024)
at org.eclipse.swt.widgets.Display.windowProc
(Display.java:5036)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native
Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage
(OS.java:2549)
at org.eclipse.swt.widgets.Display.readAndDispatch
(Display.java:3759)
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:507)
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)

Is there something specific to which I can point the support personnel to
get this resolved? Is this related to the authority on my machine (I am an
Administrator on my computer)?

Any help would be appreciated.

Bob Schuch | U.S. Xpress, Inc.
Programmer/Analyst
4080 Jenkins Road | Chattanooga, TN 37421
Office: 423 510 3791
Fax: 423 510 4002
bschuch@xxxxxxxxxxxx | www.usxpress.com

SERVICE THAT MATTERS - DRIVEN BY INNOVATION
--
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 96
***************************************

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.