Page History
[ |../../index.htm#lansa/vgudbb_0010.htm]
You are here:
...
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.
...
- The space declared in data area DC@A10 not being big enough to hold the records selected. Increase the size of the value in DC@A10.
...
- MCH0802 Message: Total parameters passed does not match number required.
...
- Using the *BLOCKBYRRNnnn or the *RECEIVEIMMED select option, but with *IOMXSERVER, *IOMBLOCKBYKEY and *IOMBLOCKBYRRN missing from data area DC@OSVEROP's I/O module. Add these keywords into data area DC@OSVEROP and recreate the I/O module.
- Other objects in the library list with same name as the I/O module.
- MCH3601 Message: Pointer not set for location referenced
...
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.
[ |../../index.htm#lansa/vgudbb_0010.htm]