LANSA for iSeries Resolved Issues

Page 1 of 2

• Prompting on some LANSA commands in the LANSA for iSeries editor causes the command parameter to be filled with *N
  - LANSA for iSeries All Versions
  When using prompt on a command (F4) and inputting some valid values, on returning to the editor, some of the command parameters are filled with *N characters.
• Message stating LPCMN.BND not found when executing RDMLX function/WAM/Component on iSeries
  - LANSA V12
  LANSA can issue an error stating LPCMN.BND is missing even though it does exist.
• Export lists not created even when selected in the Deliver To
  - LANSA V12
  After enabling the Create Export List in Deliver To the export list isn't created.
• Install or upgrade can fail if the job message queue reaches maximum size
  - LANSA for iSeries All Versions
  The job message queue reaches maximum size causing upgrade to fail.
• Changes to IBM SQL Engine affects performance in Logical Views keyed by numeric fields
  - LANSA for iSeries V11 SP5
  Logical Views keyed by Numeric fields using UNSIGNED ordering will suffer performance problems at runtime on V6R1 systems and V5R4 environments with certain PTFs applied.
• Multiple CPYTOIMPF or CPYFRMIMPF commands fail when run in an RDMLX partition in SP5
  - LANSA for iSeries V11 SP5
  A change in V11 SP5 causes multiple CPYTOIMPF or CPYFRMIMPF commands to fail when run in an RDMLX partition.
• PTFs required for the creation and restoration of programs and service programs on V6R1
  - LANSA for iSeries
  Essential IBM PTFs required to improve performance when running OS V6R1.
• Fatal error when debugging in VL to System i after applying EPC834 to V11 SP5
  - LANSA for iSeries V11 SP5
  Fatal error with missing LXQUEUE when debugging in VL to System i after applying EPC834 to V11 SP5.
• Crossed Update error message when accessing Logical Views on Other Files
  - LANSA for iSeries All Versions
  Crossed Update checking may return a false positive when accessing a logical view which contains only a subset of the physical file fields.
• Unable to restore V11 SP5 objects to QTEMP on V5R3 or V5R4
  - LANSA for iSeries V11 SP5
  Full support of IBM i 6.1 in V11 SP5 may require users of V5R3 and V5R4 to apply necessary IBM PTFs in order to restore SP5 objects.
• Unable to start up LANSA Listener because of port number conflicts
  - LANSA for iSeries
  LANSA listener default port number 4545 conflicts with other third party software.
• C2M3044 error using a key with length greater than 2000 bytes
  - LANSA for iSeries V11.3
  Total length of a key allowed in V5R4M0 increased from 2000 bytes to approximately 32K bytes but I/O fails with C2M3044 error.
• Extra objects required to use PASE libxslt after upgrading OS/400 to V5R3 and above
  - LANSA for iSeries V11.3
  Extra objects need to be restored to use PASE libxslt as the XSL Processor if LANSA V11 is installed prior to upgrading OS/400 to V5R3 and above.
• LANSA for iSeries V11.3 install fails to read 2nd CD
  - LANSA for iSeries V11.3
  LANSA for iSeries V11.3 install fails to read 2nd CD when using Virtual Optical Devices with Image Catalog.
• MCH3601 QC2POSIX error on V5R1 after applying EPCs to LANSA 11.3
  - LANSA for iSeries V11.3
  QC2POSIX error on V5R1 after applying post CU3 EPCs.
• Using LANSA V11.0 with DBCS languages does not execute correctly
  - LANSA for iSeries V11.0
  Important notes for DBCS languages in LANSA V11.0.
• Cannot run Open Systems Utility (OSU) after upgrading to V11.3 (CU3)
  - LANSA for the Web V11.3
  LANSA Version Number changes to V11.3 when upgrading to CU3, however the OSU is still on V11.0.
• How to avoid MCH3402 errors when repeatedly running RDMLX functions on iSeries after checkin and compile
  - LANSA for iSeries V11.0
  Checking in RDMLX function results in Process not getting found in the reused job.

Page 2 of 2

• Creating a new partition after applying CU3 to V11.0 system
  - LANSA for iSeres V11.3
  Creating a new partition and using the Partition Initialization after applying CU3 to V11.0 system.
• Compile failures with error MCH3203 in joblogs
  - LANSA for iSeries V11.0
  Compiles on iSeries of objects that generate C can fail with error MCH3203 in the joblog.
• Cannot get past Existing LANSA Communications Directory prompt in Setup during upgrade to 11.0
  - LANSA for iSeries V11.0
  If the communications directory name in data area DCXLOADA01 is blank, the installer will not accept any value entered into the communications directory prompt.
• When signed into LANSA on the iSeries; checked in changes made to an RDMLX function appear to have NOT taken effect
  - LANSA for iSeries V11
  When signed into LANSA on the iSeries; checked in changes made to an RDMLX function appear to have NOT taken effect until logging out of LANSA on the iSeries and then back in again.
• Recursive Triggers in an iSeries RDMLX Partition can loop indefinitely
  - LANSA for iSeries V11.0
  When using Triggers in a RDMLX partition running on the iSeries, make sure that there isn't a recursive call back to the original trigger call.
