EPC - 838

Date : 1st April 2009

EPC838 Highlights

This EPC delivers 

Get this EPC

Download EPC838 via the LANSA Support Portal

Product Visual LANSA and LANSA for iSeries
Version 11 SP5
Pre-Requisite Details EPC834 and IBM supported operating systems
Related Products None
Full Distribution In V12
Special Notes

All Version 11 SP5 Visual LANSA EPCs include updates that must be applied to Windows and System 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.

System i Specific Special Notes The System i instructions are expedited procedures that assume a sound knowledge of i5/OS.
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 CCS items 137189/137217 require user action. 
Note: EPC837 included CCS items 136567, 136628, 136667 and 136981 that required user action.
See below for details
Document Updates Updates to these guides are provided:
  • lansa009.chm Introduction to LANSA for iSeries Guide
  • lansa013.chm Visual LANSA Developer Guide
  • lansa015.chm Technical Reference Guilde
  • lansa016.chm Visual LANSA Feature Help
  • lansa020.chm Deploying Visual LANSA Applications Guide
  • lansa065.chm LANSA Application Design Guide

The guides updated by EPC are only placed in the default LANSA documentation location as installed with Visual LANSA. This default location is ...\x_win95\x_lansa\execute\eng directory. If you installed the LANSA documentation (default folder ...\lansadoc\) from the LANSA Windows CD-ROM, you should manually copy the updated guides to those folders.

The latest guide updates are also available at http://www.lansa.com/support/docs/update.htm

Hotfixes

The following Hotfixes will be replaced by this EPC:
Windows:
EPC830HF-081120
EPC830HF-081120a
EPC830HF-081120b
EPC830HF-081202
EPC830HF-090122
EPC830HF-090202
EPC834HF-081201
EPC834HF-081203
EPC834HF-081211
EPC834HF-081216
EPC834HF-081217
EPC834HF-081223
EPC834HF-090109
EPC834HF-090114
EPC834HF-090116
EPC834HF-090129
EPC834HF-090129a
EPC834HF-090209
EPC834HF-090219
EPC834HF-090226
System i:
EC830P07
EC834P01
EC834P02
EC834P03
If you have applied a patch to your environment that is not listed here contact your local LANSA vendor for instructions before applying the EPC.

Instructions to install the EPC

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

  1. Download EPC838.EXE file from the Web site or email.
  2. Unzip (double click) EPC838.EXE. These files will be extracted:

Instructions provided for:

Yes LANSA for iSeries
No System i Web Server (multi-tier)
Yes Visual LANSA

 

Detailed changes

   EPC838 includes these changes:    [Click here to Hide table...]

  CCS id.      Description
0120544
0135497
0137286
BLOB/CLOB temporary disk files now created under LPTH= instead of TPTH=

This defect has now been rectified
Note: This fix will not cleanup LOB temporary files created (by SuperServer or for exchanging LOBs to submitted job) before this patch was applied. If you wish to cleanup your temporary directory, and it is x_win95\x_lansa, ensure you back up any file you wish to delete, to avoid accidentally deleting required files.

0132911
0136420
Request for LANSA to support Visio 2007

The logical modeller now supports Visio 2007.

0135466 Keypressed event in a grid fires twice
0135710 Implement LANSA Database Triggers

LANSA validation rules and trigger functions can now be executed from outside of LANSA when LANSA DB Triggers are enabled for a file. Read and understand the section "LANSA Database Triggers" in the Visual LANSA Developer Guide before enabling LANSA DB Triggers for any file.

0137053 IDE crash when compiling SELECT_SQL with single quotes around a space
0137090 EXCHANGE list cleared during SuperServer startup in submitted job
0137115
0137337
Screen layout/buttons repositioned on windows discovered when using RAMP

The Layout Management was not invoked properly which is fixed now.

0137122 Field values in RDMLX webevent blank after calling RDML system variable function
0137140
0137323
DEFECT in FETCHing a CLOB/BLOB field after an SQLNULL value is encountered
0137154 Difference in VisualStyle behavior between Dropdown and Dropdownlist combo boxes

VisualStyles behave same for Dropdown and Dropdownlist combo box

0137189
0137217
System variable not being set correctly in SP5 

User Action: Recompile the effected object.

0137190 Spool file facility in web application works with WEB licence, not PWB licence

Spool file facility has now been enabled for non-development web systems

0137282 Using Process menu in V11SP5 causes LWEB_JOBs to loop

Procedural web functions may go into a loop. Defect fixed.

 

   EPC838 supercedes EPC837 which included these changes:    [Click here to Hide table...]

  CCS id.      Description
0135642 Unlevelled Tree Lists events fire in wrong order

Tree behaviour changed so that an Expand(True) on a Child node that results in Parent items also being expanded will Fire the Parent ItemExpanding events before the child Item expanding event (11.5 fired the child events before the parent events)

0136074 Obscure X_RUN command line so user ids and passwords cannot be seen

New XCMD command line parameter which when set to Y obscures all user ids and passwords on the command line so they cannot be seen using Process Explorer. See documentation for more details

0136309
0136849
0136869
XSL Editor crash when doing pastes or using backspace

 

