SE57112: RATIONAL DEVELOPER FOR I SERIES - RDI - FILES MAY NOT BE SYNCHRONIZED WHEN WORKSPACE IS CLOSED WITHOUT FIRST SAVING

Rational Developer for i 9.0.1

APAR status

• Closed as program error.

Error description

• RDi v900
  If a user closes the RDi workspace without first saving files
  that have been changed the files may not be written to the
  iSeries at that time.
  When the workspace is opened the next time the files are
  then written to the host and it may overwrite files without
  being prompted to overwrite.  This may cause data to be lost
  in the files that have been changed by others.
  In the <workspace>\.metadata\.log file the following exception
  !ENTRY org.eclipse.rse.ui 4 0 2013-11-06 10:05:30.141
  !MESSAGE QSYSTempFileListener.upload
  !STACK 0
  org.eclipse.swt.SWTException: Invalid thread access
   at org.eclipse.swt.SWT.error(SWT.java:4361)
   at org.eclipse.swt.SWT.error(SWT.java:4276)
   at org.eclipse.swt.SWT.error(SWT.java:4247)
   at org.eclipse.swt.widgets.Display.error(Display.java:1258)
   at
  org.eclipse.swt.widgets.Display.checkDevice(Display.java:764)
   at
  org.eclipse.swt.widgets.Display.getActiveShell(Display.java:1467
  )
   at
  org.eclipse.rse.ui.SystemBasePlugin.getActiveWorkbenchShell(Syst
  emBasePlugin.java:104)
   at
  com.ibm.etools.iseries.rse.ui.resources.QSYSTempFileListener.upl
  oad(QSYSTempFileListener.java:135)
   at
  com.ibm.etools.iseries.rse.ui.resources.QSYSTempFileListener.doR
  esourceSynchronization(QSYSTempFileListener.java:96)
   at
  org.eclipse.rse.files.ui.resources.SystemTempFileListener.synchr
  onizeTempWithRemote(SystemTempFileListener.java:718)
   at
  org.eclipse.rse.files.ui.resources.SystemTempFileListener$SynchR
  esourcesJob.run(SystemTempFileListener.java:313)
   at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
  

Local fix

• Save any open files before closing the RDi workspace.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: RDi users who edit IBM i members             *
  ****************************************************************
  * PROBLEM DESCRIPTION: When ending RDi, editor changes are     *
  *                      not uploaded in change conflict         *
  *                      scenarios.                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Save conflict scenarios can arise when users start RDi with
  previously open edit members. Other users may have changed
  those same members on the host since.
  
  Upon ending RDi the user is prompted to save outstanding
  changes, and if a save conflict scenario exists, RDi tries to
  prompt the user, but the dialog isn't shown, and the member
  changes are not uploaded to the host.
  
  This APAR fix introduces a restriction:
  In a workbench closing state, the "Save As to a different
  member" option on the Save Conflict dialog will be disabled,
  so the user can not choose it.  (It will be shown greyed out.)
  

Problem conclusion

• This problem is fixed in the RDi 9.0.1 update.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  RDI RPG AND COB

• Fixed component ID

  5724Y99RC

Applicable component levels

• R900 PSY

     UP