Version 11 Release and Installation Notices
Version 11 Service Pack 5 (SP5), the latest update for Version 11, is now available.
The SP5 highlights are Vista support (Refer to Vista upgrade
notice below), IBM i 6.1 support, Visual LANSA Themes and
further performance improvements as well as many other fixes and
enhancements.
Upgrading to LANSA Version 11 Service Pack 5
You can install a new Version 11 SP5 system,
update an existing V11 system from any service pack level to Service Pack
5 or
upgrade to Version 11 SP5 from Version 10.0.
Important
notices you should read before upgrading
Latest version of documentation
Details of supported LANSA Versions
Details of supported third-party software and hardware
combinations
Details of support for IBM i 6.1
Support for Microsoft Vista
Planned Support of
Windows 7
Planned Support of
Windows Server 2008 R2
Latest available EPCs
The latest LANSA EPCs that contain fixes and add valuable new
features to your LANSA products can be found in the
EPCs section of
this site.
You cannot apply
any V11 Service Pack or any
EPCs after EPC771 to unsupported versions of OS/400. Click for
more information...
|
18 September 2009 |
Visual LANSA V11 SP5 EPC845
Applying EPC845 and rebuilding OAMs can introduce unpredictable
behavior and fatal errors, in particular when performing
database UPDATEs.
A critical EPC845 hotfix has been built and is now
available to resolve this issue. Contact
you local LANSA vendor to request this hotfix.
|
|
2 September 2009 |
LANSA for iSeries V11 SP5 EPC845
Fix required for applications accessing an IBM i in superserver mode after applying EPC845.
An issue has been found where applications accessing an IBM i via superserver (either to an RDMLX server or using the DEFINE_ANY_SERVER) may experience access violation errors during SELECT/FETCH statements. This can occur if the previous I/O resulted in an error or record not found; the subsequent I/O request (even to a completely different file) will fail with a pointer error in the iSeries joblog:
MCH3601 Escape 40 31/08/09 11:10:57.421664 X_SSV
From module . . . . . . . . : X_SSV1
From procedure . . . . . . : Handle_X_CID_CALL_IOMODULE
Statement . . . . . . . . . : 234
To module . . . . . . . . . : X_SSV1
To procedure . . . . . . . : Handle_X_CID_CALL_IOMODULE
Statement . . . . . . . . . : 234
Message . . . . : Pointer not set for location referenced.
Cause . . . . . : A pointer was used, either directly or as a basing
pointer, that has not been set to an address.
The issue does not occur if all OAMs accessed have been rebuilt with EPC845.
A fix for EPC845 is currently in progress and will be
made available ASAP.
|
|
14 August 2009 |
LANSA for Web (WAMs) V11 SP5 EPC845
Blank fields in WAMs are padded with a single blank after applying EPC845.
When using lists in WAMs, at runtime this renders default values to blanks rather than stripping the value.
When viewed on a web browser users may experience
unexpected behavior. For example, not being able to type in a value or tabbing between fields causes the entire blank fields to be highlighted or if you click on an entry field the cursor ends up after the blank.
An EPC845 hotfix is available to
correct this problem. Contact you local LANSA vendor to
request this hotfix.
|
|
4 August 2009 |
LANSA for iSeries V11 SP5
If you are performing a LANSA for iSeries upgrade and your site has the following environment
- multiple LANSA systems on your system i
- upgrading one of the LANSA systems from V10.0 to V11 SP5
- the last system in the list of installed LANSA systems is already at V11 SP5 **
Then, the following error will be generated when upgrading the V10.0 system.
This LANSA library <PGMLIB> is the same version and cannot be upgraded
** you can determine this using the following command
WRKOBJ OBJ(*ALL/DC@A01) OBJTYPE(*DTAARA)
You should contact your local LANSA Vendor for instructions on how to complete the LANSA
upgrade.
|
|
3 August 2009 |
LANSA V11 SP5
EPC845 ships the latest fixes and enhancements
for V11 SP5 and supersedes all previous V11 SP5 EPCs.
EPC845 also delivers support for the LANSA for UNIX (Linux) release
more...
|
|
1 June 2009 |
LANSA Client V11 SP5 & EPC814
LANSA Client V11 SP5 no longer bundles Crystal Reports.
However, all existing queries (output to report) will still work with LANSA Client V11 SP5.
LANSA Client V11 SP5 supports the current supported version of Crystal Reports (CR 2008). EPC814
enhances LANSA Client V11 SP5 to allow you to avail of the free Crystal Reports 2008 runtime
engine. Refer to EPC814.htm
for further details.
|
|
21 May 2009 |
LANSA for iSeries - V11 SP5 & EPC838
After applying EPC838 to LANSA on iSeries, a fatal error
PROGRAM DC@P2002 ENCOUNTERED AN UNEXPECTED ERROR will
be generated when compiling a file after adding,
changing or deleting a validation rule via LANSA for
iSeries development screens. An EPC838 patch is
available to correct this problem. Contact you local
LANSA vendor to request this patch.
|
|
20 April 2009 |
Visual LANSA - V11 SP5 & EPC837
Fatal error when attempting to open files after applying
EPC837 to Visual LANSA. This issue was introduced in
EPC837. A fix has been delivered in EPC838.
Refer to Error when attempting to open files after applying EPC837 for more
details.
|
|
25 March 2009 |
LANSA Composer - V2.0
Previous versions of LANSA Composer compiled the generated Java code for Transformation Maps for target Java version 1.4.
To accommodate recent and future versions of Altova
MapForce, version 2.0 of LANSA Composer has been changed such that:
- You can specify (in System Settings) the Java version to target /li>
- The default value (including for an upgraded installation) is now 1.5
If the JVM on your System i or Windows server is running at version 1.4, the compiled code that results when you prepare Transformation Maps with the default setting in this version of LANSA Composer will not be compatible with your
JVM.
To address this, you should do one of the following:
a) Change the "Java version for Transformation Maps" value in System Settings to be compatible with the JVM version you are using.
b) Change the LANSA Integrator configuration on your System i or Windows server to use a JVM version 1.5 (or later). Refer to How to Confirm JAVA Version on iSeries for guidance in connection with your System i server.
Note that Java code generated for maps created with MapForce 2009 or later will require at least Java version 1.5. Therefore the second option is recommended. If you do not choose this option now, it will become necessary at a later time.
|
|
20 March 2009 |
LANSA Composer - V2.0
When the SMTP_MAIL activity is used with attachments
several times in one processing sequence, the
attachments accumulate such that each email includes
both its own and previous attachments. This issue is
corrected in hotfix 001 for LANSA Composer Version 2.0.
This hotfix is supplied on the LANSA Composer Windows
Client Version 2.0 CD and instructions to apply it are
included in the Read Me supplied on the CD. Application
of this hotfix is highly recommended if you presently
use or will use the SMTP_MAIL activity.
|
|
20 March 2009 |
LANSA Composer - V2.0
An enhancement is available for LANSA Composer version
2.0 that enables dynamic class loading for the
transformation map Java classes. The effects of this new
behaviour include:
• no need to restart JSM after preparing or deploying
maps
• maps prepared with different versions of MapForce can
co-exist
• no need to rebuild maps following a MapForce upgrade
TTo enable this enhancement you must first apply EPC840
to LANSA Integrator on the LANSA Composer server. Then
you must apply hotfix 002 for LANSA Composer version
2.0. As a part of the procedure to apply hotfix 002, you
must MOVE your existing transformation map .jar files.
Both EPC840 for LANSA Integrator and hotfix 002 for
LANSA Composer Version 2.0 are supplied on the LANSA
Composer Windows Client Version 2.0 CD and instructions
to apply them are included in the Read Me supplied on
the CD. Application of this hotfix is highly
recommended.
|
|
24 October 2008/b> |
LANSA for the web - V11 SP5
After applying V11 SP5 to your LANSA for web windows
web server, you may encounter the following error on the
browser if you specify a port number on your URL
Unable to transform input XML
A hotfix is available to correct this problem. Contact you local LANSA vendor to request this hotfix.
|
|
23 October 2008 |
LANSA Integrator - All versions
Installing or upgrading 3rd party software may cause your existing working
LANSA Integrator application to fail with a licence
error. Refer to Installation of 3rd party software affects LANSA Integrator license
on System i for further details and resolution.
|
|
22 September 2008 |
Visual LANSA - V11 SP5
When loading OTHER files via the Visual LANSA IDE,
Logical Files are only displayed for the last file on
the list. This problem will occur if you set the
field "full or partial physical file name" to
either blank (all files) or use a partial name. If you
specify the exact file name, the logical files will be
correctly returned. A workaround is to specify the exact
file name. If this workaround is inconvenient or not sufficient,
a hotfix is available to correct this problem. Contact
you local LANSA vendor to request this hotfix.
|
|
4 August 2008 |
LANSA for iSeries - V11 SP4 ONLY This issue is
resolved in SP5
Integer(1) fields have been stored and retrieved incorrectly from the database on the iSeries if they have a negative value, however within LANSA they have retained the correct value. Within LANSA if the Integer(1) field is used as a key, then a keyed access using the negative value will fail to retrieve the record. Outside of LANSA, external access (for example interactive SQL or query) will show that the field with a negative value contains the wrong value.
User Action: After upgrading to SP5, recompile any files in an RDMLX partition that contain Integer(1) fields on
iSeries. In addition, ensure that any negative values are corrected after recompilation. Please contact your product vendor if you require assistance with
this task.
|
|
21 July 2008 |
Visual LANSA - V11 SP5
Due to changes in the way that Vista handles interactive
desktop sharing and spawned processes, remote and local
debugging is not fully functional in SP5 on Vista. To
allow debugging in Vista requires a re-architecture of
the LANSA debugging mechanism. The ability to debug in
Vista using a new debugging mechanism will be available
in the first EPC for SP5. You should check the EPC
section of the LANSA web site for the availability
of this EPC.
|
|
30 May 2008 |
Visual LANSA - V11 SP4 This issue is resolved
in SP5 (refer to Note below)
If you compile OAMs at SP4 level and also compile some, but not all, functions and components that access this
OAM in the one job or superserver session on iSeries, an error will be generated.
For example, if a function or component compiled prior to SP4 uses an OAM compiled on SP4, then a function or component compiled on SP4 attempts to use the same OAM in the same job or superserver session, then an IOM0033 message is issued and ER is returned.
IOM0033: I/O request to file xxxxx(the file name that is accessed). *LIBL [member *FIRST] is invalid at this time
One workaround is to recompile all functions/components
in SP4 that access the file.
However, an EPC has been produced to resolve this issue.
EPC827 for SP4 is downloadable from the EPC
section of the web site.
Note: After applying EPC827 to SP4 or applying SP5, you will be required to recompile any
OAMs in an RDMLX partition that have been compiled in SP4 prior to
EPC827 or SP5 being applied. Refer to EPC827 User Actions.
|
|
23 April 2008 |
Visual LANSA - V11 SP4 This issue is resolved
in SP5
In V11 SP4, if you use the builtin function GET_SESSION_VALUE with the key
USER, the USER returns the value entered for USER on the command line in the exact case it was entered.
Prior to v11 SP4, the value for USER was always in UPPERCASE.
A solution is available that reverts to 11.3 behaviour.
Refer to GET_SESSION_VALUE with the key USER returns exact case
in V11 SP4 which
can lead to problems for login or data retrieval for more
details.
|
|
13 March 2008 |
LANSA Integrator - V11 SP4 This issue is
resolved in SP5
The LANSA Integrator guide shipped with SP4 makes
references to LANSA Integrator features that are not
available in the LANSA Integrator software shipped with
SP4. To avoid confusion, you can should download the
LANSA Integrator guide that is available in the documentation
section of the LANSA web site.
|
|
13 March 2008 |
LANSA for the Web - From V11 SP4
There was a change made in SP4 for V11 to prevent the DISPLAY/REQUEST/POP_UP command from being executed more than once in one web function request.
The consequences of this change has the potential to affect a currently working LANSA for the web application.
Refer to After applying SP4
an existing web application may start generating fatal
errors
|
|
29 February 2008 |
LANSA for the Web (WAMs) - From V11 SP4
As part of an ongoing program to improve WAM performance
and browser compatibility, a number of weblets have been
revamped or rewritten in V11 SP4. To avoid backward
compatibility issues, new "v2" versions of the
weblets have been created. Your application will have to
be updated to avail of these new "V2" weblets.
Refer to Revamped or
rewritten weblets in V11 SP4 to improve XSLT performance
and browser compatibility of WAMs
Note: If you have
created your own style and script weblets that do not call the
standard weblets, then you may have problems after installing
this Service Pack. In this case, you should make the modifications
detailed in the WARNING
section in the tip prior to applying this service pack.
|
|
22 February 2008 |
Visual LANSA - From V11 SP4
Applying SP4 to V11 re-introduces correct active tabsheet
behaviour when the order of tabsheets is changed. In V11.3, programatically changing the
displayposition of a tab folders active tabsheet would
change the active tabsheet to whatever tabsheet took the
place of the changing tabsheet.
In V11 SP4, after programatically changing the order of
tabsheets in a tab folder the original active tabsheet
is still the current active one and changing the active tabsheet
will have to be defined explicitly in your code. Refer
to Applying SP4 to V11
re-introduces correct active tabsheet behaviour when the order
of tabsheets is changed
|
|
12 February 2008 |
Visual LANSA - From V11 SP4
Improvements in the way that LANSA handles multilingual Text may impact on current LANSA environments. The Multilingual Application Design Guide contains a new section titled 6.8 Handling Multilingual Text in 11.4 which answers the question
Does LANSA know the correct CCSID to use for Multilingual text?
This new section contains information and recommendations relating to the functionality used for multilingual text when checking in/out multilingual text in all LANSA object types (11
SP4 and later) . It is also used when exporting to Windows and when compiling text in all objects on Windows and RDMLX objects on System i in LANSA V11 and later. Existing multilingual text may be affected if for example, the CCSID associated with each partition language doesn't match the intended execution environment or if literals are used in
RDML/RDMLX code instead of in *MTXTs. Refer to 6.8 Handling Multilingual Text in the Multilingual Application Design Guide for full details.
|
|
25 January 2008 |
Visual LANSA - From V11 SP4
Visual LANSA abnormally shuts down with an access violation in LXPPRBLD.EXE if a literal in the RDMLX contains
special characters. For example, the following code would not be accepted
DEFINE FIELD(#STRING1) TYPE(*CHAR) LENGTH(3) DEFAULT('ab')
The following error message will be displayed:
"LXPPRBLD.EXE has encountered a problem and needs to close. We are sorry for the inconvenience."
LANSA recommends that the use of special characters in literals (such as linefeed, carriage return, binary zeroes, etc.) for both LANSA for iSeries and Visual LANSA
is implemented via the specialized BIFs HEXTOBIN and BINTOHEX instead of via LANSA defined fields.
|
|
2 January 2008 |
Visual LANSA - V11
Oracle PC Other Files with numeric columns where scale is greater than precision may have problems in LANSA V11.
For example, LANSA V10.0 incorrectly allowed the load of an Oracle 5,10 column as a LANSA
Signed(5,9) field. LANSA does not expect or support the decimals for a numeric field being greater than the length. The load defect is fixed in V11
in that LANSA will attempt to load one of these columns as a field that is valid to LANSA.
If you encounter any issues with Oracle PC Other Files containing such numeric columns, you must resolve the problem in V11 by deleting any fields that have been loaded incorrectly, reloading the Oracle PC Other File, and recompiling/redeploying all objects that use the
fields.
|
|
13 December 2007 |
Visual LANSA - V11
Syntax checking in Visual LANSA V11 has been tightened
so that it agrees with LANSA for iSeries syntax
checking. RDML code that was allowed in previous
versions of Visual LANSA may generate Full Function
Check (FFC) errors after upgrading to V11. Only code
that is not allowed on System i will generate syntax
errors. Note: this issue will not be observable
until existing source is opened in the V11 Visual LANSA
Editor, at which time it can be corrected.
Examples:
A single quote followed by another single quote is not
valid syntax in a parameter
e.g. use builtin(TCONCAT) with_args(#STD_CODE '')
Code of the syntax format Keyword Space Value is not
valid syntax
e.g. select *all from_file filea with_key(#key1)
|
|
13 December 2007 |
Visual LANSA - V11
Define_com commands cannot use the same name for the
component as an existing repository field.
|
|
13 December 2007 |
Visual LANSA - V11
You cannot specify the same field in *Received and
*Returned parameters of the SUBROUTINE command.
|
|
13 December 2007 |
Visual LANSA - V11
The default intermediate precision used for CHANGE
commands in RDMLX code has been corrected to produce the
same result as RDML code on System i. This ensures that
the same results are produced across all platforms and
in RDML and RDMLX code. Note: that for
calculations where the accuracy of decimal precision is
important, the PRECISION parameter of the CHANGE command
must always be used.
|
|
13 December 2007 |
Visual LANSA - V11
CHANGE and ASSIGN commands now correctly remove trailing
blanks when assigning an Alpha or Char field type to a
String field type.
|
|
13 December 2007 |
Visual LANSA - V11
Combo-box height may be different after an upgrade to
V11. This is caused by the font used in V11. The
combo-box height changes to facilitate the font used. To
allow fixing of the height, a new property has been
added to the combo-box called "FixedHeight" which can be
used to set the height manually.
|
|
13 December 2007 |
Visual LANSA - V11
OTHER files with non-keyed logical views that may have
been converted to LANSA files in previous versions of
LANSA will generate a warning message that the non-keyed
logical views will have to be deleted before they can be
loaded into the V11 Visual LANSA Editor.
|
|
13 December 2007 |
Visual LANSA - V11
If SQL Server is used as the database:
The existing database/configuration should be upgraded,
rather than creating a new database/configuration and
importing objects. Refer to:
Support for SQL Server 2000 and SQL Server 2005
collections in Visual LANSA 11.3 (CU3)
ODBI=1, previously required for many applications due to
blocked connections, is now no longer required for most
applications. Refer to
Blocked connections with your SQL Server implementation
|
|
13 December 2007 |
Visual LANSA Framework - V11
If you have amended the Visual LANSA Framework shipped
components, your changes will be over written when you
upgrade to V11 or apply a Visual LANSA Framework EPC.
Note: All the Visual LANSA Framework shipped
components (VF_<form name>) come with a disclaimer
highlighting that changing shipped components is not
recommended.
|
|
13 December 2007 |
LANSA for the Web - V11
Webevent
The upload program (as provided in SET181UPLO in the
SET material) can stop functioning after upgrading to V11
if you also upgrade to V5R3 and use Apache as the
HTTP Server. SET181UPLO can
be changed to upload files into the IFS using Apache
|
|
13 December 2007 |
LANSA for iSeries - V11
If you have RDML code containing hexadecimal literal
values (X'nn') and you intend to use Visual LANSA for
editing your source code then you MUST modify your code
to no longer use these hexadecimal literal values
directly before you start using Visual LANSA. The RDML
must be changed as it will be corrupted when using
Check-out from the System i to Visual LANSA. Note:
Hexadecimal literal values are not supported by the
Visual LANSA IDE in any form.
|
|
13 December 2007 |
LANSA for iSeries - V11
Due to its lack of support for lowercase directory
names, CCSID 5026 is not supported in V11. Upgrading
LANSA on a System i that uses CCSID 5026 may cause
problems for LANSA systems that use the Integrated File
System (IFS).
|
|
13 December 2007 |
LANSA for iSeries - V11
The shipped DC@OSVEROP data area now sets *RPGIV and *ILE
by default with V11. This specifies that each program
is to be compiled using RPG/IV code, then bound as an
ILE type program. The compile will also statically bind
any multilingual program into the function program and
use supplied service programs to dynamically call (CALLB)
LANSA internal programs.
|
| 8 February 2007 |
LANSA Client - From V11.3
Crystal Reports XI cannot
open DBF file created in LANSA Client V11.3.
Refer to A DBF file created with LANSA Client 11.3 will not open when creating a report with Crystal Reports
XI
|
| 5 February 2007 |
LANSA Client - V11.3
Pre-requisites EPC listed in
the What's New in LANSA Client V11.3 (Readme)
The What's New in LANSA Client V11.3 (Readme) lists
EPC790 as the only pre-requisite backend server EPC: You must have applied epc790 or later to your server to support LANSA Client V11.3
However, both EPC790 and EPC800 are required as
pre-requisite EPCs. EPC790 and EPC800 are shipped on the
LANSA Client CD in the \EPC folder or can be downloaded
from the EPC
section of the LANSA Web site.
|
|
28 July 2006 |
LANSA for the Web - From V11.3 - WAMs only
Ending presubmit JavaScript with '//' no longer cancels onclick event.
This was a technique that might have been used but in
11.3 (CU3) the behavior will change.
Refer to Ending presubmit JavaScript with '//' no longer cancels onclick event in
11.3
for full details.
|
| 25 July 2006 |
LANSA for the Web - From V11.3 - WAMs only
Correct usage of WEB_MAP FOR(*NONE) and WEB_MAP FOR(*INPUT) in WAMs
enforced in CU3.
Refer to Using WEB_MAP FOR(*NONE) and WEB_MAP FOR(*INPUT) in WAMs
for full details.
|
| 24 July 2006 |
LANSA for iSeries - V11
How to avoid MCH3402 errors when repeatedly running RDMLX functions on iSeries
after checking and compile during development.
Refer to Checking in RDMLX function
results in Process not getting found in the reused job
for full details.
|
|
9 December 2005 |
LANSA Integrator - V11.0
Correction and clarification
of post Installation steps required after a new V11.0
LANSA Integrator installation.
Correction:
1. After completing a new V11.0 LANSA Integrator
installation, the HTTP server instance will contain the
following incorrect entry:
ScriptAliasMatch ^/cgi-bin/jsmdirect(.*) /QSYS.LIB/JSMLIB.LIB/JSMLIB.PGM$1
This entry is incorrect and should be JSMDIRECT.PGM$1 ie.
ScriptAliasMatch ^/cgi-bin/jsmdirect(.*) /QSYS.LIB/JSMLIB.LIB/JSMDIRECT.PGM$1
And the following directives must also be correctly
added:
ScriptAliasMatch ^/cgi-bin/jsmproxy(.*) /qsys.lib/JSMLIB.lib/jsmproxy.pgm$1
ScriptAliasMatch ^/cgi-bin/jsmadmin(.*) /qsys.lib/JSMLIB.lib/jsmadmin.pgm$1
Note: The example IBM Apache HTTP Server and HTTP Server
configurations contain the correct directives.
Remember that JSMLIB.lib needs to be changed to your JSM library name.
Clarification:
1. In 8.1 Task: Configure the Java Service Manager on
iSeries, section Step 3. Check configuration values
of the Install LANSA on iSeries guide, you must ensure
that you have JSM started before performing the following step:
Use menu option 4 Edit Manager Properties of the Java Service Manager Administrator Menu, to display the contents of the manager.properties file.
If JSM is not started before performing this step, the properties file will be empty.
|
|
6 June 2005 |
Visual LANSA - V11
After installing Visual LANSA V11 on
a system that already has Microsoft Visual C++ 6.0
installed, LANSA components may not compile
successfully. Refer to
Using Microsoft C++ 6.0 compiler with Visual LANSA V11
for full details and steps to
correct.
|
|
22 April 2005 |
Visual LANSA - V11
After installing or upgrading, your dongle may not
be recognized. Installing the latest dongle drivers
will resolve this issue. See the Updated
driver for USB dongles Tip
for further information.
|
|
15 April 2005 |
LANSA Integrator
When the installation is
completed a separate job is
submitted to optimize Integrator Jar
files. This job will run in the
background and may take up to
several hours to complete.
|
|
15 April 2005 |
Visual LANSA - V11
When installing or upgrading,
your dongle should NOT be connected.
See the
USB dongles on various platforms Tip
for further information.
|
|
15 April 2005 |
Visual LANSA - V11
When installing Visual LANSA do
not use a period/full stop (".") in
the name of the Visual LANSA install
directory.
|
|
15 April 2005 |
Visual LANSA - V11
Avoid running multiple network
client installs simultaneously. This
may result in database locking
conflicts.
|
| 15 April 2005 |
Visual LANSA - V11
You cannot install V11 or
upgrade to V11 on machines running the Windows NT
(Server and Workstation) operating system. The upgrade will generate
a message that no configuration
exists that can be upgraded to V11 and will not continue. For details
of supported configuration please
refer to the LANSA
Version 11 Supported Platforms
|
Visual LANSA
|
18 September 2009 - V11 SP5 & EPC845
Applying EPC845 and rebuilding OAMs can introduce unpredictable
behavior and fatal errors, in particular when performing
database UPDATEs.
A critical EPC845 hotfix has been built and is now
available to resolve this issue. Contact
you local LANSA vendor to request this hotfix.
|
3 August 2009 - V11 SP5
EPC845 ships the latest fixes and enhancements
for V11 SP5 and supersedes all previous V11 SP5 EPCs.
EPC845 also delivers support for the LANSA for UNIX (Linux) release
more...
|
20 April 2009 - V11 SP5 & EPC837
Fatal error when attempting to open files after applying
EPC837 to Visual LANSA. This issue was introduced in
EPC837. A fix has been delivered in EPC838.
Refer to Error when attempting to open files after applying EPC837
for more
details.
|
22 September 2008 - V11 SP5
When loading OTHER files via the Visual LANSA IDE,
Logical Files are only displayed for the last file on
the list. This problem will occur if you set the
field "full or partial physical file name" to
either blank (all files) or use a partial name. If you
specify the exact file name, the logical files will be
correctly returned. A workaround is to specify the exact
file name. If this workaround is inconvenient or not sufficient,
a hotfix is available to correct this problem. Contact
you local LANSA vendor to request this hotfix.
|
21 July 2008 - V11 SP5
Due to changes in the way that Vista handles interactive
desktop sharing and spawned processes, remote and local
debugging is not fully functional in SP5 on Vista. To
allow debugging in Vista requires a re-architecture of
the LANSA debugging mechanism. The ability to debug in
Vista using a new debugging mechanism will be available
in the first EPC for SP5. You should check the EPC
section of the LANSA web site for the availability
of this EPC.
|
30 May 2008 - V11 SP4 This issue is resolved
in SP5 (refer to Note below)
If you compile OAMs at SP4 level and also compile some, but not all, functions and components that access this
OAM in the one job or superserver session on iSeries, an error will be generated.
For example, if a function or component compiled prior to SP4 uses an OAM compiled on SP4, then a function or component compiled on SP4 attempts to use the same OAM in the same job or superserver session, then an IOM0033 message is issued and ER is returned.
IOM0033: I/O request to file xxxxx(the file name that is accessed). *LIBL [member *FIRST] is invalid at this time
One workaround is to recompile all functions/components in SP4 that access the file. However, an EPC has been produced to resolve this issue.
EPC827 for SP4 is downloadable from the EPC
section of the web site.
Note: After applying EPC827 to SP4 or applying SP5, you will be required to recompile any
OAMs in an RDMLX partition that have been compiled in SP4 prior to
EPC827 or SP5 being applied. Refer to EPC827
User Actions.
|
23 April 2008 - V11 SP4 This issue is resolved
in SP5
In V11 SP4, if you use the builtin function GET_SESSION_VALUE with the key
USER, the USER returns the value entered for USER on the command line in the exact case it was entered.
Prior to v11 SP4, the value for USER was always in UPPERCASE.
A solution is available that reverts to 11.3 behaviour.
Refer to GET_SESSION_VALUE with the key USER returns exact case
in V11 SP4 which
can lead to problems for login or data retrieval for more
details.
|
22 February 2008 - From V11 SP4
Applying SP4 to V11 re-introduces correct active tabsheet
behaviour when the order of tabsheets is changed. In V11.3, programatically changing the
displayposition of a tab folders active tabsheet would
change the active tabsheet to whatever tabsheet took the
place of the changing tabsheet. In V11 SP4, after programatically changing the order of
tabsheets in a tab folder the original active tabsheet
is still the current active one and changing the active tabsheet
will have to be defined explicitly in your code. Refer
to Applying SP4 to V11
re-introduces correct active tabsheet behaviour when the order
of tabsheets is changed
|
12 February 2008 - From V11 SP4
Improvements in the way that LANSA handles multilingual Text may impact on current LANSA environments. The Multilingual Application Design Guide contains a new section titled 6.8 Handling Multilingual Text in 11.4 which answers the question
Does LANSA know the correct CCSID to use for Multilingual text?
This new section contains information and recommendations relating to the functionality used for multilingual text when checking in/out multilingual text in all LANSA object types (11
SP4 and later). It is also used when exporting to Windows and
when compiling text in all objects on Windows and RDMLX objects on System i in LANSA V11 and later. Existing multilingual text may be affected if for example, the CCSID associated with each partition language doesn't match the intended execution environment or if literals are used in
RDML/RDMLX code instead of in *MTXTs. Refer to 6.8 Handling Multilingual Text in the Multilingual Application Design Guide for full details.
|
25 January 2008 - From V11 SP4
Visual LANSA abnormally shuts down with an access violation in LXPPRBLD.EXE if a literal in the RDMLX contains
special characters. For example, the following code would not be accepted
DEFINE FIELD(#STRING1) TYPE(*CHAR) LENGTH(3) DEFAULT('ab')
The following error message will be displayed:
"LXPPRBLD.EXE has encountered a problem and needs to close. We are sorry for the inconvenience."
LANSA recommends that the use of special characters in literals (such as linefeed, carriage return, binary zeroes, etc.) for both LANSA for iSeries and Visual LANSA
is implemented via the specialized BIFs HEXTOBIN and BINTOHEX instead of via LANSA defined fields.
|
2 January 2008 - V11
Oracle PC Other Files with numeric columns where scale is greater than precision may have problems in LANSA V11.
For example, LANSA V10.0 incorrectly allowed the load of an Oracle 5,10 column as a LANSA
Signed(5,9) field. LANSA does not expect or support the decimals for a numeric field being greater than the length. The load defect is fixed in
V11
in that LANSA will attempt to load one of these columns as a field that is valid to LANSA.
If you encounter any issues with Oracle PC Other Files containing such numeric columns, you must resolve the problem in V11 by deleting any fields that have been loaded incorrectly, reloading the Oracle PC Other File, and recompiling/redeploying all objects that use the
fields.
|
13 December 2007 - V11
Syntax checking in Visual LANSA V11 has been tightened
so that it agrees with LANSA for iSeries syntax
checking. RDML code that was allowed in previous
versions of Visual LANSA may generate Full Function
Check (FFC) errors after upgrading to V11. Only code
that is not allowed on System i will generate syntax
errors. Note: this issue will not be observable
until existing source is opened in the V11 Visual LANSA
Editor, at which time it can be corrected.
Examples:
A single quote followed by another single quote is not
valid syntax in a parameter
e.g. use builtin(TCONCAT) with_args(#STD_CODE '')
Code of the syntax format Keyword Space Value is not
valid syntax
e.g. select *all from_file filea with_key(#key1)
|
13 December 2007 - V11
Define_com commands cannot use the same name for the
component as an existing repository field.
|
13 December 2007 - V11
You cannot specify the same field in *Received and
*Returned parameters of the SUBROUTINE command.
|
13 December 2007 - V11
The default intermediate precision used for CHANGE
commands in RDMLX code has been corrected to produce the
same result as RDML code on System i. This ensures that
the same results are produced across all platforms and
in RDML and RDMLX code. Note: that for
calculations where the accuracy of decimal precision is
important, the PRECISION parameter of the CHANGE command
must always be used.
|
13 December 2007 - V11
CHANGE and ASSIGN commands now correctly remove trailing
blanks when assigning an Alpha or Char field type to a
String field type.
|
13 December 2007 - V11
Combo-box height may be different after an upgrade to
V11. This is linked to the font used in V11. The
combo-box height changes to facilitate the font used. To
allow fixing of the height, a new property has been
added to the combo-box called "FixedHeight" which can be
used to set the height manually.
|
13 December 2007 - V11
OTHER files with non-keyed logical views that may have
been converted to LANSA files in previous versions of
LANSA will generate a warning message that the non-keyed
logical views will have to be deleted before they can be
loaded into the V11 Visual LANSA Editor.
|
13 December 2007 - V11
If SQL Server is used as the database:
The existing database/configuration should be upgraded,
rather than creating a new database/configuration and
importing objects. Refer to:
Support for SQL Server 2000 and SQL Server 2005
collections in Visual LANSA 11.3 (CU3)
ODBI=1, previously required for many applications due to
blocked connections, is now no longer required for most
applications. Refer to
Blocked connections with your SQL Server implementation
|
6 June 2005 - V11
After installing Visual LANSA V11 on
a system that already has Microsoft Visual C++ 6.0
installed, LANSA components may not compile
successfully. Refer to
Using Microsoft C++ 6.0 compiler with Visual LANSA V11
for full details and steps to
correct.
|
22 April 2005 - V11
After installing or upgrading, your dongle may not
be recognized. Installing the latest dongle drivers
will resolve this issue. See the Updated
driver for USB dongles Tip
for further information.
|
15 April 2005 - V11
When installing or upgrading,
your dongle should NOT be connected.
See the
USB dongles on various platforms Tip
for further information.
|
15 April 2005 - V11
When installing Visual LANSA do
not use a period/full stop (".") in
the name of the Visual LANSA install
directory.
|
15 April 2005 - V11
Avoid running multiple network
client installs simultaneously. This
may result in database locking
conflicts.
|
15 April 2005 - V11
You cannot install V11 or
upgrade to V11 on machines running the Windows NT
(Server and Workstation) operating system. The upgrade will generate
a message that no configuration
exists that can be upgraded to V11 and will not continue. For details
of supported configuration please
refer to the LANSA
Version 11 Supported Platforms
|
|
Visual
LANSA Framework |
13 December 2007
If you have amended the Visual
LANSA Framework shipped components, your changes will be
over written when you upgrade to V11 or apply a Visual
LANSA Framework EPC. Note: All the Visual LANSA
Framework shipped components (VF_<form name>) come with
a disclaimer highlighting that changing shipped
components is not recommended.
|
|
LANSA Composer |
25 March 2009 - V2.0
Previous versions of LANSA Composer compiled the generated Java code for Transformation Maps for target Java version 1.4.
To accommodate recent and future versions of Altova MapForce, version 2.0 of LANSA Composer has been changed such that:
- You can specify (in System Settings) the Java version to target
- The default value (including for an upgraded installation) is now 1.5
If the JVM on your System i or Windows server is running at version 1.4, the compiled code that results when you prepare Transformation Maps with the default setting in this version of LANSA Composer will not be compatible with your JVM.
To address this, you should do one of the following:
a) Change the "Java version for Transformation Maps" value in System Settings to be compatible with the JVM version you are using.
b) Change the LANSA Integrator configuration on your System i or Windows server to use a JVM version 1.5 (or later). Refer to How to Confirm JAVA Version on iSeries for guidance in connection with your System i server.
Note that Java code generated for maps created with MapForce 2009 or later will require at least Java version 1.5. Therefore the second option is recommended. If you do not choose this option now, it will become necessary at a later time.
|
20 March 2009 - V2.0
When the SMTP_MAIL activity is used with attachments
several times in one processing sequence, the
attachments accumulate such that each email includes
both its own and previous attachments. This issue is
corrected in hotfix 001 for LANSA Composer Version 2.0.
This hotfix is supplied on the LANSA Composer Windows
Client Version 2.0 CD and instructions to apply it are
included in the Read Me supplied on the CD. Application
of this hotfix is highly recommended if you presently
use or will use the SMTP_MAIL activity.
|
20 March 2009 - V2.0
An enhancement is available for LANSA Composer version
2.0 that enables dynamic class loading for the
transformation map Java classes. The effects of this new
behaviour include:
• no need to restart JSM after preparing or deploying
maps
• maps prepared with different versions of MapForce can
co-exist
• no need to rebuild maps following a MapForce upgrade
To enable this enhancement you must first apply EPC840
to LANSA Integrator on the LANSA Composer server. Then
you must apply hotfix 002 for LANSA Composer version
2.0. As a part of the procedure to apply hotfix 002, you
must MOVE your existing transformation map .jar files.
Both EPC840 for LANSA Integrator and hotfix 002 for
LANSA Composer Version 2.0 are supplied on the LANSA
Composer Windows Client Version 2.0 CD and instructions
to apply them are included in the Read Me supplied on
the CD. Application of this hotfix is highly
recommended.
|
|
LANSA Client |
1 June 2009 - V11 SP5 & EPC814
LANSA Client V11 SP5 no longer bundles Crystal Reports.
However, all existing queries (output to report) will still work with LANSA Client V11 SP5.
LANSA Client V11 SP5 supports the current supported version of Crystal Reports (CR 2008).
EPC814 enhances LANSA Client V11 SP5 to allow you to avail of the free Crystal Reports 2008 runtime
engine. Refer to EPC814.htm
for further details.
|
8 February 2007 - From V11.3
Crystal Reports XI cannot open DBF file created in LANSA Client 11.3
Refer to A DBF file created with LANSA Client
11.3 will not open when creating a report with Crystal Reports
XI
|
5 February 2007 - V11.3
Pre-requisites EPC listed in
the What's New in LANSA Client V11.3 (Readme)
The What's New in LANSA Client V11.3 (Readme) lists
EPC790 as the only pre-requisite backend server EPC: You must have applied epc790 or later to your server to support LANSA Client V11.3
However, both EPC790 and EPC800 are required as
pre-requisite EPCs. EPC790 and EPC800 are shipped on the
LANSA Client CD in the \EPC folder or can be downloaded
from the EPC
section of the LANSA Web site.
|
|
Documentation |
13 March 2008 - V11 SP4 This issue is resolved
in SP5
The LANSA Integrator guide shipped with SP4 makes
references to LANSA Integrator features that are not
available in the LANSA Integrator software shipped with
SP4. To avoid confusion, you can should download the
LANSA Integrator guide that is available in the documentation
section of the LANSA web site.
|
|
LANSA
for the Web |
14 August 2009 - V11 SP5 EPC845
Blank fields in WAMs are padded with a single blank after applying EPC845.
When using lists in WAMs, at runtime this renders default values to blanks rather than stripping the value.
When viewed on a web browser users may experience
unexpected behavior. For example, not being able to type in a value or tabbing between fields causes the entire blank fields to be highlighted or if you click on an entry field the cursor ends up after the blank.
An EPC845 hotfix is available to
correct this problem. Contact you local LANSA vendor to
request this hotfix.
|
3 August 2009 - V11 SP5
EPC845 ships the latest fixes and enhancements
for V11 SP5 and supersedes all previous V11 SP5 EPCs.
EPC845 also delivers support for the LANSA for UNIX (Linux) release
more...
|
24 October 2008 - V11 SP5
After applying V11 SP5 to your LANSA for web windows web
server, you may encounter the following error on the
browser if you specify a port number on your URL
Unable to transform input XML
A hotfix is available to correct this problem.
Contact you local LANSA vendor to request this hotfix.
|
13 March 2008 - From V11 SP4
There was a change made in SP4 for V11 to prevent the DISPLAY/REQUEST/POP_UP command from being executed more than once in one web function request.
The consequences of this change has the potential to affect a currently working LANSA for the web application.
Refer to After applying SP4
an existing web application may start generating fatal
errors
|
29 February 2008 - From V11 SP4 - WAMs
only
As part of an ongoing program to improve WAM performance
and browser compatibility, a number of weblets have been
revamped or rewritten in V11 SP4. To avoid backward
compatibility issues, new "v2" versions of the
weblets have been created. Your application will have to
be updated to avail of these new "V2" weblets.
Refer to Revamped or
rewritten weblets in V11 SP4 to improve XSLT performance
and browser compatibility of WAMs
Note: If you have
created your own style and script weblets that do not call the
standard weblets, then you may have problems after installing
this Service Pack. In this case, you should make the modifications
detailed in the WARNING
section in the tip prior to applying this service pack.
|
13 December 2007 - Webevent All Versions
The upload program (as provided in SET181UPLO in the
SET material) can stop functioning after upgrading to V11
if you also upgrade to V5R3 and use Apache as the
HTTP Server. SET181UPLO can
be changed to upload files into the IFS using Apache
|
28 July 2006 - From V11.3 - WAMs only
Ending presubmit JavaScript with '//' no longer cancels onclick event.
This was a technique that might have been used but in
11.3 (CU3) the behavior will change.
Refer to Ending presubmit JavaScript with '//' no longer cancels onclick event in
11.3 for full details.
|
25 July 2006 - From V11.3 - WAMs
only
Correct usage of WEB_MAP FOR(*NONE) and WEB_MAP FOR(*INPUT) in WAMs
enforced in V11.3.
Refer to Using WEB_MAP FOR(*NONE) and WEB_MAP FOR(*INPUT) in WAMs
for full details.
|
|
LANSA for iSeries |
2 September 2009 - V11 SP5 EPC845
Fix required for applications accessing an IBM i in superserver mode after applying EPC845.
An issue has been found where applications accessing an IBM i via superserver (either to an RDMLX server or using the DEFINE_ANY_SERVER) may experience access violation errors during SELECT/FETCH statements. This can occur if the previous I/O resulted in an error or record not found; the subsequent I/O request (even to a completely different file) will fail with a pointer error in the iSeries joblog:
MCH3601 Escape 40 31/08/09 11:10:57.421664 X_SSV
From module . . . . . . . . : X_SSV1
From procedure . . . . . . : Handle_X_CID_CALL_IOMODULE
Statement . . . . . . . . . : 234
To module . . . . . . . . . : X_SSV1
To procedure . . . . . . . : Handle_X_CID_CALL_IOMODULE
Statement . . . . . . . . . : 234
Message . . . . : Pointer not set for location referenced.
Cause . . . . . : A pointer was used, either directly or as a basing
pointer, that has not been set to an address.
The issue does not occur if all OAMs accessed have been rebuilt with EPC845.
A fix for EPC845 is currently in progress and will be
made available ASAP.
|
4 August 2009 - V11 SP5
If you are performing a LANSA for iSeries upgrade and your site has the following environment
- multiple LANSA systems on your system i
- upgrading one of the LANSA systems from V10.0 to V11 SP5
- the last system in the list of installed LANSA systems is already at V11 SP5 **
Then, the following error will be generated when upgrading the V10.0 system.
This LANSA library <PGMLIB> is the same version and cannot be upgraded
** you can determine this using the following command
WRKOBJ OBJ(*ALL/DC@A01) OBJTYPE(*DTAARA)
You should contact your local LANSA Vendor for instructions on how to complete the LANSA
upgrade.
|
3 August 2009 - V11 SP5
EPC845 ships the latest fixes and enhancements
for V11 SP5 and supersedes all previous V11 SP5 EPCs.
EPC845 also delivers support for the LANSA for UNIX (Linux) release
more...
|
21 May 2009 - V11 SP5 & EPC838
After applying EPC838 to LANSA on iSeries, a fatal error
PROGRAM DC@P2002 ENCOUNTERED AN UNEXPECTED ERROR will be
generated when compiling a file after adding, changing
or deleting a validation rule via LANSA for iSeries
development screens. An EPC838 patch is available to
correct this problem. Contact you local LANSA vendor to
request this patch.
|
4 August 2008 - V11 SP4 ONLY This issue is
resolved in SP5
Integer(1) fields have been stored and retrieved incorrectly from the database on the iSeries if they have a negative value, however within LANSA they have retained the correct value. Within LANSA if the Integer(1) field is used as a key, then a keyed access using the negative value will fail to retrieve the record. Outside of LANSA, external access (for example interactive SQL or query) will show that the field with a negative value contains the wrong value.
User Action: After upgrading to SP5, recompile any files in an RDMLX partition that contain Integer(1) fields on iSeries. In addition, ensure that any negative values are corrected after recompilation. Please contact your product vendor if you require assistance with
this task.
|
30 May 2008 - V11 SP4 ONLY This issue is
resolved in SP5
If you compile OAMs at SP4 level and also compile some, but not all, functions and components that access this
OAM in the one job or superserver session on iSeries, an error will be generated.
For example, if a function or component compiled prior to SP4 uses an OAM compiled on SP4, then a function or component compiled on SP4 attempts to use the same OAM in the same job or superserver session, then an IOM0033 message is issued and ER is returned.
IOM0033: I/O request to file xxxxx(the file name that is accessed). *LIBL [member *FIRST] is invalid at this time
One workaround is to recompile all functions/components in SP4 that access the file.
However, an EPC has been produced to resolve this issue.
EPC827 for SP4 is downloadable from the EPC
section of the web site.
Note: After applying this EPC, you will be required to recompile any
OAMs in an RDMLX partition that have been compiled in SP4 prior to this
EPC being applied. Refer to EPC827 User Actions.
|
13 December 2007 - V11
If you have RDML code containing hexadecimal literal
values (X'nn') and you intend to use Visual LANSA for
editing your source code then you MUST modify your code
to no longer use these hexadecimal literal values
directly before you start using Visual LANSA. The RDML
must be changed as it will be corrupted when using
Check-out from the System i to Visual LANSA. Note:
Hexadecimal literal values are not supported by the
Visual LANSA IDE in any form.
|
13 December 2007 - V11
Due to its lack of support for lowercase directory
names, CCSID 5026 is not supported in V11. Upgrading
LANSA on a System i that uses CCSID 5026 may cause
problems for LANSA systems that use the Integrated File
System (IFS).
|
13 December 2007 - V11
The shipped DC@OSVEROP data area now sets *RPGIV and *ILE
by default with V11. This specifies that each program
is to be compiled using RPG/IV code, then bound as an
ILE type program. The compile will also statically bind
any multilingual program into the function program and
use supplied service programs to dynamically call (CALLB)
LANSA internal programs.
|
24 July 2006 - V11
How to avoid MCH3402 errors when repeatedly running RDMLX functions on iSeries
after checking and compile during development.
Refer to Checking in RDMLX function
results in Process not getting found in the reused job
for full details.
|
|
LANSA
Integrator |
23 October 2008 - All versions
Installing or upgrading 3rd party software may cause
your existing working LANSA Integrator application to
fail with a licence error. Refer to Installation of 3rd party software affects LANSA Integrator license
on System i for further details and resolution.
|
13 March 2008 - V11 SP4 ONLY This issue is
resolved in SP5
The LANSA Integrator guide shipped with SP4 makes
references to LANSA Integrator features that are not
available in the LANSA Integrator software shipped with
SP4. To avoid confusion, you should download the
LANSA Integrator guide that is available in the documentation
section of the LANSA web site.
|
9 December 2005 - V11.0
Correction and clarification
of post Installation steps required after a new V11.0
LANSA Integrator installation.
Correction:
1. After completing a new V11.0 LANSA Integrator
installation, the HTTP server instance will contain the
following incorrect entry:
ScriptAliasMatch ^/cgi-bin/jsmdirect(.*) /QSYS.LIB/JSMLIB.LIB/JSMLIB.PGM$1
This entry is incorrect and should be JSMDIRECT.PGM$1 ie.
ScriptAliasMatch ^/cgi-bin/jsmdirect(.*) /QSYS.LIB/JSMLIB.LIB/JSMDIRECT.PGM$1
And the following directives must also be correctly
added:
ScriptAliasMatch ^/cgi-bin/jsmproxy(.*) /qsys.lib/JSMLIB.lib/jsmproxy.pgm$1
ScriptAliasMatch ^/cgi-bin/jsmadmin(.*) /qsys.lib/JSMLIB.lib/jsmadmin.pgm$1
Note: The example IBM Apache HTTP Server and HTTP Server
configurations contain the correct directives.
Remember that JSMLIB.lib
needs to be changed to your JSM
library name.
Clarification:
1. In 8.1 Task: Configure the Java Service Manager on
iSeries, section Step 3. Check configuration values
of the Install LANSA on iSeries guide, you must ensure
that you have JSM started before performing the following step:
Use menu option 4 Edit Manager Properties of the Java Service Manager Administrator Menu, to display the contents of the manager.properties file.
If JSM is not started before performing this step, the properties file will be empty.
|
15 April 2005
When the installation is
completed a separate job is
submitted to optimize Integrator Jar
files. This job will run in the
background and may take up to
several hours to complete.
|
|
Visual LANSA
