Version 15 Release and Installation Notices

Category: Web execution/Partition initialization
Upgrading from Windows 10 to Windows 11 introduces web execution 404 errors and partition init import failures for all supported versions of Visual LANSA.
If you upgrade from Windows 10 to Windows 11, you can encounter several related problems in Visual LANSA. These errors can occur irrespective of LANSA version or EPC level.
The symptoms of the windows 11 compatibility issues are:

• A web execution error 404 is issued for pages that previously executed OK in Windows 10.
• Performing a Partition init of any of the options (Mandatory partition initialization/Visual LANSA Framework/WAM development/LANSA Client field and file definitions/Sample Material) will fail for some imports, for example Standard Widgets, Standard Resources, VLF.The import error is: Operating system Error occurred when attempting to perform EXECUTE operations.
• Connecting to a windows backend server (on Windows 11) in the Web Administrator will give a Connection failed (0x0000001c) error.

This compatibility issue has been fixed and the fix will be shipped in the next EPCs for V14 SP2 and V15 respectively.
If you have an urgent need for the fix prior to the EPCs being available, you can request a hotfix by contacting your local LANSA support group. Please note that hotfixes are only available for the supported versions of LANSA (V14 SP2 and V15) at the latest EPC level.

Category: Install
Installing Visual LANSA V15 on an operating system older than Windows 10 or Windows Server 2016 (or newer) can end with an error during the SQL Server 2019 install. If you encounter the following error:
The SQL Server install ended in Error. Check C:\Program Files\Microsoft SQL Server\150\Setup_Bootstrap\Log\Summary.txt to identify the error.
search the %TEMP% folder for SqlSetup.log. Open SqlSetup.log and look for the following entry:
Unsupported Operating System. SQL Server 2019 is only installable on Windows Server 2016/Windows 10 or newer.

SQL Server 2019 cannot be installed on an operating system older than Windows 10 or Windows Server 2016. For example, SQL Server 2019 cannot be installed on Windows 8.1

Category: Deployment
V15 includes enhancements which mean that the next deployment of any kind after installing V15 must be a Version (MSI), not a Patch (MSP). Attempting to deploy V15 changes as an MSP will generate the following message

Category: Install/System Initialization
Because the default minimum password length for IBM i is 6 characters, the shipped default password for the user profile in a new V15 LANSA installation has now been changed to vlansa. If you use this default user profile to perform a system initialization during the Visual LANSA V15 slave install, the connection will fail unless the correct password is used, including case sensitivity (depending on the password level enabled on your IBM i environment).
Note: LANSA strongly recommends that after installing V15, for security reasons, you immediately change the default user profile password to your company standard and/or create your own user profiles to access the new V15 system, including for use in the system initialization during the Visual LANSA V15 slave install.

Category: IDE
Launching the V15 Visual LANSA IDE without a license has changed (the change was introduced in V14 SP2).
The LANSA 'read-only mode' has been introduced to allow you to view code and compile objects without a development license. This mode is ideal for build machines. The Demo mode where you could create a limited number of name restricted objects, available in previous versions, has been removed. A new evaluation version of Visual LANSA will be available for download soon that will enable you to use the IDE unrestricted for a limited time period to replace demo mode.

Category: Install
The LANSA for i install is delivered as a save file in V15. The install can no longer be launched directly from the V15 DVD. The LANSA for i install save file is in a ZIP file on the V15DVD. The ZIP file can be extracted from the DVD, the save file unzipped and moved to the IBM i using standard steps and the LANSA install launched using the instructions in the LANSA for i Install guide. The following link provide example instructions from IBM on how to FTP from the IBM i IFS to a save file in QGPL. (Its vital to create the save file in QGPL first)
http://www-01.ibm.com/support/docview.wss?uid=nas8N1012624
This change also means that LANSA for i CANNOT be installed using the Image Catalog instructions provided here.

Category: OSU
The Open Systems Utilities (OSU) is no longer shipped in V15. The OSU utilities was never implemented for RDMLX and is no longer compatible with RDML in later versions of LANSA. Historically, the most commonly used utility was [email protected] (High speed partition deletion) but partitions can be deleted from within LANSA housekeeping, without requiring exclusive use of the LANSA system, since LANSA V12. 

Category: Performance
IBM PTF available for Mutex wait (MTXW) issue that can affect performance of LANSA applications.
LANSA customers who have large systems involving many thousands of LANSA runtime jobs have sometimes reported a slowing down in performance of the LANSA jobs due to a Mutex Wait (MTXW) situation. Refer to Performance slowdown in LANSA applications caused by Mutex wait issue

Category: Checkin/Compile
If you encounter the error - LIBRARY QSYSINC NOT FOUND during checkin and compile to the IBM i, the most likely reason is that some C compiler options are missing. We suggest you install (reinstall) the 5722SS1 Option 13 "System Openness Includes".
Licensed Product Program Option Description
5770SS1 *BASE IBM i
5770SS1 1 Extended Base Support
5770SS1 2 Online Information
5770SS1 3 Extended Base Directory Support
5770SS1 8 AFP Compatibility Fonts
5770SS1 12 Host Servers
5770SS1 13 System Openness Includes
As per the advice at http://archive.midrange.com/midrange-l/200510/msg00213.html you should install it from your original OS/400 or i5/OS CDs
GO LICPGM
Select option 11. Install Licensed Programs
Type a 1=Install next to 5722SS1 Option 13, "System Openness Includes" and press Enter

Category: Host Monitor/Checkin and Compile
A checkin and compile problem has been encountered with the following criteria in place
- An RDML physical file which has a key, in an RDMLX partition
- Where the master repository is on an IBM i with Operating System 7.3
- The checkin and compile via the host Monitor will fail with an MCH5601 error in the joblog on a MOVOBJ command
This has been confirmed as an OS 7.3 issue and an IBM PTF is available to resolve the issue. The PTF is SI62854.
This problem is not exclusive to any particular version of LANSA and can occur on all supported versions of LANSA with the master repository on IBM OS 7.3.