Component fixes

Fixpack files and installation

The fixpack is packaged in multiple files that mirror installable components in the original V5.0 intallation. For example, there is a fixpack file for the client, a fixpack file for the Server Runtime feature, etc. The fixpack files are further packaged according to the target operating system. The fixpack files will overlay files in the directory tree structure where your current VisualAge Smalltalk is installed.

Fixpack Files

Installation instructions for development systems

You can install the manager and client fixpacks in a team development environment or as a standalone installation.

Team development environment

To install VisualAge Smalltalk in a team development environment, a system administrator should install the manager library fixpack on a network attached server computer. The individual developers can then install the client code fixpack locally on their machine and connect to the manager library using EMSRV.

Standalone

If you are working independently of other developers you can install both the manager library fixpack and the client code fixpack on one machine. It is recommended that you install the manager library fixpack before installing the client fixpack.

1. Back up your VisualAge installation.
   1. Back up your manager directory tree.
   2. Back up your client directory tree.
2. Make note of the features that you currently have loaded. You will need to re-load them once the fixpack files are installed.
3. Make sure your VisualAge Smalltalk image is not running.

1. Download the appropriate fixpack files to the directory where your VisualAge Smalltalk installation resides. For OS/2 and Windows, this is the directory you specified when installing VisualAge Smalltalk V5.0; for AIX, HP-UX, and Solaris, this is the /opt/IBMvast directory. For Server Runtime installations, this is where the esvio.exe program resides (on OS/2 and NT).
2. Unzip the fixpack files using whatever option your unzip program provides to restore the subdirectory structure of the fixpack file. Be sure that your unzip program restores the files with the same case that they were zipped with in the fixpack, or use whatever option your unzip program provides to restore the case of the zipped fixpack files. For example:
   • Winzip

     
     Check the Use File folders option to restore the file directory structure of the zipped file.

   • Pkunzip

     
     Use the -d option to restore the file directory structure of the zipped file.

     pkunzip -d w501mgr.zip

   • INFO_Zip

     
     Use the -d option to restore the file directory structure of the zipped file.

     Unzip -d w501mgr.zip

   • Uncompress and Untar

     zcat a501cln.tar|tar -xvf  -

3. Start your image. Once the image has finished loading, from the System Transcript menu bar, select Tools > Load/Unload Features.
4. Load the VisualAge base and any features that were loaded before you installed the fixpack files.
5. Refer to the Component Fix Notes for special instructions relating to specific fixes.
6. Save your image. This completes the fixpack installation.

After installing the fixpack:

1. If you install a new feature off the product CD, you must re-install both the client and manager fixpacks.
2. Do not purge any of the VisualAge 5.0.1 fixpack maps. Purging the maps will cause the Load Features function to fail.

Installation instructions for Server Runtime

Before installing the fixpack, backup your VisualAge Smalltalk Server Runtime directory tree.

To install the fixpack, follow these steps:

1. Download the appropriate fixpack files to the directory where your VisualAge Smalltalk installation resides. For OS/2 and Windows, this is the directory you specified when installing VisualAge Smalltalk Server Runtime V5.0; for AIX and Solaris, this is the /opt/IBMvast/server directory.
2. Unzip (or uncompress and untar) the fixpack files using the option necessary to restore the subdirectory structure of the fixpack file. For example:
   • Winzip

     
     Check the Use File folders option to restore the file directory structure of the zipped file.

   • Pkunzip

     
     Use the -d option to restore the file directory structure of the zipped file.

     pkunzip -d w501mgr.zip

   • INFO-Zip

     
     Use the -d option to restore the file directory structure of the zipped file.

     Unzip -d w501mgr.zip

   • Uncompress and untar

     zcat a501cln.tar|tar -xvf  -

Windows 2000 Support

At the time this fixpack was created, not all VisualAge Smalltalk features were supported in Windows 2000. In addition, some prerequisite software levels are changed when running in Windows 2000. Please refer to VisualAge Smalltalk web page for the latest information on supported features and prerequisites.

Details for each are given in this section.

• Windows 2000 Support -- Base
• Windows 2000 Support -- Server
• Windows 2000 -- EMSRV

Windows 2000 Support -- Base

• When clicking on a menu bar item, the menu will occasionally be only partially displayed. This generally happens when clicking in the lower right quadrant of the imaginary box surrounding the menu item label. To bypass this problem, click in the center of this imaginary box. This problem will be corrected in a future release of VisualAge Smalltalk.
• The VisualAge Smalltalk Install program does not correctly setup the shortcuts in the VisualAge Smalltalk program folder. This problem will be corrected in the next release of VisualAge Smalltalk. To bypass this problem, manually edit the Development Image and Unlock Client shortcuts as follows:
  1. Development Image shortcut
     • Right-click on the Development Image shortcut and select Properties from the popup menu.
     • Set the Target field to:

       <varoot>\bin\abt.exe

     • Set the Start In field to:

       <varoot>\image

     • Click OK.
  2. Unlock Client shortcut
     • Right-click on the Unlock Client shortcut and select Properties from the popup menu.
     • Set the Target field to:

       <varoot>\bin\nodialog.exe -iunlock.icx "-default:<varoot>\image\abt.ini"

     • Set the Start In field to:

       <varoot>\unlock

     • Click OK.
     where <varoot> is the install directory for VisualAge Smalltalk (for example, c:\vast50).

