Cannot get past Existing LANSA Communications Directory prompt in Setup during upgrade to 11.0

Date:6 February 2006
Product/Release:LANSA for iSeries V11.0
Abstract:If the communications directory name in data area DCXLOADA01 is blank, the installer will not accept any value entered into the communications directory prompt
Submitted By:LANSA Technical Support

Description:

During an upgrade from LANSA V10.0 to V11.0, one of the install screens will prompt for the Existing LANSA Communications Directory. For most installs this value will be pre-filled and does not need to be changed. However in some cases no default value will appear for this prompt. Furthermore, even if the correct value is entered the Install will reject it and the install cannot continue.

Cause:

This is caused by the communications library path being blank in the data areas that the install uses. The install cannot complete until the data areas contain the correct value. The steps below should be followed to update the communications entry which will allow the install to complete.

Solution:

To correct the data areas, you should use following steps to ensure that the data is updated correctly.

  1. From the command prompt, run LANSA Configure

    From the command prompt, run LANSA Configure
     
  2. From the resulting menu choose COMMS_EXTENSIONS

    From the resulting menu choose COMMS_EXTENSIONS
     
  3. Then from the menu choose COMMS_DEFINITIONS

    Then from the menu choose COMMS_DEFINITIONS
     
  4. Press F21 to enter change mode and enter the correct communications routing table detail. For example, if LANSA is installed to the default location, you might enter "/etc/dc_pgmlib/lroute.dat" (note this may vary and you are advised to determine which directory is used in your configuration before continuing)

    Press F21 to enter change mode and enter the correct communications routing table detail
     
  5. Press enter to accept and then exit the LANSA Configure program.
     
  6. If you display the data area lcoa01 you should see the change has already taken place. The above steps should also create the lroute.dat table in the /etc/dc_pgmlib folder.

    After logging off and signing back on again as qsecofr, you should be able to run the upgrade without any further problems.