Previous Topic Next topic Print topic


Troubleshooting XDB Link Issues

Restriction: This topic applies to Windows environments only.

The following table gives a list of common problems and possible solutions.

Problem Solution
A DOS system error is returned on startup of IBM LAN Requester. Your Communications Manager, LAN feature profile is using a station address that is identical to another workstation's address. Change the station address to be unique within the LAN.
When booting the Communications Manager, LU 6.2 sessions are not allowed on the SNA gateway for a downstream Gateway. Only the 3270 session allocates on the SDLC/Token Ring Gateway. Ensure you are using the correct CFG for Communications Manager and that it allows APPC. Ensure the CFG pointed to in config.sys for Communications Manager allows APPC.
The LAN Requester abends when selected from the Communications Manager main menu.

 

NetBIOS support is missing from config.sys and the Communications Manager CFG. Correct your Communications Manager CFG, access the LAN feature profiles section and configure the IEEE802 option (you may choose not to use Univ Admin Addresses and opt to create your own). Now you may reboot your machine and try to access the LAN Requester. If this fails to work, you must re-install Communications Manager. Remove the existing manager and re-install using the CFG file already modified above.
Import is taking a long time to transfer records. DB2 is slow. Timeout errors are occurring. Import was started without a commit interval being specified. Since no interval was specified, DB2 is filling up its buffer pool with a single unit of work. Run Import using the command:
xdbimpor /cnnn 

where nnn is the commit interval. Try 50 to start.

Previous Topic Next topic Print topic