Windows 2000 User Interface

Windows 2000 Support -- Server

• The VisualAge Smalltalk Install program does not setup the shortcuts in the VisualAge Smalltalk program folder correctly. This problem will be corrected in the next release of VisualAge Smalltalk. To bypass the problem, manually edit the Unlock Server Runtime shortcut as follows:
  • Right-click on the Unlock Server Runtime shortcut and select Properties from the popup menu
  • Set the Target field to:

    <varoot>\bin\nodialog.exe -iunlock.icx "-default:<varoot>\image\esvio.ini"

  • Set the Start In field to:

    <varoot>\unlock

  • Click OK,
  where <varoot> is the install directory for VisualAge Smalltalk (for example, c:\vast50)

Windows 2000 -- EMSRV

Warp Server for e-Business Support

Component fixes

APARs

Problems found by other sources

Component Fix Notes

Domino Y2K Fix

In order to override this behavior, add an entry in the INI file's DominoConnection section with key CenturyCutoff and a 2 digit value. Set the 2-digit value to the last 2 digits of the first year to be interpreted as belonging to the previous century. For example, the following code will cause the year strings from 00 to 79 to belong to the current century and the year strings from 80 through 99 to belong to the previous century.

 [DominoConnection] 
 CenturyCutoff =  80

 [DominoConnection] 
 CenturyCutoff = 20

HTTP Status Code Fix

transferToYahoo         
| trans |       
trans := (self subpartNamed: 'page1')  abtHtmlTransaction.      
trans response statusCode: 301 text: " 
trans response location: 'http://www.yahoo.com'.

To capture this fix, replace the abtwsi.jar file in the \servlets subdirectory of your application server. Unload and reload the servlet com.ibm.abt.web.servlet.Router in order to pick up the updated code. Alternatively, you can stop and restart your web server.

ABTWSI.JAR is uppercase in \webconn directory

To reinstall the abtwsi.jar file on OS/2 and Windows, delete or rename the existing ABTWSI.JAR file before unzipping the Server Runtime fix pack.

If you forget to delete ABTWSI.JAR before you installed the fixpack, copy the abtwsi.jar file to the /servlets directory of the web server with the file name as lowercase. For example:

copy d:\vast\webconn\ABTWSI.JAR  d:\websphere\appserver\servlets\abtwsi.jar

Missing Source Code for some applications in mgr50.dat

1. Start a development image
2. Select Tools > Load/Unload Features from the System Transcript menu or Tools > Load/Unload Features from the Visual Organizer menu.
3. Select "5.0.1 Fixpack Source Code Fix" in the left-hand list and move it to the right-hand list.
4. Select OK.

• This feature will never appear as a loaded feature in the Load/Unload Features dialog.
• After the first developer has loaded this feature, it will not appear as an unloaded feature for that developer or any other developer who is connected to the same manager library.

Packaging Runtime as ICs

• When you unpack the client fixpack over a V5.0 client, some of the snapshot files in the <varoot>\icspkg directory are replaced. The modified snapshots correspond to sets of changed Smalltalk code in the fixpack. Before you can repackage your ICs that depend on these modified snapshot files, you will need to load the fixpack code into your development image(s). This is because the timestamps of applications in the image must match the timestamps held in the snapshot files in the <varoot>\icspkg directory.
• When you unpack the client fixpack over a V5.0 client, a new runtime IC directory, <varoot>\ics501 is created. This directory contains the set of updated ICs FOR USE WITH RUNTIME IMAGES ONLY. You MUST NOT copy these ICs into the <varoot>\icsrun directory. If you do, your development image(s) will not start up. An image (development or runtime) is bound FOREVER to the set of ICs used to build it.

1. Copy all the files in your <varoot>\icsrun directory to your <runtimeroot>\icsrun directory.
2. Copy all the files in your <varoot>\ics501 directory to your <runtimeroot>\icsrun directory. This will replace older ICs with newer ICs.
3. Update the IC_ROOT= line in your runtimeapp.ini file to point to your <runtimeroot>\icsrun directory. For example:

   IC_ROOT=d:\myruntimeapp\icsrun

4. Package your runtime application as ICs specifying your <runtimeroot>\<imagedirectory>.

ULC Files

For Windows:

• w501cln.zip -- Contains the Smalltalk development code for ULC.
• w501mgr.zip -- Contains the Smalltalk manager library code for ULC.
• w501ulc.zip -- Contains the UI Engine and Samples.

• o501cln.zip -- Contains the Smalltalk development code for ULC.
• w501mgr.zip -- Contains the Smalltalk manager library code for ULC.
• o501ulc.zip -- Contains the UI Engine and Samples.

Additional Fixes provided on the web

EMSRV for Netware

Please reference fix 13154.

CICS samples for non-HPFS OS/2

ftp://ps.boulder.ibm.com/ps/products/visualage/fixes/v5.0/

Please reference fix 13171.

Walkback on UNIX when packaging reusable ICs

ftp://ps.boulder.ibm.com/ps/products/visualage/fixes/v5.0/

Please reference fix 13093.

Other information