Migration Guide


Obsolete code

Some VisualAge classes (or class names), or methods in those classes, are no longer supported. To load or run your Version 3.0 applications that use obsolete code for Version 4.5, do the following:

  1. Look through the list of obsolete VisualAge code below. Identify those obsolete classes used by your Version 3.0 applications.
  2. Examine the configuration maps VisualAge, Obsolete Parts for VisualAge classes and ENVY/Image EW R3.0 Compatibility for IBM Smalltalk extended widgets.
  3. Determine which applications in these maps contain obsolete classes used by your Version 3.0 applications.
  4. From the maps, load the pertinent applications.
  5. Try loading your Version 3.0 applications again.
Tipicon
Some of the classes listed below are application classes. If your Version 3.0 application's direct prerequisites include any of the classes below, load the appropriate configuration map and fix your applications so they no longer use obsolete code. Note that this only applies for direct prerequisites, and not for prerequisites well up the tree of prerequisites.

Obsolete VisualAge code

The following classes are themselves obsolete or contain code that is obsolete:

If your application uses these classes, load applications in the configuration map VisualAge, Obsolete Parts that contain obsolete classes used by your Version 3.0 application. Further, if your application uses AbtTableView, follow the steps in Morphing tables after loading the applications.

Obsolete IBM Smalltalk code

The following classes are themselves obsolete or contain code that is obsolete:

If your application uses these classes, load ENVY/Image EW R3.0 Compatibility.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]