Appendix A. LANSA for Web Platform Differences
Some of the features you are familiar with if you are using LANSA for the Web on IBM i may not be available when you are using LANSA for the Web on a Windows platform.
The following list includes the specific platform differences as well as answers to some of the common questions about development with LANSA for the Web.
Item |
IBM i | Windows |
Locking of DLLs |
N/A |
When developing and testing RDML functions at the same time, the RDML compilation may fail because the LWEB_JOB (W3_P1200) has the related DLL in use. To allow concurrent development and execution of Web applications, set Maximum reuse to 1 (in the Administrator, menu Tools, sub-menu Configure System, Tab Transaction monitor). With set to 1, the LWEB_JOB will be terminated. This unloads any DLLs in use. |
Web Skeletons |
Default skeleton is member WEBSKEL in file DC@F28 in the LANSA data library. Overrides are members in file DC@W22. |
Default skeleton is webskel.s in the LANSA source directory.
Overrides are named <filename>.s in the LANSA partition source directory. |
EMAIL BIFs |
Supported |
These BIFs cannot be used in functions that are invoked on remote Windows server systems so therefore cannot be used in Web applications. |
WEB_STATIC_ PAGE Built-In Function |
Yes |
Yes, with these restrictions:
|
Data Area |
Data Area DC@LWEB |
Values are stored in registry with this key: |
Spool File Access |
Supported |
Not supported |
Location of DC@W08 |
In a database. |
In DC_W08.DAT file in the Visual LANSA Execute directory. |
Implementation of: |
In a database. |
In a 'memory-file'. There are no related tables in the database. |
Model A (Single Tier) - |
Yes |
No, only multi-tier supported. |
Multi panel displays |
Yes |
If the screen format is larger than one page it can be displayed in a Web browser window but NOT in a PC window. |
Field spanning lines |
|
Not supported. |
LANSA for the Web Programs |
All used on IBM i |
|
Exchange List |
OS400 users can specify (in the web administrator) whether to use regular exchange (2K byte limit) or the extended exchange. |
LANSA for the Web on Windows does not differentiate between types of Exchange list. The memory available is the only limit to the size of the Exchange Lists on Windows |
Printing |
Supported |
Supported with these restrictions:
|
File Components |
Uses IBM i physical files |
Uses simple text file |
Library Lists |
Supported |
No such concept on Windows |
Highlighting of fields with errors |
No plans at this stage for HTML. |
No plans at this stage for HTML. |
Cursor positioning |
No plans at this stage. |
No plans at this stage. |
LANSA processes with an Action Bar style |
No |
No. |
Process and function level help |
No |
No. |
Field conditioning (e.g. IOCOND) |
No. |
No. |
LANSA Repository based GUI constructs (except drop downs) |
No |
No |
Column headings on flat panel will appear to the left of the field on the same line. |
No change planned. |
No change planned. |
Browse lists do not fold if the length is greater than 80 characters. |
No change planned. |
No change planned. |
When recompiling a function, does LANSA for the Web check to see if I have made any manual changes to the HTML or XML.
|
As for Windows. |
No.
You can compare two versions of a page Using the LANSA Editor - provided backup was enabled and the original version of the page was saved. |
Fields with values of Hex '00' (*LOVAL) or Hex 'FF' (*HIVAL) cannot be sent to the browser. |
As for Windows. |
Hex '00' and Hex 'FF' are conventionally used for string delimiting and end markers. This is also the case with LANSA for the Web. Consequently, if these values are used they will be misinterpreted and result in unpredictable results if sent to the browser. |
3GL programs with screen displays. |
No |
No |
Browse commands |
No |
No |
Message types *STATUS, *WINDOW and *WINDOWBUZ |
No |
No |