LANSA Open and TCP/IP: Troubleshooting communications
|Product/Release:||LANSA Open - All Versions|
|Abstract:||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.|
|Submitted By:||LANSA Technical Support|
In general, LANSA Open (formally LANSA/Server) running over TCP/IP will have the same communications problems as when running using CPI-C or Enhanced APPC.
While the AS/400 generated joblog (whenever available) remains the main source of information, there are configuration issues that are LANSA Open and TCP/IP specific. Perform the following checks before starting the usual check for job descriptions, library lists, user profile authorities, etc.
When a communications problem (lce0023) occurs when running TCP/IP do the following :
- Use PING to check TCP/IP configuration. This is equivalent to "can you get a 5250 emulation session" when using other communications methods. PING will test the TCP/IP configuration and connection between the workstation and the host.
It is also possible to PING an IP address (e.g. PING 22.214.171.124) or the Host system name (e.g. PING MYAS400). The first option, if successful, will prove that TCP/IP is configured and a route exists between the workstation and the host. The second option will additionally prove that the name resolution (either DNS or Hosts file) is also working.
PING does not prove, though, that a connection to a particular port id (application) would be successful.
- Verify that the LISTENER job is running on the AS/400. Use the AS/400 WRKACTJOB command to do this.
- Check that the LISTENER is listening to the correct port. The port is indicated as the Connection ID in the Work with Listener Records on the AS/400 and the LANSA Open Communications extensions on the PC.
If these steps complete correctly it is almost certain that TCP/IP and LANSA Open have been correctly configured in both the PC and the AS/400 and that they are running.
The next steps involve standard checking. Refer to the LANSA Open troubleshooting guide (PDF 27K) (also at the back of the LANSA Open Guide.)
When communicating over TCP/IP the returned code shown by LANSA Open does not reveal as much as it does when running Enhanced APPC or CPI-C. A new feature, the tracing facility, has been added to LANSA Open. Using this facility allows the TCP/IP native error to be determined. So, the next step should be turning on the tracing options at the LANSA Open communications administrator level.
The trace can occur at a number of levels, initially only turn Error tracing on. This is done in the LANSA Open Communications Administrator. See the LANSA Communications Extensions section in the LANSA Open guide for details.
The following is an example of an error:
A LANSA Open application may be returning the following error:
Lce0023 - A Communications Error has occurred for the action 'Allocate'.
The return code is 0x06.
In reviewing the trace file, the following line is found:
Native Error:10061 CPIC Error:20 in connect
The above native error's description will be found in the LANSA Open guide. The descriptions are very cryptic, in this case: WSAECONNREFUSED.
This means that connection to the AS/400 was refused. This most likely means that the listener is not running. This would have been detected previously in point 2.
The possibility exists that a native error is not being reported. In this case, other tracing options should be considered, i.e.: External IPC calls, Calls to CPIC and Internal IPC calls. This information should be the sent to LANSA Technical Support.
Other related issues:
- Joblogs will be generated for the User ID used to start the listener job. The actual User profile who is executing the application will appear inside the joblog. Bear this in mind when looking for the right joblog.
- Make sure that LCOMGR16.DLL/ LCOMGR32.DLL is specified as the Communication's DLL and APPC as the Communication's type in either the LANSA.INI or configuration utility in order to run TCP/IP.
- In the LANSA Open Administrator you must specify Socket as the Communication Type for the system entry that will connect through TPC/IP.