EPC - 130400

Date : February 13 2013

EPC130400 Mandatory fixes for V13 - All previous levels of V13 become unsupported with the release of this EPC

  • This EPC must be installed. It becomes the minimum supported EPC level for V13.
  • This EPC corrects a runtime security issue and must be applied.
  • This EPC also corrects Repository corruption after check-in.
Product Visual LANSA and LANSA for iSeries
Version 13
Pre-Requisite Details 130300
Related Products None
Special Notes All Version 13 Visual LANSA EPCs include updates that must be applied to Windows and IBM i systems (Independent Visual LANSA development environments only require the Windows updates). Failure to upgrade both sides of a development environment will render the Host Monitor and Super Server applications inoperable. Attempting to use the Host Monitor and Super Server applications without having applied the EPC to both sides of a development environment will generate an EPC mismatch error.

Make a full backup of your LANSA environment on each platform to which this EPC will be applied.
IBM i Specific Special Notes The IBM i instructions are expedited procedures that assume a sound knowledge of IBM i.
You should use a user profile that is QSECOFR, part of the QSECOFR group, or, has *ALLOBJ and *SECADM special authorities.
You must end the web server and run the LANSA for the Web cleanup program before applying this EPC.

You must end the Listener and Host Monitor if active.
You must end the LANSA Integrator server if it has been used with the LANSA system to be updated.
User Actions The following CCS items require user action: 0148234 IBM i: SQL0204 error when long names for files are less than 9 characters long See below for details.
Document Updates This EPC does not contain updates to any guides.

The latest guides available at www.lansa.com/support/docs/update.htm
Hotfixes The following Hotfixes will be replaced by this EPC:

Instructions to install the EPC

EPC130400 includes software to be installed on an IBM i machine and on a Windows machine. These instructions describe the installation and use of all delivered items.

  1. Download EPC130400.EXE file from the Web site or email.
  2. Unzip (double click) EPC130400.EXE. These files will be extracted:
    • EPC130400.htm - this document
    • EPC130400 - IBM i Save file
    • EPC130400w.exe - Windows Visual LANSA install executable

Instructions provided for

Detailed changes

CCS id. Description
DBCS input in IME not selected by default in a memo box

VisualMultilineEdit failed to select full width hiragana in the Japanese IME when it receives focus. It will now do so if it has a datacolumn with Keyboard Shift O.
Stop CPF8350 from being written to joblog on RDMLX environment shut down
Error compiling file with virtual field code fragments in V13, OK in V12 SP1

Some virtual field definitions would produce an incorrect error "xxx is not a valid name" when compiling the corresponding file.
0148142 Can't define PJF with longnames in V13
0148185 Unicode data incorrectly validated for DBCS for WAM
0148191 Prompter missing on Access Route key field
0148234 IBM i: SQL0204 error when long names for files are less than 9 characters long

IBM does not support alternate file names < 9 characters so the Identifier will be used when creating the files.

User Action:
If your RDMLX partition is Enabled for Long Names AND with version 13 you have created LANSA physical files or logical views with mixed case or lower case names less than 9 characters long: Rebuild the Tables, Indexes and OAMs on Windows and IBM i (check all rebuild options) and also rebuild any functions (on Windows and IBM i) that use SELECT_SQL against the files.
0148332 DEF_ARRAY defined in PRIM_OBJT reusable part fails to compile

Using expandable groups in the OF_FIELDS parameter of the DEF_ARRAY command failed to compile.
Keys dropped from access route during checkin
0148349 ADD_ENTRY abending in User Designed Control
0148350 Virtual Field calculation rounding issue
0148382 V13 external resource check-in fails with authorization error

The actual issue is related to introduction of long names. When checking in the object the long name was being used, and truncated, which caused operation to fail.
0148424 Cannot compile when using SELECT/OMIT created on IBM i Master system
0148474 Correct runtime security issue

Affected objects

Object Name Object Type
liih.exe \LANSA
liio.dll \LANSA
liiosrv.dll \LANSA
liiv.dll \LANSA
x_prim.dll \LANSA
levacc03.dll \X_WIN95\X_LANSA\Execute
lh_ideri.dll \X_WIN95\X_LANSA\Execute
lxptbbld.exe \X_WIN95\X_LANSA\Execute
x_dbmms.dll \X_WIN95\X_LANSA\Execute
x_dnp.dll \X_WIN95\X_LANSA\Execute
x_funms.dll \X_WIN95\X_LANSA\Execute
x_netdnp.dll \X_WIN95\X_LANSA\Execute
x_pdfms.dll \X_WIN95\X_LANSA\Execute
x_prim.dll \X_WIN95\X_LANSA\Execute
x_funstr.h \x_win95\x_lansa\source
Object Name Object Type Library
X_BASE *SRVPGM LANSA program library
X_COMP *SRVPGM LANSA program library
X_DBG *SRVPGM LANSA program library
X_DBM *SRVPGM LANSA program library
X_FUN *SRVPGM LANSA program library
X_PDF *SRVPGM LANSA program library
X_PRIM *SRVPGM LANSA program library
X_VAR *SRVPGM LANSA program library
[email protected] *PGM LANSA program library
x_funstr.h STMF ../x_lansa/source

Install Instructions

  1. Sign on with QSECOFR user profile, part of the QSECOFR group or a user profile that has *ALLOBJ and *SECADM special authorities.
  2. Backup all the LANSA folders, system libraries and ALL the LANSA IFS objects (LANSA_pgmlib/x_lansa) before applying this EPC
  3. You need exclusive use of the LANSA system before applying the EPC. To check for active users refer to Appendix B How to check for Active Users in the Installing LANSA on IBM i guide for instructions.
  4. End the Listener, Host Monitor and Web Server for the LANSA system and run the LANSA for the Web cleanup program.
  5. Move the unzipped file EPC130400 to an IFS folder on the IBM i ( e.g. /LANSA_pgmlib/tmp/epc130400 )
  6. For this EPC use the following options:
    1. Install the EPC from = *IFS
    2. Apply this EPC to = FULL_LANSA_SYSTEM
  7. Run the following command before the LOADEPC command to avoid having to add the LANSA program library to the jobs library list.
    CHGCMD CMD(pgmlib/LOADEPC) PGM(pgmlib/[email protected])
  8. Run the command LOADEPC with the following parameters:

    pgmlib/LOADEPC and press command 4 (F4) to prompt the command (can be run in batch)

    EPC number . . . . . . . . . . . > 130400
    Install the EPC from . . . . . . >*IFS
    IFS Path and object name . . . .e.g./LANSA_pgmlib/tmp/epc130400
    Apply this EPC to . . . . . . . FULL_LANSA_SYSTEM
    LANSA program library . . . . . pgmlib

  9. Sign off and then on again before commencing the next installation, e.g.:
    • to apply this EPC on another LANSA system
    • to apply another EPC on the same LANSA system
  1. Recommend that a backup be done of all LANSA folders and your LANSA database before applying this EPC.
  2. Stop using the LANSA development environment and stop all currently executing LANSA applications.
  3. Double-click on EPC130400w.exe.
  4. Select the "Setup" button or "Cancel" if you do not want to proceed.
  5. If you have multiple configurations installed, Select the configuration to which the EPC is to be applied.
  6. If you are prompted to reboot your pc - please reboot.
  7. To view details of the installed EPCs:
    1. sign into LANSA
    2. view the Help menu
    3. Product Information option
    4. then select the Installation Details tab
    5. expand the Installation/ EPC Summary
    6. review the last entries

© 2013 LANSA