Version 12 Release and Installation Notices
Version 12 Service Pack 1 (SP1), the latest service pack for V12, became available in June 2011. SP1 highlights include Enhanced WAMs, allowing the building of web sites using jQuery/jQuery UI and to return JSON responses for AJAX requests, new RDMLX Repository object named External Resource which provide the ability to enroll all resources associated with an application in the Repository and the ability to install or upgrade LANSA for iSeries into IASPs.
You can install a new Version 12 Service Pack 1 system, update an existing Version 12 system to Service Pack 1 or upgrade an existing Version 11.3 or later system to Version 12 Service Pack 1. Read important SQL Server 2008 Express 2008 upgrade information for V12 SP1.
|14 July 2015||LANSA for iSeries||All Versions||Category: Performance|
LANSA customers have reported significant LANSA performance issues after applying the latest CUME PTF to IBM i 7.2. A PTF is available from IBM to correct this problem. Refer to Latest CUME PTF for IBM i 7.2 introduces significant LANSA performance issues
|28 Apr 2014||Visual LANSA Framework||V12 SP1 EPC870||Category: Web execution|
One of the recent Chrome browser updates (version 34) has introduced some changes that affect Weblets running inside VLF Web. It will be most noticeable with the STD_BUTTON_V2 Weblet (regular WAM button, which will cease to work - pressing the button will have no effect.
This only appears to affect VLF Web, not regular WAMs. However since the upgrading of chrome generally happens automatically, it has the potential to affect many users.
Hotfixes for both V12 SP1 (EPC870) and V13 SP1 (EPC130100) versions of the VLF have been produced. If you are experiencing problems after upgrading Chrome, please contact your local support team to obtain the appropriate hotfix.
|15 Jul 2013||Visual LANSA & LANSA for the Web||V12 SP1||Special instructions required for LANSA V12 SP1 install on Windows 8 and Windows 2012 for Web (IIS Plugin) and UAC. Refer to V12 SP1 install on Windows 8 and Windows 2012|
|13 Jun 2013||LANSA for iSeries||V12 SP1 EPC873||EPC873 introduces a problem when using the stream file BIFs.|
Applying EPC873 to V12 SP1 can introduce a problem when using the stream file BIFs (STM_FILE_*) which are used to open and write files on the IBM i IFS. The issue is that the STM_FILE_WRITE_CTL BIF is writing an incorrect CRLF character, which can cause corruption of the stream file. An EPC873 fix can be requested from LANSA Support to correct this.
|19 Nov 2012||LANSA Composer||4.0||Altova MapForce version 2013 has been tested with LANSA Composer version 4.0 but requires a hotfix in order to function correctly. LANSA Composer version 4.0 Hotfix 005 can be requested via LANSA support channels.|
|13 Jul 2012||LANSA Composer||4.0||An issue has been identified in LANSA Composer versions 3.0 and 4.0 that may lead to changes to a processing sequence being incompletely applied or not applied at all following either edit/save or following an import. This problem can occur even though the save or import operations appear to complete successfully.|
A similar problem may affect the import (only) of Transformation Maps in LANSA Composer version 4.0 (not version 3.0).
For an affected processing sequence, opening it in the editor and saving it will correct the state, even though the save exhibits the symptom described. Further edit/save and/or import operations will succeed normally.
This issue has been corrected and the following hotfixes are available:
- hotfix 010 for LANSA Composer version 3.0, and
- hotfix 003 for LANSA Composer version 4.0
These hotfixes are highly recommended for all LANSA Composer users and can be requested via LANSA support channels.
|7 Mar 2012||LANSA Composer||4.0||This issue applies only to installations of LANSA Composer that are upgrading from an earlier version. New installations will not be affected.|
Server Initialisation following LANSA Composer 4.0 Upgrade may replace certain user-modified definitions by incorrectly importing ALL supplied definitions, including those that may been user-modified such as Document Types and Standards and Notification Events. This means that user modifications to such definitions will be lost.
Hotfix 001 for LANSA Composer version 4.0 is available to address this issue and should be requested from LANSA Support BEFORE performing your LANSA Composer upgrade.
|1 Mar 2012||LANSA Composer||4.0||In the LANSA Composer 4.0 client, a fatal error can be generated while importing supplied Transformation Maps using the Server Initialization Wizard when the LANSA Composer server is running on Windows. Refer to Potential fatal error in LANSA Composer 4.0 when running Initialization for full details and steps to avoid the error.|
|22 Feb 2012||LANSA Composer||4.0||Changed treatment of trailing blanks in string comparisons involving fixed-length character fields in Transformation Maps.|
Customers upgrading from earlier versions of LANSA Composer might also upgrade the mapping tool to the latest version shipped with this version of LANSA Composer (Altova MapForce version 2012SP1). If you do so, you should be aware that Altova MapForce version 2012SP1 exhibits changed behaviour with respect to the treatment of trailing blanks in string comparisons involving fixed-length character fields in Transformation Maps. The string comparison is now sensitive to any trailing blanks in the database field, whereas it was not in MapForce 2010 R3 SP1 (the version shipped with LANSA Composer version 3.0). The effect of this is that affected working maps may no longer work when prepared with a new version of MapForce (they may fail to select the intended data).
Such maps will have to be altered in order to restore the previous behaviour, for example by using a right-trim function on the field value before using it in the string comparison.
|22 Feb 2012||LANSA Composer||4.0||The following issue has been discovered with the use of JDK 1.7 with LANSA Composer 4.0.|
If you are using JDK1.7 on the Composer Client or Composer Windows Server Machine, any attempts to compile a Transformation Map will generate an error message “No compile classes”. This error is caused by recent changes in the way JAVA outputs the compiled trace information.
To avoid this problem, you will need to continue to use the earlier supported versions of JDK with LANSA Composer.
Note: this problem will also occur with earlier versions of LANSA Composer if JDK 1.7 is used.
|22 Feb 2012||LANSA Composer||4.0||LANSA Composer implementations using HTTP activities may require a LANSA Integrator fix to be applied|
LANSA Composer installs and uses LANSA Integrator V12 EPC869 for many of the transport and other activities.
An issue has been discovered that requires an EPC869 LANSA Integrator correction.
If LANSA Composer server is running on a Windows server then the automatic installation or upgrade to version 4.0 has applied this fix for you already. No further action is necessary.
However, if LANSA Composer server is running on an IBM i server, then you will need to manually apply this fix. In addition, if you installed the optional LANSA Integrator Studio with your LANSA Composer client(s), then you should apply this fix to that as well. Please read on for more information and installation instructions.
EPC869 HTTP outbound services now identify themselves as HTTP/1.1. Because the HTTP client supports HTTP/1.1 protocol, some HTTP servers are deciding to send the response content using the Chunked Transfer encoding mechanism. This is causing the response to be corrupted.
An EPC869 fix addressing this issue is available on the LANSA Composer installation media in the \FIXES\EPC869INT-111123 folder. After upgrading your LANSA Composer server or installing yor LANSA Composer client(s), please follow the instructions provided in the readme.txt file in that folder to apply the fix to LANSA Integrator on your LANSA Composer server on IBM i or Windows or to LANSA Integrator Studio in your LANSA Composer client installation.
|14 Feb 2012||LANSA Integrator||V12 SP1 EPC869||The following has been discovered with the use of JDK 1.7 with LANSA Integrator.|
Downloading and using JDK.17 will generate an error message "No compile classes" when compiling projects using the various supplied Wizards in Integrator STUDIO.
This error is caused by recent changes in the way JAVA outputs the compiled trace information.
To avoid this problem, you will need to continue to use the earlier supported versions of JDK with Integrator Studio.
|18 Jan 2012||Visual LANSA||V12 SP1 EPC871||After upgrading to V12 SP1 EPC871, your web application may encounter intermittent failures if your application uses header variables with *webevent functions. An EPC871 fix can be requested from LANSA Support to correct this.|
|30 Dec 2011||Visual LANSA||V12 SP1 EPC871||Installing a new V12 SP1 EPC871 non-english LANSA system or upgrading to V12 SP1 EPC871 on non-english LANSA systems can cause problems with system variables that use the system variable evaluation program M@SYSVAR.|
For example, the @ sign charracter for language FRA is à ie. MàSYSVAR but after an upgrade to V12 SP1 EPC871, the evaluation program will be M@SYSVAR. This will cause programs that use system variables (evaluated by M@SYSVAR) to fail.
The problem is due to the autoimport.exe that is performed during the install or upgrade running the english import.. The issue can be corrected by re-running the SYSVAR import via the System Initialization utility.
|07 Dec 2011||LANSA Integrator||V12 SP1 EPC869||A significant issue has been discovered that requires an EPC869 LANSA Integrator correction.|
EPC869 HTTP outbound services now identify themselves as HTTP/1.1. Because the HTTP client supports HTTP/1.1 protocol, some HTTP servers are deciding to send the response content using the Chunked Transfer encoding mechanism. This is causing the response to be corrupted. An EPC869 fix can be requested from LANSA Support.
|01 Dec 2011||Visual LANSA||V12 SP1 EPC871||WAMs generated after applying EPC871, which contains fields in a list which have the *HIDE or *HIDDEN tag may not display correctly at runtime. Refer to Hidden columns on a WAM list are shown at runtime for full details and correction.|
|04 July 2011||Visual LANSA||V12 SP1 EPC871 (spin0316)||The V12 SP1 DVD will install SQL Server 2008 Express SP2 instead of SQL Server 2008 Express.|
The install will not upgrade from SQL Server 2008 Express to SP2.
SQL Server 2008 Express SP2 does not install The SQL Server Configuration Manager. A separate install for this can be found in \setup\installs\MSSQLEXP\ SQLManagementStudio*.exe
|4 Jul 2011||Visual LANSA||V12 SP1||SQL Server 2008 SP2 is shipped on the V12 SP1 DVD. You may experience the following error when installing Visual LANSA where the install attempts to install or upgrade SQL Server 2008 to SP2. |
Install ended in error.
Error <-3> creating database. Error message: SQL Server Network Interfaces: Error Locating Server/Instance Specified[xFFFFFFFF]. Microsoft SQL Server Native Client 10.0
If you have Microsoft .Net Framework 4 installed, it must be the full version i.e. both .Net Framework 4 Client Profile and .Net Framework 4 Extended must be installed prior to installing Visual LANSA (see image).
If the full version is not installed then the Microsoft SQL Server 2008 Express with SP2 install will fail. Refer to the Microsoft Support site article for full details: https://support.microsoft.com/en-us/help/2500042/error-message-when-you-install-sql-server-2008-service-pack-2
Note: The error will also occur if you attempt to install or upgrade to SQL Server 2008 SP2 manually (not as part of the Visual LANSA install).
|29 Jun 2011||Visual LANSA Deployment Tool||V12 SP1||It can occur in the Deployment Tool that objects (Forms, Processes/Functions, WAMs) selected in the Object Selection dialog are not saved correctly with the package. This occurs when the Other Objects tab is active when pressing OK on the Object Selection dialog; any newly added Forms/Processes/WAMs are discarded. A work-around is to press OK after adding these objects, before going back into the dialog to select Other Objects. Contact your local LANSA vendor to request a hotfix.|
|21 Apr 2011||LANSA for iSeries||V12||When upgrading LANSA for iSeries to V12, you may be unable to restore V12 objects to QTEMP on V5R3 or V5R4. This is a known situation whereby PTFs are required for any objects saved on IBM i 6.1 before they can be restored on previous IBM i versions. Refer to Unable to restore V11 SP5 objects to QTEMP on V5R3 or V5R4. This situation also applies to V12 objects.|
|03 Sep 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|
|30 Jul 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: |
|30 Jul 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|
|23 Jul 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|
|22 Jul 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.
|09 Jul 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|
|29 Mar 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. We have established that at CUME C1137540 level, this problem does not occur. If you encounter any issues during checkin or checkout, check the joblog on the IBM i for errors similar to the following examples|
If either of these errors (or similar MCH3601 pointer errors) exist, 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.
|01 Feb 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
|01 Feb 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.
|01 Feb 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
|01 Feb 2010||Visual LANSA||V12||The Visual LANSA General Checklist contains the following check|
|01 Feb 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.|
|01 Feb 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
|01 Feb 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.|
|01 Feb 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.|
|01 Feb 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.
|01 Feb 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.