• "QSYSINC library not found" during checkin and compile of RDMLX object on iSeries
  - LANSA for iSeries V11.0
  Error generated during checkin and compile of RDMLX object (eg. WAM) caused by IBM QSYSINC library not installed.
• LANSA iSeries upgrade failure due to QSHELL or MAXJOB settings
  - LANSA for iSeries
  LANSA install/upgrade can fail if it uses a jobq/subsystem that does not allow QSHELL jobs to run or there is not enough MAXJOBs value for the subsystem.
• LANSA for iSeries upgrade to V11.0 fails due to existing old version of OSU
  - LANSA for iSeries V11.0
  An upgrade to V11.0 on iSeries can fail with error messages in the joblog.
• Loading Demo Data on iSeries in V11.0 does not complete successfully
  - LANSA for iSeries V11.0
  Once the Install/Upgrade to V11.0 completes or EPC751 is applied to V11.0, a data problem prevents the Install Demonstration Data function from ending successfully.
• Cannot start LANSA after upgrade to V10.0
  - LANSA for iSeries & LANSA for the Web V10.0
  You may experience an error after upgrading to V10 of LANSA and are trying to login to LANSA.
• Accessing a file through different access paths (e.g. *OPNQRYF, POINT) in the same Function
  - LANSA for iSeries
  You can access the same file through different access paths (e.g. standard SELECT, FETCH, using POINT or *OPNQRYF) as long as you close the file path after being processed.
• Possible problem when creating new partition
  - LANSA for the AS/400
  Creating a new partition fails when using a number as the unique identifier prefix.
• DB2/400 constraints and LANSA
  - LANSA for iSeries
  It is not recommended to use DB2/400 constraints on LANSA applications. However, it is possible to detect and make them appear like LANSA validation errors.
• About LANSA's multilingual support
  - LANSA for the AS/400 and LANSA for Windows
  Changing partition multilingual attributes.
• *DBMS_RECORD_LOCKED must be used only if there was an I/O error
  - LANSA for the AS/400
  The *DBMS_RECORD_LOCKED variable is used to detect if the previous I/O operation (e.g. SELECT or FETCH) failed because the record was locked during the allowable wait time.

Archive

• Intermittent compile error CPF9872 in LANSA for iSeries
  - LANSA for iSeries
  The iSeries compiler fails intermittently with CPF9872 RC4 indicating that program QWXCRTMD has ended unexpectedly.
• Security error in the LANSA Listener TP jobs after applying EPC734 to V5R1 or V5R2
  - LANSA for iSeries
  A security error can be generated after applying EPC734 to V5R1 or V5R2 if certain PTFs have not been applied.
• LANSA for the iSeries and API changes introduced in i5 from V5R3 and above
  - LANSA for iSeries V10.0
  LANSA for the iSeries V10.0 and QSYGETPH in i5 V5R3 and higher.
• Domino Integrated BIFs fail when using DOMINO 6.5
  - LANSA for iSeries
  Pointer error during the open database when using DOMINO 6.5 with LANSA for the Web.
• Partition security officer not allowed to configure communications routing table
  - LANSA Communciations
  Partition security officer not authorised to edit the communications routing table.
• Functions will not compile after install of LANSA/AD
  - LANSA/AD
  After a successful install of LANSA/AD functions fail to compile with a CPD0162 error in the joblog.
• LANSA for the AS/400 compiler errors in the generated DDS
  - LANSA for the AS/400
  Various LANSA for the AS/400 compile errors found in the generated DDS listing.
• The effect of using triggers to evaluate virtual fields in LANSA for iSeries and LANSA Open
  - LANSA for iSeries and LANSA Open
  A SELECT with a WHERE condition is evaluated slightly differently on LANSA for iSeries and LANSA Open (and LANSA Client).
• Printing in A4 format in LANSA for the AS/400
  - LANSA for the AS/400
  A printed document might not have A4 format although the printer file has A4 format in its definition.
• Error When Using an OTHER file with DATESTAMP field
  - LANSA for the AS/400
  An error can occur when compiling an OTHER file defined in LANSA for the AS/400 with a Datestamp field.
• Recreation of I/O Module Fails after a Field has been Deleted
  - LANSA for Windows and LANSA for the AS/400 all Releases
  After deletion of a field from a file definition, the I/O module recompilation fails.
• Compiler error CPF6301 when compiling I/O Module (IRP with errors)
  - LANSA for the AS/400
  CPF6301 error is issued by the RPG compiler even when there are no errors in the compilation's Message Summary.
• Problem with Full Function Checks and compiles
  - LANSA for the AS/400 All Releases
  Full Function Checks (FFCs) and compiles are failing with error CPF4102, DC@F33 in DC@DTALIB member NOT_AVAIL not found.
• Exporting/Importing
  - LANSA for the AS/400 All Releases
  An import finishes with 7 completion messages, no warnings and no fatal errors. However, no object appears to have been imported.
• Large number of fields in a file affect performance
  - LANSA for the AS/400
  The number of fields in a file can affect application performance but only if very large numbers are involved.
• Using "Optimize for Remote Communications"
  - LANSA for the AS/400
  Functions compiled on a process with the "Optimize for Remote Communications" flag set to 'Y' can cause unexpected results..