WDSC Fixpacks

From MidrangeWiki
Revision as of 21:27, 2 January 2012 by SeanPorterfield (talk | contribs) (link to 7.0.0.8)
Jump to: navigation, search

WDSC 6.0

This IBM site has useful info on installing or updating V6.0...

http://www-1.ibm.com/support/docview.wss?rs=715&context=SSZND2&dc=D410&dc=D430&dc=D400&dc=D420&dc=DB550&q1=WDSC+6.0.1&uid=swg24010773&loc=en_US&cs=utf-8&lang=en


WDSC 7.0

The WDSC support page has information regarding fix packs.

  • To install a WDSC fixpack, you cannot use the Workbench's Window->Update.
  • You must use the IBM Installation Manager.
  • Start->All programs->IBM Installation Manager. Choose Update Packages.
  • I strongly advise looking at the README before doing this!

How to determine the version of WDSC you are running

  • Start->All Programs->IBM Installation Manager->View Installed Packages gives an XML file that has this URL: C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager\installed.xml

For 7.0.0.4, this shows: 

 IBM® WebSphere® Development Studio Client for iSeries® 
 V 7.0.0.4 (7.0.0.20071003_2001)

For 7.0.0.8, this shows: 

 IBM® WebSphere® Development Studio Client for iSeries® 
 V 7.0.0.8 (7.0.0.20090225_1508)

Fix pack 7.0.0.2


Fix pack 7.0.0.6

Fix pack 6 for WDSC V7.0 was released on or about 24 June 2008. The previous fix pack was fix pack 4: there is no fix pack 3 or 5. Fix packs are cumulative: fix pack 6 contains all previous fixes released in fix packs 1, 2 and 4.

The fix pack can be installed only through the IBM Installation Manager. Installation manager can download the fix pack either real-time, or you can download a .zip file, extract that and point Installation Manager to that location instead of the Web.

Instructions on installing the fix pack are in the release notes cited above. The installation says to stop WDSC and all programs opened by it (like a help session in a browser.) I am personally more cautious and reboot prior to the installation process. Steps I follow:

  • At the end of my work day, visit the IBM .zip file download site above, start the download.
  • Close down WDSC.
  • Make a copy of my workspace folder - all of it.
  • Go home.
  • In the morning, unzip the .zip file to a temporary directory.
    • Fix pack 6 .zip file is 1.16GB, and the unzipped directory is 1.19GB, so have at least 2.5BG of free disk space available to try the .zip method!
  • Once the .zip file is extracted, reboot
  • Start → All Programs → IBM Installation Manager
  • Don't choose Update! Instead, choose File → Preferences → Repositories.
    • Add a new repository and drill down into your temporary directory until you find wdsc\updates\repository.config
  • Start the update. On my machine, it took about an hour to complete.
  • The first time you start WDSC will take longer (maybe 10 minutes more.)

User reports

  • 2008-06-25 Running user actions result in RSEG1003U An unexpected exception has occurred. Both WDSC and WDSC AE. 5 users. APAR SE32901 FIXED 14 July 2008 by iFix001. Run Installation manager to get the update.
  • 'Seems snappier' 1 user.

Fix pack 7.0.0.7

There was no fix pack 7.

Fix pack 7.0.0.8

Fix pack 8 for WDSC V7.0 was released on or about 5 March 2009. Fix packs are cumulative: fix pack 8 contains all previous fixes released in fix packs 1, 2, 4 and 6.

The fix pack can be installed only through the IBM Installation Manager. Installation manager can download the fix pack either real-time, or you can download a .zip file, extract that and point Installation Manager to that location instead of the Web. Installation Manager will need to upgrade itself to version 1.2.1; mine upgraded to 1.3.0 when I started it on 5 Mar 2009.

User reports

Several people have reported that Fixpack 8 breaks user actions, returning RSEG1003U An unexpected error has occurred 

java.lang.NullPointerException
java.lang.NullPointerException
   at com.ibm.etools.systems.core.ui.uda.SystemUDActionSubsystem.doCommandSubstitutions(Unknown Source)
   at com.ibm.etools.systems.core.ui.uda.SystemUDActionSubsystem.run(Unknown Source)
   at com.ibm.etools.systems.core.ui.uda.SystemUDAsBaseAction.run(Unknown Source)
   at org.eclipse.jface.action.Action.runWithEvent(Unknown Source)
   at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(Unknown Source)
   at org.eclipse.jface.action.ActionContributionItem.access$2(Unknown Source)
   at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(Unknown Source)
   at org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
   at org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
   at org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)
   at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
   at org.eclipse.ui.internal.Workbench.runEventLoop(Unknown Source)
   at org.eclipse.ui.internal.Workbench.runUI(Unknown Source)
   at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown Source)
   at org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source)
   at org.eclipse.ui.internal.ide.IDEApplication.run(Unknown Source)
   at org.eclipse.core.internal.runtime.PlatformActivator$1.run(Unknown Source)
   at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Unknown Source)
   at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Unknown Source)
   at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
   at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at org.eclipse.core.launcher.Main.invokeFramework(Unknown Source)
   at org.eclipse.core.launcher.Main.basicRun(Unknown Source)
   at org.eclipse.core.launcher.Main.run(Unknown Source)
   at org.eclipse.core.launcher.Main.main(Unknown Source)
  • 17 Mar 2009, IBM releases Interim Fix 001 which looks like it takes care of the above issue. Use Installation Manager to update.

WDSC 7.1

Fix pack 7.1.0.3

To install the fix pack, start the IBM Installation Manager and click on 'Update'.

The fix pack is also available as a downloadable zip (130MB). You will find it on the Download section of the support site soon. You can also download the zip from:

http://download.boulder.ibm.com/ibmdl/pub/software/awdtools/rdi/v71/7103/zips/rdi-7.1.0.3.zip

WDSC 7.5

Fix pack 7.5.0.1

The fix pack provides documentation for the Rational Team Concert for i - Client feature.

To install the fix pack, start the IBM Installation Manager and click on 'Update'.

The fix pack is also available as a downloadable zip (2MB). You will find it on the Download section of the support site soon. You can also download the zip from: http://download.boulder.ibm.com/ibmdl/pub/software/awdtools/rdi/v75/7501/zips/rdi-7.5.0.1.zip

Later Fix packs

More recent fix packs are documented at the RDi article

Retrieved from "https://wiki.midrange.com/index.php?title=WDSC_Fixpacks&oldid=11355"