Debugger Problems

This is often caused by either of the following:

• The debugger .stb, .dll, or .exe is out of sync with the source code.

  Solution: Check the values of the CODEWATCH_STBPATH and CODEWATCH_SRCPATH environment variables for accuracy. Also, check the build dates and times of the .stb file, and the .dll or .exe file.

• A CICS application built with -margins 1,72.

  Solution: Build the application with no margins or with -margins 2,72.

Windows

You started the enterprise server region outside of the Visual Studio IDE.

Solution: Start the enterprise server regionfrom the Server Explorer in Visual Studio. When you start an enterprise server region outside of the Visual Studio IDE (using casstart or from ESCWA, for example), it runs as System, which prevents the debugger from accessing it properly. You can verify this by looking in the task manager to see the user ID under which your cassi.exe processes are running.

Linux/UNIX

If the problem is on a remote XServer display, this is likely due to a mismatch between the Linux/UNIX DISPLAY variable and the IP address/port number of the client machine.

Solution: Be sure that the IP address and port numbers are the same on both machines, and see that no firewall settings are preventing proper communication between the two.

• The CODEWATCH_STBPATH and CODEWATCH_SRCPATH do not point to the locations of your .stb and .pli files respectively.

  Solution: Recompile and relink using the -deb option.

• You are attempting to debug a .dll or .exe that you have not built for debugging.

  Solution: We recommend that you use the mmap Codewatch command to find the .dll or .exe you are attempting to debug. (See Mmap for details.) If you find it in a directory other than the directory where your newly built and debuggable .dll or .exe is located, review the settings for your enterprise server region. If the directory containing an old version of the .dll or .exe is listed before the directory that contains your newly created .dll or .exe in the search sequence, change the sequence order to find the new file first. For example, the CAS_BATCH_PATH environment variable searches for JCL programs to execute in the order of directories listed.