EPC - 790

Date : 24 October 2006

EPC790 Highlights

EPC790 delivers enhancements and corrections for Visual LANSA, LANSA for iSeries, LANSA for the Web, LANSA Client and the Visual LANSA Framework.

The significant benefits to be achieved by applying EPC790 are:

WAMs :
- It is now possible to generate the XSL for a single webroutine of a WAM. Use the right click menu to invoke the XSL generation. WAM developers should find this enhancement improves productivity.
- The stability and reliability in the XSL Editor has been improved.
- A new weblet (std_largelist) now supports very large lists (either XHTML or CSV). This weblet is recommended for report-like lists where there is no need to visualize columns with web widgets (controls) and the fields are output-only. You will need EPC792 applied to the Web Administrator and EPC791 applied to the LANSA for the Web IIS Plugin before you can use the std_largelist weblet.
- The performance for various types of deployed WAM applications, especially for complex WAMs, has been improved.
- The XSL editor Options dialogue now includes validation of entered values. Some users had mistakenly entered invalid values which caused unpredictable results during development (e.g. retrieving icons and images). The Options dialogue now makes its best attempt to connect to the nominated URL and ports at the time of update and when the XSL Editor is invoked.
- EPCs and other upgrades will now automatically invoke changed imports. All system wide imports will be done e.g. BIFs, commands, Technology Services. A new dialogue will be presented during this EPC install requesting that you nominate the Web enabled RDMLX partitions to receive the changed Weblets. This enhancement ensures that web partitions will never be using old versions of Weblets and Technology Services again.
- Internet Explorer V7.0 is now supported by the LANSA XSL editor.
- Various issues associated with the XSL Editor and with web and WAM execution have been addressed.
Visual LANSA :
- The performance of RDMLX applications has been improved, in some cases, substantially.
  Many Visual LANSA applications running on iSeries will perform significantly faster after applying EPC790. Although there will be benefits for RDMLX applications running on Windows, the improvements on this platform will not be as dramatic. The amount of improvement available to Visual LANSA applications will depend on the processing they perform. The major improvements are in the handling of packed and integer field types (which affects common operations like maths processing and comparisons). Therefore, applications that use such commands as Change, Assign, If, DoWhile, DoUntil, Loc_Entry, etc. should experience improvements especially where these commands are executed repeatedly (as in a loop situation).
- Importing times for medium to large imports has been reduced. For example, importing time for the Visual LANSA Framework should be reduced after applying EPC790. Deployment of LANSA developed applications will also benefit.
- Installation of changed system imports is now handled automatically. Removes the obligation from the user to complete this step to ensure all definitions are up-to-date.
- Various issues associated with deployed Visual LANSA applications and the Visual LANSA Framework have been addressed.
Server side support for LANSA Client V11.3 has been completed. EPC790 will be listed as the pre-requisite for LANSA Client V11.3 when it is released.

Product

Visual LANSA and LANSA for iSeries

Version

11.3

Pre-Requisite Details

EPC771 (CU3)

Instructions to install the EPC

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

Download EPC790.EXE file from the Web site or email.
Unzip (double click) EPC790.EXE. These files will be extracted:
- EPC790.htm - this document
- EPC790 - iSeries Save file
- EPC790w.exe - Windows install executable
- EPC790HF-061117 - Folder
- EC790P07 - Zip file
- EC790P09 - Zip file

Instructions provided for:

Yes	LANSA for iSeries
Yes	iSeries Web Server (multi-tier)
Yes	Visual LANSA
Yes	EPC790HF-061117 (Windows)
Yes	EC790P07 (iSeries) EC790P09 (iSeries)

Detailed changes

EPC790 includes these changes: [Click here to Show table...]

