LANSA Open Tips
| Date | Version | Tip | |
|---|---|---|---|
| Mar 21, 2014 | All | A LANSA Open for .NET license error can be generated if all installation steps are not completed When setting up LANSA Open for .NET there is an import for each platform that must be completed to avoid execution issues |
|
| Mar 27, 2008 | Listener fails with error MCH6801 - Object domain or storage protection error When trying to start the LANSA Listener, the Listener fails and error message MCH6801 - Object domain or storage protection error for offset &5 in object &1 appears in the job log |
||
| Nov 02, 2004 | All | LANSA Listener fails with references to LCOTPJOBS in joblog When trying to start the LANSA Listener, the Listener fails, and in the job log there are references to object "LCOTPJOBS" |
|
| Dec 08, 1997 | LANSA Open Application Examples Visual Basic and C application examples that are shipped with LANSA Open Release 3.0. |
||
| Archived | Can the host names defined by the DNS Server be used in the Fully Qualified Name of the Host? If a user has defined host names in the Windows NT Server DNS Server, it is possible to use the host names defined by the DNS Server in the Fully Qualified Name of the Host |
||
| Archived | Sample Delphi Applications A sample Delphi application that uses LANSA/Server over the demonstration personnel system |
||
| Archived | Configuring the Listener Job To prepare the AS/400 for TCP/IP and LANSA's Workstation Products, a Listener job must be started |
||
| Archived | The effect of using triggers to evaluate virtual fields A SELECT with a WHERE condition is evaluated slightly differently on LANSA for iSeries and LANSA Open (and LANSA Client) |
||
| Archived | Connecting in SuperServer mode to a Windows server Some things to look at before trying to establish a SuperServer connection from either a LANSA for Windows application or a LANSA Open one to an NT Server box |
||
| Archived | Improving connection times in LANSA Open Factors that have an influence in the time it takes in opening a LANSA Open session |
||
| Archived | LANSA Open and TCP/IP: Troubleshooting communications Some additional steps need to be taken in order to determine a communications problem when running LANSA Open over TCP/IP instead of using other communications methods |
||
| Archived | All | Handling NULL terminated strings in Visual Basic when using LANSA Open When using DLLs with Visual Basic you need to take special care of strings because Visual Basic cannot handle strings terminated by a NULL character and all DLLs terminate strings this way |
|
| Archived | Getting information out of an AS/400 data area from Visual Basic You can get information out of an AS/400 data area very easily from Visual Basic using LANSA/Server |
||
| Archived | LANSA/Server Usage Tips Tips about LANSA/Server functions that allow you to "execute" programs on the AS/400 |
||
| Archived | Customizing environments for LANSA/Server Tips about LANSA/Server functions that allow you to "execute" programs on the AS/400 |
||
| Archived | Dealing with LANSA/Server communications problems Diagnosing and resolving the most common problems encountered during the LANSA/Server CONNECT phase |