PREPARING FOR REMOTE DEBUG: Terms: MUT: Machine Under Test - Machine with failure that is being debugged. DEBUG SYSTEM - System that is initiating the debug session at the remote site and examining the failure on the MUT. You need: 1. An appropriate cable to connect the modem to your system's com port. 2. A 2400 baud or higher Hayes-compatible modem, which can be either internal or external. An external modem is preferred so that the user can monitor the lights while the remote site is connecting and reset the modem without affecting the MUT. A 9600 baud modem is preferred. Lower than 2400 baud can be used by special arrangement. 3. Two phone lines, one is the voice or talk line, the other is for your modem. The modem phone line should be an analog line or a digital phone with an acoustic coupler. It MUST not have an answering machine or voicemail connected to it. It also should not go through a switchboard that requires further dialing. If there is a live operator, special arrangements can be made. It must be a line that only rings in one location. The following instructions will assist you when you work together with your analyst to set up and establish communications with the remote debug host. The instructions must be followed EXACTLY. The instructions are space dependent and something so trivial as an extra carriage return can keep your system from booting. Follow these steps: 1. Connect the cable from the com port to the modem. You should use COM2 if you have two or more com ports on your system. If there is no COM2, attach cable to COM1. If you have at least two COM ports and absolutely need to use COM1, be sure to choose the appropriate COM1 settings in the KDB.INI, as described below in step #4. COM3 and higher are not supported for doing a remote debug. If using 1.3 and you have two com ports, COM2 MUST be used for the debug session. COM1 can ONLY be used if the system has only 1 communications port. 2. The debug kernel defaults to 9600. The KDB.INI file can change the speed at which the kernel communicates with the modem. The modem of the MUT must be able to be set to the same speed as the modem of the remote site. 3. Put the kernel debugger install diskette in your diskette drive. At an OS/2 Window or Full screen prompt, type "a:install" (or b:install, as appropriate). You should be in the root directory of your boot drive (normally the default directory of the OS/2 Command Prompt icon). 4. If you need to change the com port or baud rate, or if the analyst has commands that need to be set on every bootup, you must set up a KDB.INI file. This MUST be done live and MUST NOT be done with an editor. Type the following after you finish with the above install. NOTE: means hit enter, ª indicates a necessary space copyªconªkdb.ini .bª2400tª1 (Enter a "dot" in front of the "b") (Replace 1 with 2 if modem is on com2 and the 2400 with whatever speed you need.) g (File closes.) (note that some people have reported problems if you hit enter before hitting F6) 5. Type the following at the command line to see if the system recognizes the modem: mode com1 (Or com2. You will see baud rate, parity, etc. listed.) If you receive an error message, verify that you have the comm driver loaded in the config.sys. DEVICE=C:\OS2\COM02.SYS (1.3 microchannel systems) DEVICE=C:\OS2\COM01.SYS (1.3 AT BUS systems) DEVICE=C:\OS2\COM.SYS (2.x systems) *Note that you do not have to have the COM device driver installed once you are done setting up your modem. Also note that the COM.SYS supplied with 2.1 GA requires that DOS support (including VCOM.SYS) be active. No other version has this requirement. This is APAR PJ08728. 6. Refer to the accompanying Modemset.txt file to see whether we have any known DIP switch settings for your modem. 7. Type "t ". This will pull up the T.exe that got installed with the kernel debug package. The default is com1/9600 baud. If this does not match your modem/port setup, hit F2 twice. You can now change COM port and speed. Hit Enter to return to the main screen. If you type AT you should get back an OK. If not, go back into the setup screen and see if changing Handshaking from Xon/Xoff to Hardware helps. If not, you will need to fix your modem, cable, or whatever -- OS/2 support cannot help. Once you get OK back when you type AT, refer to the accompanying Modemset.txt file for AT commands for your modem. *Note: there is currently a bug in T.exe such that it cannot access com2 if a mouse is on com1. If this is true for you, you must either use your own com package (such as PROCOMM) to set up the modem or move your mouse to use com2. 8. Now you are ready to call your analyst so that he/she may dial in and test your link before you recreate the failure. If you do not have his/her phone number, you can open a secondary call by calling 1 800-992-4777 with the PMR #. The analyst will return your call. 9. Do an orderly shutdown and reboot to activate the debugger. 10. Analyst now dials in. You should arrange to do a dialin before the problem occurs, if possible, to make sure everything is properly set up. ---------------------------------------------------------------- PREPARING FOR LOCAL DEBUG: Follow through step 4 above. 1. Reboot the MUT. You should see the kernel's signon at the debug terminal. You should see the message, "Symbols linked" on the screen. Do not proceed until this step is successful. 2. When the MUT has completed booting, press control-C at the debug terminal. You should see a register dump and a # prompt. The debug kernel has stopped the OS/2 machine under test (MUT);therefore, the MUT will appear to be dead. 3. Press G (the debug kernel command for GO) and press enter. Activity at the MUT will resume.