CCS id.	Description
113517	Option added to generate single webroutine XSL. Previously, a WAM developer had no choice other than to regenerate the XSL for all webroutines which was unnecessarily time consuming and possibly confusing.
120907	LANSA Import has been modified to reduce processing time. Importing large applications could take 1+ hours for Windows servers. The processing time has been reduced by up to a half, depending on the contents of the import. Further reductions in processing time can be achieved, these improvements will be delivered by the appropriate update method, eg. CU4.
124212	Executing a WAM with a reusable part on iSeries, for the second time, resulted in error: "MCH3601 - Pointer not set for location referenced". Shutdown of *APPLICATION variables has been corrected.
124878	EPC/upgrade to automatically import changed imports into a development environment. (See Highlights)
125791	Client/server Visual LANSA Framework application would generate an error attempting to find a language message file. Now corrected. Even though language specific user message files were defined in the partition multilingual attributes for LANSA for iSeries, the message file overrides were not being executed in the appropriate place when executing RDMLX applications. This resulted in the messages not being displayed in the correct language.
125965	LANSA Owner Profile no longer needs ALLOBJ to compile RDML file in RDMLX Partition. If RPGIV is in data area DC@OSVEROP, the LANSA Owner Profile previously required ALLOBJ OS/400 authority to compile an RDML file in an RDMLX partition. ALLOBJ is no longer needed in this situation.
125983	A SuperServer application no longer fails (with an Access Violation) when F1=Help is invoked.
125989	The XSL Editor now supports Internet Explorer versions 6 and 7. At the time this EPC was released Internet Explorer V7.0 was still on beta test. The XSL Editor has been run against this beta version, consequently several resulting issues have been addressed.
126235	A User Defined Built-In Function with 5 arguments would fail to execute if the 5th argument was a literal. Now corrected.
126323	A runtime error would be experienced when using an ActiveX control in a LANSA application executing on a Windows 2003 R2 server. Now corrected.
126469	Validation has been added to the XSL Editor when it opens and in its Options dialog. A test connection will be done when values are added/changed. A problem manifest as an inability to open any existing weblets/webroutines. This problem arose if the Base URL, as defined in the XSL Editor Options dialogue, was entered incorrectly. The XSL Editor will now check if the Base URL, Application Base URL and Web Service Base URL are valid when the XSL Editor starts. If not, the default value will be used. Base URL will default to the TEMP folder. Application Base URL will default to http://localhost/cgi-bin/lansaweb. Web Service Base URL will default to http://localhost/LANSAWebServices/ When changing the value in the Options dialog, the value will be tested and if not valid, a warning will be given. Again, the default values will be used, even if the entered setting is saved. When launching a WAM in a browser (either directly, via debug or via remote debug) the Application Base URL is tested. When creating or testing Web Services, the Web Service Base URL is tested. Note that throughout using the XSL Editor, the Base URL, Application Base URL and Web Service Base URL are tested before every use. This ensures that the XSL Editor will not be come unresponsive due to an invalid URL (due to timeout, webserver down, network down, etc). Once a URL is found to be invalid the default values will be used. If you experience a sudden loss of images, layout, etc, it is likely that this is the cause. Simply restart the IDE or update the settings by selecting OK in the Options dialog. This will reset the URLs to their entered values. Note that once a default value is used, the XSL Editor will continue to use the default value until the XSL Editor is restarted or the values changed in the Options dialog.
126493	Importing Other type objects would result in incorrect messages being issued to the import log, ie. they would refer to the wrong object type. Now corrected. Eg. Importing of a message file would generate the warning message: "EIM0306 system variable evaluation program <msgfilename> MSGF not imported". Successful import of these object types will now issue message EIM0076 "Object TESTMSGFS of type MSGF in library TSTLIB successfully imported."
126496	Default softkey license file location derived from lansa.exe rather than the current directory.
126513	Defective Behavior in Webevents with Input Capable Browse lists. In some circumstances message handling could hit an overflow condition.
126553	PERMFILOVR with a RDMLX function cannot identify M@PEROVR for French Program M@PEROVR now locatable when the permanent file override facility is used from an RDMLX function in certain languages, French being the original example. USER ACTION: Rebuild all OAMs for RDMLX files that are the subject of permanent file overrides on iSeries.
126594	After using an override on a field to change column heading, edit word is lost (grid)
126631	"Unable to Transform input XML" when running Visual LANSA Framework WAMs on Japanese. Corrected.
126728	Can DBCS RDML objects be compiled on English iSeries when the partition is RDMLX This issue arose because the client machine was a Japanese or Korean system but the server was not the same language. For a Japanese client, a different server language is now handled, however it is recommended that server be Japanese. For a Korean client, the server must be a Korean system, otherwise the Won character cannot be translated correctly.
126733	Special characters replacement stops after the first ampersand. Special characters in field values are usually replaced so that they won't break surrounding html. But the replacement logic incorrectly stops after replaced the first ampersand.
126735	String intrinsic method UPPERCASE does not work the same on iSeries. Corrected.
126787	Where tabstyle = flatbuttons in CU3 the tabsheets are not visible Issue fixed for Tab control where Tabstyle(flatbuttons) would not paint correctly
126811	USE command build error would cause an abend in the Deployment Tool when installing the Visual LANSA Demo.
126832	Deployment Tool crashes when adding non-LANSA files to package Large volume of selected files are now correctly handled when FileOpen and SaveAs Common Dialogs are used. The Explorer style MUST be enabled.
126849	OTHER file definitions containing dates in CYYMMDD format cannot be edited in Visual LANSA, fatal error message issued. Message removed as Visual LANSA support of CYYMMDD confirmed.
126850	Initialize event does not fire. Customer's application was used to determine specific situation where Initialization logic was being run but the event was not being signaled. The event was not being signaled because Visual LANSA was recovering from a "dead" state when the Initialize logic was running. This was incorrect, so the Initialization logic is now blocked and runs after the "dead" state recovery is complete.
126873	Impose a shorter timeout for downloading icons/images from Web server. To improve performance, the XSL Editor now caches which images are not available on the web server. so as to avoid attempting to get them more than once.
126881	Class property can have BOLD value? All Cascading Stylesheet class names are shown in Details tab.
126892	A LANSA Client JOIN Query on an OTHER File would fail during execution. Corrected.
126937	WAM runtime memory leak Small amount of used memory is not reclaimed after each web routine execution if list is either mapped in or out. It is now fixed.
126957	XSLEditor was leaking GDI Objects. Some GDI leaks in the XSL Editor have been addressed. The one addressed applies to loading webroutines with many weblets, fields and lists (The Outline view was leaking). There are still some GDI objects leaked in the XSL Editor and it is therefore suggested that the VL IDE is restarted periodically throughout the day.
127026	Dates displayed in a Listview/Grid ignore the DateFormat property FieldVisualization has been enhanced to allow custom DateFormats to be displayed in LANSA List components ( Grid, ListView, Tree etc..). eg. A Date Field in a Grid will now use the DateFormat and CustomDateFormat properties of its DefaultVisual(true) PRIM_EVDT to initialize its display.
127056	Form is disabled in Version 11.0 but not in Version 10.0. Issue resolved where disabling a List Control (Grid, ListView, Tree, ListBox) from an ItemGotFocus or ItemGotSelection event caused the parent form to be unresponsive to mouse clicks until the form was deactivated and reactivated.
127082	Load OTHER File dialog failed to connect for non-ML partitions
127122	IDE Crash when compiling function Full RDMLX field types are now fully supported by the WHERE parameter of the SELECTLIST and LOC_ENTRY commands.
127171	Random crashes when dynamic components are closed. KEEP_LAST processing has been fixed to support Full RDMLX expression in the WITH_KEY parameter. Only Visual LANSA runtime changed, no rebuild required.
127180	RDML Exchange causes data corruption Truncation of 64-bit Integers on iSeries has been corrected.
127187	If the LCXP9000 user exit program was relied upon to add the LANSA program library to the list, LANSA Open and SuperServer startup would fail with "Cannot resolve to object X_PDF". Now corrected.
127206	XSL Editor: Removing list causes layout to "disappear" from designer Windows environmental changes, for example, applying Microsoft's IE6 security patch 916281 can cause the styles, which are imported using an @import directive, to become unavailable in the XSL Editor's Design view. LANSA has implemented a change to avoid the impacts of such environmental changes. To avail of the fix, you are required to apply the LANSA for the Web IIS Plug-in shipped in EPC791 in conjunction with the std_style.xsl installed with EPC790 or later to the Visual LANSA environment. This feature has limitations which are specified in the LANSA Web Administrator Help. Note: this solution will not work if the XSL Editor is using an iSeries web server for the Design mode.
127283	Width of message box different from version 10 to 11
127313	Input box no longer disappears when a weblet is dropped on an input box for a field on a panel.
127594	Integer Array caused a Crash when Array index value 0 is outside maximum allowable range 1 to 9999 for an array
127597	"Data XML" data was incorrectly modified before saving the web routine An undo operation can fail due to the Data XML being modified when validating a document before Save. The "Data XML" is no longer modified when validating a document before Save.

