7.1 What to Do if You Have Communications Problems

Communication problems can be caused by a number of factors, from the communications router to the application on the PC. While the actual configuration and maintenance of communications between client workstations and IBM i servers is beyond the scope of this guide, the information in this chapter may help you to determine the cause of your problem.

Start with these basic checks:

Can you get a 5250 terminal emulation session running under the communications router in order to sign on to the IBM i? 

If you can't, then work with your communications router and its configuration options until you can. If you can't run a terminal emulation session then there is no way that you are going to get a session using LANSA Open to start and run.

Check that the user profile you are using is validly defined and is authorized to use the LANSA system and partition. 

Do this simple test:

Check that the partition and language code that you are using are valid. 

Check that your LANSA system is correctly licensed. 

Sign on to LANSA for i as QSECOFR, or the LANSA system owner, and use the command LANSA REQUEST(LICENSE) to display your current licensing status.

Check the communications subsystem on the IBM i is active. 

Check the communications router is active and correctly started on your workstation. 

Check for a communication job on the IBM i

Does an IBM i "workstation" job appear in the QCMN subsystem?

Check that the file or library you are trying to open exists 

   01 - The library does not exist.

   02 - The file does not exist but the library does exist.

   03 - The file does not exist.


   The reason for that failure can be clearly identified, however, there are other errors when the cause is not so straightforward. For example:

   This could be caused by:


   This could be caused by:


   This could be caused by:

General Protection Fault (GPF) 

A GPF usually occurs when an application tries to access a part of the memory that is already allocated. It can also occur when running out of stack space.

If you request help from your LANSA vendor, be sure to include the job log with the problem's description.