http://sda.berkeley.edu:8080/quicktables/quickconfig.do?teds2000

To debug this start-up link just add a "+debug" after the dataset key:

http://sda.berkeley.edu:8080/quicktables/quickconfig.do?teds2000+debug

When you click on the debug mode link above you'll see a page of debug output that: 1) checks for various errors; 2) lists the contents of the dataset's XML configuration file in a (somewhat) reader-friendly manner so you can determine if any configuration information is missing or incorrect. Since there are no errors in the above setup, debug mode doesn't report any problems. Let's look at a few configurations with (intentional) errors to see what happens when there are problems.

• XML configuration file isn't well-formed

  This XML file has a typo: the "progspath" element is mis-spelled "progspat". Here's the first few lines of the file:

  <xml version="1.0"?>
  <!DOCTYPE sdaconfig SYSTEM "http://sda.berkeley.edu/quicktables/sdaconfig.dtd">
  
  <sdaconfig>
  
       <progspat>csm/7502docs/qrtesting/bin</progspath>
  
  (rest of file omitted ...)
  

  Since the opening "progspat" doesn't match the closing "progspath" this file is not well-formed. As you can see, this results in the display of just a basic error page. The full debug mode output will only be produced once you have a well-formed XML file.

• "progspath" specifies a non-existent directory

  This XML file is well-formed. However, when debug mode checks the "progspath" specification, it detects that the listed directory doesn't exist:

  Checking for errors ...
  Error: 'progspath' does not specify a valid directory: /csm/7502docs/bad_dir

  Debug mode checks the accessibility of various directories and files listed in the XML configuration file and reports any problems it finds.

[Note: we expect to make some additions and improvements to the debug mode output while beta-testing continues. If you find any problems or have any suggestions, please let us know.]