EPC790 supersedes EPC784, EPC783, EPC781, EPC780 and EPC769: [Click here to Show table...]

CCS id.	Description
EPC784
125424	iSeries: Cannot open LOB disk file for writing error on FETCH or SELECT of LOB If FETCH or SELECT was used to retrieve the same row twice during the same LANSA session, and a BLOB or CLOB field is in the fields list, and the field contains data, this error would occur.
125573	Emails sent using the EMAIL BIF displays the BCC recipients Emails now no longer display BCC recipients to TO or CC recipients
125615	Incorrect calculation of percentage in Visual LANSA application
125617	Communications Administrator for application on Network Client fails to open
125702	Visual LANSA Editor crashes when using a date field with MinDate property in a reusable part.
125736	iSeries: Web Component corrupts DC@F74 after checkout Check out of a web component now creates or updates the correct task tracking record
125737	If OpenSession cannot find requested file, termination of server job abends
125892	SQL Syntax error in SQL Server when updating file with LOB field UPDATE commands that affected BLOB and CLOB fields would not work if the database was using emulated collections (some SQL Server installations). USER ACTION: Recompile the OAM for any affected file.
125911	iSeries: Repository field level help text not retrieved (LANSA Client and Open)
125940	Unable to start Host Monitor after applying 765 to a TCHI system Running certain DBCS slave->server configurations may cause Host Monitor and SuperServer applications to fail. This may occur when a client system's code page is incompatible with the server's CCSID. For example, a Traditional Chinese slave system may get the problem if connecting to an English server.
126101	Weblets have incorrect authorities for some users on Checkin.
126112	EPC does not install correctly when LANSA jobs still running. host monitor not available.
126141	Chinese characters appearing as invalid characters in Design view of XSL editor The XSL Editor now shows Chinese characters in the Design View when running on Chinese Windows, regardless of the Development Language chosen.
126180	Grid weblet - data in cells being cut off at 30 chars USER ACTION: Windows - reinitialize the web partition. iSeries - reimport weblets to web partition.
126185	RDML OTHER file, RDMLX partition, iSeries, RDML trigger corrupts virtual fields Where an RDML OTHER file is used in an RDMLX partition on iSeries with an RDML trigger function, any virtual fields may be corrupted if the file is used from a WAM or other RDMLX object, including SuperServer via DEFINE_ANY_SERVER. User Action: Recompile the OAM for any affected file.
126186	Modified list for webroutine cannot be select for insertion thru XSL editor The three delete items in the HTML Editor's context menu, aka Edit menu, are now grouped together. The Delete Entire List menu item also shows the name of the list. If the current HTML element is the list (XSL:template for the list in the Outline tab or Ancestor view) then only Delete Entire List is available. If the current HTML element is the list (XSL:apply-templates for the list in the Outline tab or Ancestor view) then no delete is enabled at all.
126206	LceLansaCall does not always retrieve exchanged field values back to client LceLansaCall() would only return field values to the client if they were originally specified as part of the strExchangeList parameter.
126239	Imports contain incorrect DBCS setting for TCHI in F60 table Importing the standard weblets (std_weblets) incorrectly changed language TCHI definition. USER ACTION: Windows - reinitialize the web partition. iSeries - reimport weblets to web partition.
126241	BLOB and CLOB data loss on write or read iSeries: CLOB data lost on insert/update, but OK as I/O result. Read okay. Windows: Oracle: Insert of BLOB or CLOB caused abend. On all databases, read of CLOB data lost approx every 8K.
126257	In ModelB form posting blank field values directly to the lansaweb url displays Fixed the problem which only affect Model B configuration on iSeries and using modified URL for posting the form.
126277	More than 30 seconds response will time out
126295	SELECTLIST/LOC_ENTRY with WHERE on RDMLX fields runs slowly Performance issue located and corrected. RDML and Full RDMLX fields are now comparable.
126298	Trailing spaces being returned from RDML Functions running in an RDMLX Partition Where a CALL_SERVER_FUNCTION to an RDML function is executed via RDMLX iSeries Server, trailing blanks were being returned for Alpha fields put on the exchange list by the RDML function, causing cosmetic issues in the UI of a form. Wherever an RDML function is called from the RDMLX environment, Alpha fields put in the exchange list by the RDML function, going back to the RDMLX environment will no longer contain trailing blanks.
126307	JSM requires working list max entry count The maximum size of a working list is now passed on to the JSM Server.
126311	Error when using the assistant with CALL_SERVER_FUNCTION. The Built in function definition for CALL_SERVER_FUNCTION for argument 3 in LANSA for iSeries now has the correct default value of 'N'. User Action: Run System Initialization specifying Standard Built In Function Definitions
126324	LceOpenSession() should fail for LANSA Open 10 applications passing RDMLX object.
126332	Fields used as visual components are not exchanged to JSM service Fields used as visual components are now exchanged to JSM service when using SERVICE_EXCHANGE(*FIELD)
126441	Where a file had code file checks to a file that has the special character @, #, or $ in the OAM name, the OAM is not found and the application fails. This issue has been addressed. User Action: Rebuild OAMs for LANSA files on iSeries if a) partition is RDMLX enabled and b) this file has code file checks to a physical file with the special characters @, #, or $ in its name, OR to a logical file belonging to a physical file with the special characters in its name.
EPC783
125888	Special handling for large lists (weblet). New weblet (std_largelist) to support very large lists (either XHTML or CSV). This weblet is recommended for report-like lists where there is no need to visualize columns with web widgets (controls) and the fields are output-only.
125889	Special handling for large lists (runtime). Runtime changes to support new weblet std_largelist. See CCS 125888.
125970	Improve WAM runtime memory usage. Memory allocation has been improved. This is more noticeable when processing large lists.
126196	WAM cannot display working list entries of number > 32767
EPC781
126277	Allow custom timeout when the request is from LANSAServiceConsumer.
126357	Use internal job number to check status of Web Transaction Monitor Job.
126954	LANSAServiceConsumer.dll failed to load XML data from a LANSA Application Server. LANSAServiceConsumer.dll uses the COM interface IServerXMLHTTPRequest for the HTTP requests which load XML data from a LANSA Application Server. Under certain, as yet undetermined, circumstances, the COM interface can fail on Windows Server 2003 and some Windows Server 2000 installations. To workaround the problem, neon (see http://www.webdav.org/neon/) is used to do the HTTP requests instead. As neon is licensed under the GNU Library General Public License, end users must be provided with source code used to build the binary (libneon.dll). Source code and related notes for neon are available on the LANSA Install CD (directory "\3rdparty\neon"). See Settings.ini for instructions about how to select which HTTP request method to use. The updated LANSAServiceConsumer.dll is also enhanced with new logging capability. Also see Settings.ini for more information.
EPC780
126140	LANSA for the Web RDML webevent applications may perform slower after applying V11.3 (CU3). This performance degradation has now been corrected.
EPC769
123764 125685	Allow embedded I/O to same file inside of SELECT / UPDATE / DELETE Where a file is used in a SELECT loop and anywhere within the SELECT loop, in a subroutine called or another function called etc while in the SELECT loop if anything other than a DELETE without key or UPDATE without key is executed for the same file then the SELECT loop may finish before all records are read. User Action: Rebuild OAMs for LANSA files on iSeries if the partition is RDMLX enabled and this file is used in this manner

Affected objects

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

Object Name	Folder
lansa.exe	\lansa
lansaautoimport.exe	\lansa
liimeng.msg	\lansa
liimfra.msg	\lansa
liimjpn.msg	\lansa
liio.dll	\lansa
liiosrv.dll	\lansa
liis.dll	\lansa
liiv.dll	\lansa
liiy.dll	\lansa
lpcr.bnd	\lansa
lpcrfra.bnd	\lansa
lpcrjpn.bnd	\lansa
lppa.bnd	\lansa
lppafra.bnd	\lansa
lppajpn.bnd	\lansa
x_base.dll	\lansa
x_prim.dll	\lansa
XSLEditorFrame.dll	\lansa
XSLEditorFrameFRA.dll	\lansa
XSLEditorFrameJPN.dll	\lansa
lxxf03.asc	\lansa\imports\def_clt
lxxf14.asc	\lansa\imports\def_clt
lxxf48.asc	\lansa\imports\std_bifs
lxxf48.asc	\lansa\imports\std_bifs\fra
lxxf48.asc	\lansa\imports\std_bifs\fra\500
lxxf48.asc	\lansa\imports\std_bifs\jpn
lxxf02.asc	\lansa\imports\std_weblets
lxxf60.asc	\lansa\imports\std_weblets
lxxf74.asc	\lansa\imports\std_weblets
lxxfcr.asc	\lansa\imports\std_weblets
lxxfwe.asc	\lansa\imports\std_weblets
lxxfwl.asc	\lansa\imports\std_weblets
lxxfws.asc	\lansa\imports\std_weblets
lxxfwx.asc	\lansa\imports\std_weblets
lxxf60.asc	\lansa\imports\TechServices
Interop.LANSAServiceConsumerLib.dll	\lansa\XSLEditor
LANSAServiceConsumer.dll	\lansa\XSLEditor
libneon.dll	\lansa\XSLEditor
PreviewBrowser.dll	\lansa\XSLEditor
PreviewBrowserFRA.dll	\lansa\XSLEditor
PreviewBrowserJPN.dll	\lansa\XSLEditor
settings.ini	\lansa\XSLEditor
XSLEditor.dll	\lansa\XSLEditor
XSLEditorFRA.dll	\lansa\XSLEditor
XSLEditorJPN.dll	\lansa\XSLEditor
XSLHTMLEditor.dll	\lansa\XSLEditor
XSLHTMLEditorFRA.dll	\lansa\XSLEditor
XSLHTMLEditorJPN.dll	\lansa\XSLEditor
XSLTextEditor.dll	\lansa\XSLEditor
XSLTextEditorFRA.dll	\lansa\XSLEditor
XSLTextEditorJPN.dll	\lansa\XSLEditor
x_txteng.dat	\X_WIN95\X_LANSA
x_txtfra.dat	\X_WIN95\X_LANSA
x_txtjpn.dat	\X_WIN95\X_LANSA
dc_f03.dll	\X_WIN95\X_LANSA\EXECUTE
lesystem.dll	\X_WIN95\X_LANSA\EXECUTE
lp_systm.dll	\X_WIN95\X_LANSA\EXECUTE
lppa.bnd	\X_WIN95\X_LANSA\EXECUTE
lppafra.bnd	\X_WIN95\X_LANSA\EXECUTE
lppajpn.bnd	\X_WIN95\X_LANSA\EXECUTE
lxptbbld.exe	\X_WIN95\X_LANSA\EXECUTE
lxutil.dll	\X_WIN95\X_LANSA\EXECUTE
w3_p1200.exe	\X_WIN95\X_LANSA\EXECUTE
w3_p1600.dll	\X_WIN95\X_LANSA\EXECUTE
w3@p1600.dll	\X_WIN95\X_LANSA\EXECUTE
w3_p2000.exe	\X_WIN95\X_LANSA\EXECUTE
w3wprfun.dll	\X_WIN95\X_LANSA\EXECUTE
w3wsvpgm.dll	\X_WIN95\X_LANSA\EXECUTE
w3wsvpgx.dll	\X_WIN95\X_LANSA\EXECUTE
x_base.dll	\X_WIN95\X_LANSA\EXECUTE
x_bifms.dll	\X_WIN95\X_LANSA\EXECUTE
x_comms.dll	\X_WIN95\X_LANSA\EXECUTE
x_comp.dll	\X_WIN95\X_LANSA\EXECUTE
x_dbmms.dll	\X_WIN95\X_LANSA\EXECUTE
x_dll.dll	\X_WIN95\X_LANSA\EXECUTE
x_funms.dll	\X_WIN95\X_LANSA\EXECUTE
x_jsm.dll	\X_WIN95\X_LANSA\EXECUTE
x_lsv.dll	\X_WIN95\X_LANSA\EXECUTE
x_pdfms.dll	\X_WIN95\X_LANSA\EXECUTE
x_prim.dll	\X_WIN95\X_LANSA\EXECUTE
x_run.exe	\X_WIN95\X_LANSA\EXECUTE
x_ssv.dll	\X_WIN95\X_LANSA\EXECUTE
x_xqlms.dll	\X_WIN95\X_LANSA\EXECUTE
x_var.dll	\X_WIN95\X_LANSA\EXECUTE
lansa037.chm	\X_WIN95\X_LANSA\EXECUTE\ENG
lansa038.chm	\X_WIN95\X_LANSA\EXECUTE\ENG
lansa039.chm	\X_WIN95\X_LANSA\EXECUTE\ENG
lansa040.chm	\X_WIN95\X_LANSA\EXECUTE\ENG
lansa048.chm	\X_WIN95\X_LANSA\EXECUTE\ENG
lansa049.chm	\X_WIN95\X_LANSA\EXECUTE\ENG
lansa087.chm	\X_WIN95\X_LANSA\EXECUTE\ENG
lansa093.chm	\X_WIN95\X_LANSA\EXECUTE\ENG
tutoriallist.chm	\X_WIN95\X_LANSA\EXECUTE\ENG
iom00001.s	\X_WIN95\X_LANSA\SOURCE
liiodef.h	\X_WIN95\X_LANSA\SOURCE
x_funstr.h	\X_WIN95\X_LANSA\SOURCE
x_glodef.h	\X_WIN95\X_LANSA\SOURCE
x_oidstr.h	\X_WIN95\X_LANSA\SOURCE
x_varpro.h	\X_WIN95\X_LANSA\SOURCE
x_varstr.h	\X_WIN95\X_LANSA\SOURCE

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

Object Name	Folder
weblets.savf	LANSA *pgmlib*
dcxs870x.srvpgm	LANSA pgmlib
dcxs872x.srvpgm	LANSA pgmlib
w3profun.pgm	LANSA pgmlib
x_base.srvpgm	LANSA *pgmlib*
x_bif.srvpgm	LANSA pgmlib
x_com.srvpgm	LANSA pgmlib
x_comp.srvpgm	LANSA pgmlib
x_dbg.srvpgm	LANSA pgmlib
x_dbm.srvpgm	LANSA pgmlib
x_dbm_is.svpgm	LANSA pgmlib
x_dll.srvpgm	LANSA pgmlib
x_fun.srvpgm	LANSA pgmlib
x_jsm.srvpgm	LANSA pgmlib
x_lsv.srvpgm	LANSA pgmlib
x_pdf.srvpgm	LANSA pgmlib
x_prim.srvpgm	LANSA pgmlib
x_ssv.srvpgm	LANSA pgmlib
x_var.srvpgm	LANSA pgmlib
x_xql>srvpgm	LANSA pgmlib
dc@p2120.pgm	LANSA pgmlib
dc@p6207.pgm	LANSA pgmlib
dc@p6301.pgm	LANSA pgmlib
dc@p8027.pgm	LANSA pgmlib
lxip0010.pgm	LANSA pgmlib
lxxp0100.pgm	LANSA pgmlib
W3@p1200.pgm	LANSA *pgmlib*
w3@p1400.pgm	LANSA *pgmlib*
w3p@2000.pgm	LANSA pgmlib
x_run.pgm	LANSA pgmlib
lcxp0010.pgm	LANSA comlib
w3@p1600.pgm	LANSA *comlib*
lxqueue.srvpgm	LANSA comlib
lxutil.srvpgm	LANSA comlib
w3s1000.srvpgm	LANSA comlib
w3xsvpgm.srvpgm	LANSA *comlib and Web server*
w3xsvpgv.srvpgm	LANSA *comlib and Web server*
w3xsvpgx.srvpgm	LANSA *comlib and Web server*
w3xsvpgy.srvpgm	LANSA *comlib and Web server*
W3@p1100.pgm	LANSA *comlib and Web server*
lweb.dta	LANSA *comlib and Web server*
epc784img.savf	Web server (Installs new images and script files. Updates standard script and CSS files)
epc784opn.savf	Web Server Pase objects
lppa.bnd	./x_lansa/
lppafra.bnd	../x_lansa/
lppajpn.bnd	./x_lansa/
x_txteng.dat	./x_lansa/
x_txtfra.dat	./x_lansa/
x_txtjpn.dat	./x_lansa/
liiodef.h	./x_lansa/source/
x_funstr.h	./x_lansa/source/
x_glodef.h	./x_lansa/source/
x_oidstr.h	./x_lansa/source/
x_varpro.h	./x_lansa/source/
x_varstr.h	./x_lansa/source/

Install Instructions

Instructions for installing on iSeries

These instructions have been abridged for experienced LANSA users. IIf 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
Recommend a backup be done of all the LANSA folders, system libraries and ALL the LANSA IFS objects (LANSA_pgmlib/x_lansa) before applying this EPC
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 iSeries guide for instructions.
End the Listener, Host Monitor and web server for the LANSA system and run the LANSA for the Web cleanup program.
Move the unzipped file EPC790 to a shared folders (QDLS) on the iSeries.
Use the XFLRTOSAVF command to convert the folder to a save file (LANSA program library must be on your library list) - press F4 for command details. A save file will be created by this command.
You now have a save file.
Sign on as a user profile that is QSECOFR, part of the QSECOFR group, or, has *ALLOBJ and *SECADM special authorities.
Use the RSTOBJ command to restore all objects from library QTEMP into library QTEMP, eg.
RSTOBJ OBJ(*ALL) SAVLIB(QTEMP) DEV(*SAVF) SAVF(<save file name>) RSTLIB(QTEMP)
Display your current library list. If QTEMP is not shown, add it to your library list by using the ADDLIBLE (add library list entry) command.
Install the EPC using the command:

LOADEPC790 PGMLIB(<pgmlib>) COMLIB(<comlib>)
<pgmlib> is the name of the LANSA program library, often DC@PGMLIB but it may be different on your system.
<comlib> is the name of the LANSA Communications library, often DC@COMLIB but it may different on your system.
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.
Sign off and then on again before commencing the next installation, eg:
- to apply this EPC on another LANSA system
- to apply another EPC on the same LANSA system
Import the standard weblets into your RDMLX partitions from the save file found in the LANSA program library.

Special Instructions for users of iSeries web server (multi-tier)

To apply EPC790 on the Web Server tier of your LANSA for the Web system, follow these steps:

End the web server and run the LANSA for the Web cleanup program. Refer to 13.5.6 Clean Up Systems in the LANSA Online documentation for cleanup instructions.
If you haven't installed or upgraded LANSA for the Web on the Web Server, do so before proceeding with step 2.
Restore the EPC objects into QTEMP (Perform the same steps you used to restore the objects in your LANSA for the Web application/data server system).
Display your current library list. If QTEMP is not shown, then add it to your library list using the ADDLIBLE (add library list entry) command.
Install the EPC for the Web Server by using the command:

LOADE790MT ADMLIB(<adminlib>) COMLIB(<comlib>)
where <admin> is the name of the LANSA for Web Administration library.
where <comlib> is the name of the LANSA Com/Share library. This is often DC@COMLIB but it may different on your system
Press enter to continue processing.
Save, and then delete, the backout library (iiiEPCMBnn where iii = 1st three characters of the LANSA pgm library and nn is sequence number) created by the install. The contents of this library may be used to backout this EPC and return your system to its previous state.
Sign off and sign on again if you want to run the configuration program.

Instructions for installing on Windows

Recommend that a backup be done of all LANSA folders and your LANSA database before applying this EPC.
Stop using the LANSA development environment and stop all currently executing LANSA applications.
Double-click on EPC790w.exe.
Select the "Setup" button or "Cancel" if you do not want to proceed.
If you have multiple configurations installed, Select the configuration to which the EPC is to be applied.
From EPC790 you will be asked to nominate the web partitions into which the updated set of weblets are to be imported.
If you are prompted to reboot your pc - please reboot.
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

Instructions for installing EPC790HF-061117 to Visual LANSA

Copy the extracted EPC790HF-061117 directory structure into the LANSA V11.0 root directory eg. C:\Program Files\LANSA

In the EPC790HF-061117 directory there is a file called hotfix.cmd. Run this command file (double click on it).

This will perform the following actions

Create a BACKUP folder under the \LANSA and \EXECUTE folders.
Copy the files to be replaced to these folders and rename them to *.bak
Copy the delivered files to the appropriate locations.

Step 3 can potentially fail for any of the following reasons

The hotfix is being applied to a non- V11.0 LANSA environment
The files it is attempting to backout and replace are in use
The LANSA development environment is in use
The LANSA web server is in use

If the copy fails, you should review the messages in the DOS prompt and correct the issue eg. if a file is in use because the IDE is open, you should close the IDE and re-run the hotfix.cmd.

If any unexpected issues arise after applying the hotfix, use the backout library to restore the original files and report the problem to your local LANSA Support group.

Instructions for installing EC790P07 and EC790P09 to LANSA for iSeries

EC790P07 and EC790P09 include software to be installed on an iSeries system. These instructions describe the installation and use of all delivered items.

Unzip (double click) the EC790P07.ZIP. These files will be extracted EC790P07.htm and EC790P07 - iSeries Save file. Follow the instructions in EC790P07.htm to apply the patch.
Unzip (double click) the EC790P09.ZIP. These files will be extracted EC790P09.htm and EC790P09 - iSeries Save file. Follow the instructions in EC790P09.htm to apply the patch.

EPC Information

Note: A password is required to download EPCs. Request a password

Customers in Asia Pacific and EMEA can download EPCs from this site. Customers in the Americas can download EPCs at the Americas Region Support Portal.

EPC - 790

EPC790 Highlights

Instructions to install the EPC

Instructions provided for:

Detailed changes

Affected objects

Install Instructions

Instructions for installing on iSeries

Special Instructions for users of iSeries web server (multi-tier)

Instructions for installing on Windows

Instructions for installing EPC790HF-061117 to Visual LANSA

Instructions for installing EC790P07 and EC790P09 to LANSA for iSeries

EPC Information

Version Info

Documentation

EPCs

Issues

Tips

Exchange

Help Desk

Newsletter