0136356 Expanded property causing corruption of Listcount value
0136529 SELECT with *Compute does not work for RDMLX Key fields if they are blank
0136539
0136568
0136571
0136633
0136811
0136827
0137087
0137111
Defect in List and Grid column sequence

A change introduced in 11.3 to address an issue with SortPosition (number 135349) broke pre-existing behavior. An alternative change has fixed the SortPosition and also restored the pre-existing behavior.

0136558
0136941
SAVE_LIST built in crashes in V11 SP5 RDMLX on second invocation

BIFs SAVE_LIST, RESTORE_SAVED_LIST and DELETE_SAVED_LIST fail when invoked a second time when running in an RDMLX web function or WAM. 

0136567 HTML for table views occasionally generates two cells in same row

User Action: The affected HTML needs to be regenerated.

0136586
0137029
Grid CurrentItem.Entry causes an error if there are no entries in the grid

Version 10 behavior has been re-instated.

0136628 Generate XSL publishes language specific pages wrongly. 

User Action: Recompile the affected WAM without generating XSL.

0136654 Blank dates gets changed to 200000 in VL
0136667 Escape message not issued when file is not there from submit LANSA RUN on RDMLX

User Action: Recompile RDMLX functions that may be called from RDML on System i in batch processing where the batch processor is required to receive notification of fatal errors.
0136689 YMDX output stamping attribute on VL does not work on UPDATE, only INSERT
0136720
0137034
IDE stability

Deleting a file that contains logicals could crash the AutoComplete facility.

0136748 Deployment tool : Maintain a Host Route Table on a Network Client configuration

The setting for determining the location of a Host Route Table to be used as the basis for an application or package specific Host Route Table has been corrected to look at the Server when running a network client. Previously the local system directory was checked.

0136810 VL attempts to create temporary files in the root directory

Upgrade of JPEG support introduced a rule that limited memory use to one megabyte causing bigger JPEG files to be managed by a work file. This one megabyte limited has been increased to a gigabyte.

0136816 SAVE_LIST BIF second argument to be irrelevant for RDMLX code
0136877 Using tab in Windows forms, fields of type Time do not get focus

A one digit change to a date or time was accidentally cancelled the moment a date/time control loses focus.

0136887 Visual Style for Grid Cell is lost when UPD_ENTRY is used.
0136902 WAM would not rebuild correctly after upgrade to SP5 due to code structure

Using a list in a web-map that has the same name as a repository field could cause the mapping to fail.

0136932 Mixed Mode Commitment with SQL Server 2005 gets SQL Error 3981
0136948 Fatal error occurs when loading translations into the translation tool

When attempting to use the Deployment Tool's translation interface, the application crashed after selecting the languages to translate from and to then pressing the OK button.

0136954 Incorrect behavior of cross reference in DT after setting default options

If the Deployment Tool was configured to include default cross references, when an item was included in a package with no cross reference information selected this selection was being ignored and he default values were applied. 

0136981 RENAME command does not work correctly when using SuperServer

When the Server was not RDML iSeries, RENAME commands correctly would not work when were multiple I/O commands processed.

User Action: If you use SuperServer to RDMLX iSeries, Windows, or UNIX, rebuild any functions that contain RENAME commands.

0137038 When the list is displayed the values are either missing or corrupted

In Webevent RDMLX functions, columns following columns of integer types (length 2 and 4) will not display.

0137068 SELECT_SQL Oracle difference between 10.0 and 11.x

Embedded field with a value of blank was stripped to an empty string. When this was compared to a single blank it compared equal on all databases except Oracle. This was due to Oracle interpreting an empty field as a NULL and thus it fails to compare to anything. The fix was to ensure that on Oracle there is at least one blank.

0137102 When enabled "short char" data type not showing on webevent browse list

If you have enabled the RDMLX partition's "Short Char" option, strings that fall in this category didn't display in webevent browse lists. It would also cause columns following it to not display.

 

Affected objects

   Windows Components:    [Click here to Show table...]

 

   System i Components:    [Click here to Show table...]

Install Instructions

Instructions for installing on System i

These instructions have been abbreviated for experienced LANSA users. If you need further assistance to install the EPC, full instructions are available in the Technical Resources of the LANSA web site at www.lansa.com/support/notes/epc.

  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 C How to check for Active Users in the Installing LANSA on System 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 EPC838 to an IFS folder on the System i. ( e.g. /LANSA_pgmlib/tmp/epc838' ) 
  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 command LOADEPC with the following parameters:

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

  8. EPC number . . . . . . . . . . . > 838

    Install the EPC from . . . . . . > *IFS
    IFS Path and object name . . . . e.g. /LANSA_pgmlib/tmp/epc838

    Apply this EPC to . . . . . . . FULL_LANSA_SYSTEM
    LANSA program library . . . . . pgmlib

  9. Save and then delete the backout library (iiiEPCnn where iii = 1st three characters of the LANSA pgm library and nn is sequence number) created by the install. The contents of the library may be used to backout this EPC and return your system to its previous state.
  10. Sign off and then on again before commencing the next installation, e.g.:

Instructions for installing on Windows

  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 EPC838w.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

© 2009 LANSA