| |
Version 12 Release and Installation Notices
| September 3 2010 |
LANSA V12
In V12 EPC851, when executing RDMLX on the IBM i, an error can
be generated stating that
LPCMN.BND does not exist. This can effect RDMLX functions, RDMLX Webevent
functions, RDMLX components running on System i, and WAMs
executing on a System i application server. Refer to Message stating LPCMN.BND not found when executing RDMLX
function/WAM/component on
IBM i
|
| July 30 2010 |
LANSA Composer - V3.0
This item only applies if you installed the LANSA Composer client-runtime version that is compatible with the LANSA Composer server running in a LANSA
V11 SP5 system. If the LANSA system containing the LANSA Composer server is later upgraded to LANSA version 12, then the LANSA Composer client will no longer be able to connect to it. In this event, you can do one of two things:
- uninstall and re-install the affected LANSA Composer clients; OR
- apply Hotfix 001 for LANSA Composer version 3.0 to each affected LANSA Composer client installation.
Hotfix 001 for LANSA Composer version 3.0 is installed with the LANSA Composer client version 3.0. You can find it in file LC_HotFix_3_0_001.zip in the
X_WIN95\X_LANSA\X_LIC\Execute folder. Refer to the file LC_HotFix_3_0_001.doc contained in the zip file for further instructions.
|
| July 30 2010 |
LANSA Composer - V3.0
If you are upgrading from LANSA Composer
version 2.0 and have NOT previously applied Hotfix 002, then you
should complete the following steps to move the .jar files for
your existing Transformation Maps to their new location. Refer
to the following technical note
Important note if upgrading LANSA Composer version 2.0 and have NOT previously applied Hotfix 002 |
| July 23 2010 |
Visual LANSA Framework - V12
Deploying a VLF application from V12,
you may encounter an error on some PCs
that VF_AC006 module cannot be located
or is not a LANSA component. For further
details including a solution, refer to Unable to Load/locate module VF_AC006 error
after deploying a VLF application in V12 |
| July 22 2010 |
Visual LANSA - V12
You may experience the following error during the installation of a V12 Visual LANSA network client onto a Windows 7 or Vista PC.
This error can occur when the V12 Visual LANSA Server that you are connecting to is installed on Windows 2008 64-bit. LANSA has investigated the cause of this fatal error and have reported our findings to Microsoft.
If you encounter this installation error, you should contact your local LANSA vendor for instructions on how to overcome the problem and complete the V12 network client install. |
| July 9 2010 |
Visual LANSA - V12
It is possible to generate an error "LANSA requires this
operating system to have at least SP1
installed" when installing
V12 on Windows 7. Refer to It is possible to generate a compatibility error when installing V12 on
Windows 7 |
| March 29 2010 |
LANSA for iSeries - V12
If your IBM i master system is on V5R4, you must ensure that you are
up to date with the latest CUME and PTFs to avoid any issues during
checkin or checkout. You must get to the latest CUME and PTFs level
before installing V12 to avoid potential problems. If you do not,
you may experience checkin or checkout issues,
for example, objects not available in the IDE after a refresh or
checking out from the master repository or *svrpgm not created during
a checkin and compile. If you encounter any issues during
checkin or checkout, check the joblog on the IBM i for the following
error
MCH3601 X_BASE
From module . . . . . . . . : LPBASE
From procedure . . . . . . : NotifyDependents__12LpInteractorFQ2_6LpBase6ReasonlP8LpObject
Message.. . . . . . . . . . . : Pointer not set for location referenced.
If this error exists, then you will need to apply the very latest CUME and
PTFs.
NOTE: Because this issue is one of re-encapsulation of V6R1 shipped
objects, V12 will need to be reinstalled after applying the latest CUME and
PTFs.
|
| February 1 2010 |
Visual LANSA - V12
V12 provides the option of installing SQL Server 2008 Express as the database. Adaptive Server Anywhere databases are no longer provided.
Use the following tip to migrate your existing database from V11 and ASA to V12 and SQL Server 2008 Express.
Steps to migrate your database from ASA to SQL Server 2008 Express |
| February 1 2010 |
LANSA for iSeries - V12
If your IBM i master system is on V5R4, you must ensure that you are
up to date with the latest CUME and PTFs to avoid any issues during
checkin or checkout. If you experience any checkin or checkout issues,
for example, objects not available in the IDE after a refresh or
checking out from the master repository, ensure that your IBM i CUME
and PTF levels are up to date. |
| February 1 2010 |
Visual LANSA - V12
V12 adds support for FLDX so that numeric enter key behaves like field exit (Tab).
The FLDX parameter of x_run was previously ignored and defaulted to 'N' rather than the correct default of 'Y' as per the documentation.
If you wish the numeric enter key to revert to pre V12 behaviour (Enter key), you can set FLDX=N on the x_run
|
| February 1 2010 |
Visual LANSA - V12
The Visual LANSA General Checklist contains the following check
· If you are installing LANSA on a PC running Windows Vista or Windows 2008 you must have User Account Control ( UAC ) turned OFF.
If UAC is ON, the install process will terminate.
When the install process terminates, the message on the screen will indicate that UAC is the cause. Steps to turn off UAC are available from the Microsoft site at http://technet.microsoft.com/en-us/library/cc709691(WS.10).aspx. Care should be taken when making changes to the UAC and you must be able to log on with or provide the credentials of a member of the local Administrators
group. |
| February 1 2010 |
Visual LANSA - V12
After upgrading to V12, a Visual LANSA network client installation may
not function as expected if the Microsoft Visual C++ 2008 Redistributable is not available on this PC.
Refer to Upgrading Network Clients to V12 - manual intervention may be required
for further details and steps to correct. |
| February 1 2010 |
Visual LANSA - V12
When installing Visual LANSA V12 on Windows 7, you may generate an MS SQL Server 2008 compatibility message indicating that SQL Server 2008 Service Pack 1 should be applied.
If you are using Windows 7 64 bit and SQL Server 2008 Express, you must install the SP1 for SQL Server 2008 Express.
LANSA recommends downloading and applying the Service Pack to avoid any issues during the Visual LANSA install.
Note: you may have to restart the Visual LANSA V12 install if a reboot is required after applying Service Pack 1 to SQL Server 2008 Express
|
| February 1 2010 |
Visual LANSA Framework - V12
The version of the Visual LANSA Framework shipped with V12 doesn't
cater for password length greater than 10 characters or case
sensitivity. Support for these features will be added to the VLF post
V12 GA. |
| February 1 2010 |
Visual LANSA - V12
Object Locking must be enabled in the Visual LANSA system when
using the Deliver to option to deliver to an IBM i remote system. This
requirement has been removed in EPC851
for V12. |
| February 1 2010 |
Visual LANSA - V12
The Visual LANSA V12 Installation can fail if TCP/IP not enabled.
For example, you may have Microsoft SQL Server already installed but if the TCP/IP protocol is not
enabled an installation failure may occur. You can check for this possibility in the following
location:
In SQL Server folder, select SQL Server Configuration manager within the Configration Tools folder. When the SQL Server Configuration manager launches, select SQL Server Network Configuration and then Protocols for <Server name>. TCP/IP should be displayed as Enabled or Disabled. If its set as Disabled, enable this protocol and restart the Visual LANSA Install. Check with your Database Administrator if you require assistance with setting or changing SQL Server protocols. |
| February 1 2010 |
Visual LANSA - V12 & V11
An LX_ConfigurationName error message is issued when installing a V11 Network Client once V12 is installed on the Server.
While attempting to install a V11 Network Client, where the Server machine already has both v11 and v12 configurations, a message stating that the LX_ConfigurationName does not exist in the server registry appears after selecting the configuration to connect to.
This message can be avoided by ensuring that the V11 configuration on the Server is the "current configuration".
Even though the message appears stating that the LX_ConfigurationName does not exist in the registry, this message is not a fatal message and after clicking OK, the install continues. |
Visual LANSA |
September 3, 2010 - V12
In V12 EPC851, when executing RDMLX on the IBM i, an error can
be generated stating that
LPCMN.BND does not exist. This can effect RDMLX functions, RDMLX Webevent
functions, RDMLX components running on System i, and WAMs
executing on a System i application server. Refer to Message stating LPCMN.BND not found when executing RDMLX
function/WAM/component on
IBM i |
July 22, 2010 - V12
You may experience the following error during the installation of a V12 Visual LANSA network client onto a Windows 7 or Vista PC.
This error can occur when the V12 Visual LANSA Server that you are connecting to is installed on Windows 2008 64-bit. LANSA has investigated the cause of this fatal error and have reported our findings to Microsoft.
If you encounter this installation error, you should contact your local LANSA vendor for instructions on how to overcome the problem and complete the V12 network client install. |
July 9, 2010 - V12
It is possible to generate an error "LANSA requires this
operating system to have at least SP1
installed" when installing
V12 on Windows 7. Refer to It is possible to generate a compatibility error when installing V12 on
Windows 7 |
February 1, 2010 - V12
V12 provides the option of installing SQL Server 2008 Express as the database. Adaptive Server Anywhere databases are no longer provided. Use the following tip to migrate your existing database from V11 and ASA to V12 and SQL Server 2008 Express.
Steps to migrate your database from ASA to SQL Server 2008 Express |
February 1, 2010 - V12
V12 deployed runtime applications now require the Visual C++ 2008 Runtime to be installed on the PC. This can be deployed/installed automatically by ticking the "Deploy VC90 Runtime" package setting in the deployment tool. It is now ticked by default in all shipped package templates. However if the deployment package build process involves copying an existing deployment package, then this setting needs to be manually selected.
Failure to include the VC90 Runtime will result in an x_run.exe - Application error similar to "The application was unable to start correctly."
|
February 1, 2010 - V12
The Visual LANSA General Checklist contains the following check.
If you are installing LANSA on a PC running Windows Vista or Windows 2008 you must have User Account Control ( UAC ) turned OFF.
If UAC is ON, the install process will terminate.
When the install process terminates, the message on the screen will indicate that UAC is the cause. Steps to turn off UAC are available from the Microsoft site at http://technet.microsoft.com/en-us/library/cc709691(WS.10).aspx. Care should be taken when making changes to the UAC and you must be able to log on with or provide the credentials of a member of the local Administrators group. |
February 1, 2010 - V12
After upgrading to V12, a Visual LANSA network client installation may
not function as expected if the Microsoft Visual C++ 2008 Redistributable is not available on this PC.
Refer to Upgrading Network Clients to V12 - manual intervention may be required
for further details and steps to correct. |
February 1, 2010 - V12
When installing Visual LANSA V12 on Windows 7, you may generate an MS SQL Server 2008 compatibility message indicating that SQL Server 2008 Service Pack 1 should be applied.
If you are using Windows 7 64 bit and SQL Server 2008 Express, you must install the SP1 for SQL Server 2008 Express.
LANSA recommends downloading and applying the Service Pack to avoid any issues during the Visual LANSA install. Note: you may have to restart the Visual LANSA V12 install if a reboot is required after applying Service Pack 1 to SQL Server 2008 Express.
|
February 1, 2010 - V12
V12 adds support for FLDX so that numeric enter key behaves like field exit (Tab).
The FLDX parameter of x_run was previously ignored and defaulted to 'N' rather than the correct default of 'Y' as per the documentation.
If you wish the numeric enter key to revert to pre V12 behaviour (Enter key), you can set FLDX=N on the x_run |
February 1, 2010 - V12
Object Locking must be enabled in the Visual LANSA system when
using the Deliver to option to deliver to an IBM i remote system. This
requirement has been removed in EPC851
for V12. |
February 1, 2010 - V12
The Visual LANSA V12 Installation can fail if TCP/IP not enabled.
For example, you may have Microsoft SQL Server already installed but if the TCP/IP protocol is not
enabled an installation failure may occur. You can check for this possibility in the following
location:
In SQL Server folder, select SQL Server Configuration manager within the Configration Tools folder. When the SQL Server Configuration manager launches, select SQL Server Network Configuration and then Protocols for <Server name>. TCP/IP should be displayed as Enabled or Disabled. If its set as Disabled, enable this protocol and restart the Visual LANSA Install. Check with your Database Administrator if you require assistance with setting or changing SQL Server protocols. |
February 1, 2010 - V12
An LX_ConfigurationName error message is issued when installing a V11 Network Client once V12 is installed on the Server.
While attempting to install a V11 Network Client, where the Server machine already has both v11 and v12 configurations, a message stating that the LX_ConfigurationName does not exist in the server registry appears after selecting the configuration to connect to.
This message can be avoided by ensuring that the V11 configuration on the Server is the "current configuration".
Even though the message appears stating that the LX_ConfigurationName does not exist in the registry, this message is not a fatal message and after clicking OK, the install continues. |
|
Visual LANSA Framework |
July 23, 2010 - V12
Deploying a VLF application from V12,
you may encounter an error on some PCs
that VF_AC006 module cannot be located
or is not a LANSA component. For further
details including a solution, refer to Unable to Load/locate module VF_AC006 error
after deploying a VLF application in V12 |
February 1, 2010 - V12
The version of the Visual LANSA Framework shipped with V12 doesn't
cater for password length greater than 10 characters or case
sensitivity. Support for these features will be added to the VLF post
V12 GA. |
|
LANSA Composer |
July 30, 2010 V3.0
This item only applies if you installed the LANSA Composer client-runtime version that is compatible with the LANSA Composer server running in a LANSA
V11 SP5 system. If the LANSA system containing the LANSA Composer server is later upgraded to LANSA version 12, then the LANSA Composer client will no longer be able to connect to it. In this event, you can do one of two things:
- uninstall and re-install the affected LANSA Composer clients; OR
- apply Hotfix 001 for LANSA Composer version 3.0 to each affected LANSA Composer client installation.
Hotfix 001 for LANSA Composer version 3.0 is installed with the LANSA Composer client version 3.0. You can find it in file LC_HotFix_3_0_001.zip in the X_WIN95\X_LANSA\X_LIC\Execute folder. Refer to the file LC_HotFix_3_0_001.doc contained in the zip file for further instructions.
|
July 30, 2010 V3.0
If you are upgrading from LANSA Composer
version 2.0 and have NOT previously applied Hotfix 002, then you
should complete the following steps to move the .jar files for
your existing Transformation Maps to their new location. Refer
to the following technical note Important
note if upgrading LANSA Composer version 2.0 and have NOT previously applied Hotfix 002 |
|
LANSA Client |
| None at this time. |
|
Documentation |
| None at this time. |
|
LANSA for iSeries |
September 3, 2010 - V12
In V12 EPC851, when executing RDMLX on the IBM i, an error can
be generated stating that
LPCMN.BND does not exist. This can effect RDMLX functions, RDMLX Webevent
functions, RDMLX components running on System i, and WAMs
executing on a System i application server. Refer to Message stating LPCMN.BND not found when executing RDMLX
function/WAM/component on
IBM i |
March 19, 2010 - V12
If your IBM i master system is on V5R4, you must ensure that you are
up to date with the latest CUME and PTFs to avoid any issues during
checkin or checkout. You must get to the latest CUME and PTFs level
before installing V12 to avoid potential problems. If you do not,
you may experience checkin or checkout issues,
for example, objects not available in the IDE after a refresh or
checking out from the master repository or *svrpgm not created during
a checkin and compile. If you encounter any issues during
checkin or checkout, check the joblog on the IBM i for the following
error
MCH3601 X_BASE
From module . . . . . . . . : LPBASE
From procedure . . . . . . : NotifyDependents__12LpInteractorFQ2_6LpBase6ReasonlP8LpObject
Message.. . . . . . . . . . . : Pointer not set for location referenced.
If this error exists, then you will need to apply the very latest CUME and PTFs.
NOTE: Because this issue is one of re-encapsulation of V6R1 shipped
objects, V12 will need to be reinstalled after applying the latest CUME and PTFs.
|
February 1, 2010 - V12
Object Locking must be enabled in the Visual LANSA system when
using the Deliver to option to deliver to an IBM i remote system. This
requirement has been removed in EPC851
for V12.
|
|
LANSA Integrator |
| None at this time. |
|
LANSA for the Web |
| None at this time. |
|
| |
|
|
