ICAT Installation/Setup for Two-Tiered Connection
IBM Shop IBM Support Download
HomeNewsProductsServicesSolutionsAbout IBM
Search 

ICAT Installation/Setup for Two-Tiered Connection

This page shows how to set up the two-tiered network connection for the ICAT remote debugger. This is a two-system LAN/WAN setup that facilitates the transmission of UDP network packets from ICAT on the host system to KDBNET.SYS on the target KDB system. The illustration below shows the two-tiered setup information. For questions about COMx connections, see Installation/Setup of ICAT COMx Connection.


Target OS/2 Setup

The kernel debugger is required for this setup, and KDBNET.SYS must be installed on the target system, too, per the following steps:

  1. In CONFIG.SYS, locate the line containing PROTMAN.OS2
  2. After this line, enter: DEVICE=x:\y\KDBNET.SYS /V /Id.d.d.d /Ppppp where x and y are the drive letter and path to the directory where you wish to store KDBNET.SYS. The IBMCOM subdirectory is probably the most convenient place to put it. d.d.d.d is the IP address of the target machine pppp is the port number on which KDBNET will accept UDP data (1000 is the recommended port number)
  3. Locate the PROTOCOL.INI file, which should be in the IBMCOM subdirectory.
  4. In the stanza that begins with [IBMLXCFG], add the following line: kdbnet_nif = kdbnet.nif
  5. Add a new stanza to PROTOCOL.INI: [KDBNET_nif] Bindings = IBMFEEO2_nif DriverName = KDBNET$ KDBIPADDR = "d.d.d.d" KDBSNETMASK = "255.255.248.0" KDBPORT = 1000 NMPORT = 1001 BCASTNOTIFY = "YES" NNOACTION = "C" where d.d.d.d is replaced with the IP address of the machine.
  6. Look at the other stanzas of the PROTOCOL.INI file. If the value of "Bindings =" is something other than IBMFEE02_nif, use that value instead of IBMFEE02_nif.
  7. Copy the file KDBNET.NIF to the IBMCOM\PROTOCOL subdirectory.
  8. Reboot the target machine. If KDBNET is properly installed, you should see a "banner" during the bootup process.




Host OS/2 Setup

The host system can be running almost any version of OS/2, but we recommend OS/2 3.0 or later. You will need to modify the seticat.cmd file's environment variable, CAT_MACHINE=d.d.d.d:port

where d.d.d.d is the IP address of the target system port should use the suggested value of 1000 for the KDB port number Example: SET CAT_MACHINE=9.51.1.1:1000

You will also need to change:

CAT_COMMUNICATION_TYPE=UDP By default it is set to: CAT_COMMUNICATION_TYPE=ASYNC_SIGBRK

Once you have run the modified setenv.cmd and seticat.cmd files, you should be able to start icatgam.exe and Attach to the remote system via the LAN/WAN. If you have connection problems, invoke catdebug.cmd before running ICAT, and when you shut down the debugger, inspect the resulting catdebug.001 output file.




Some Notes on Two-tiered Debugging

Don't reboot the target machine from ICAT's File pulldown if KDBNET.SYS is installed on that target. ICAT and KDB and KDBNET.SYS can't resync in this manner.

Limitations using KDBNET.SYS/ICAT UDP debugging:

  • On the target machine, KBDNET.SYS does not function until the RUN=NETBIND.EXE has been completed. This occurs AFTER all device drivers have been loaded and initialized, therefore ICAT thru KBDNET.SYS cannot be used to debug device driver loading or initialization.

  • The CONFIG.SYS contains a RUN=\IBMCOM\PROTOCOL\NETBIND.EXE statement. After NETBIND.EXE is run, UDP packets will be available for KDBNET.SYS to examine. Therefore, the earliest one can use ICAT in UDP mode is after NETBIND.EXE has completed. To debug a device driver during system initialization time, one must use ICAT in serial mode.




PrivacyLegalContact---
⌐ 1999 IBM Corporation