This SAS KB article explains how to obtain an enhanced debugging log for PROC HTTP.

The Downloads section contains XML files that enable the additional logging after you follow the steps in this article. If you are running SAS^® 9.4M0 (TS1M0), SAS^® 9.4M1 (TS1M1), or SAS^® 9.4M2 (TS1M2), download the logging_m2.xml file. If you are running SAS^® 9.4M3 (TS1M3) or later, download the logging_m3.xml file. Then, use the following instructions for obtaining a debug log from PROC HTTP.

You should save the XML file that is relevant for your SAS release to a location that is accessible by the machine running SAS on the compute tier. This machine is identified in the log with the following macro variable:

%put &syshostname;

Note: If you are running SAS^® Enterprise Guide^®, the value that is returned by the SYSHOSTNAME variable might not be your local machine.

A SAS administrator should then complete the following steps:  

1. Add the LOGCONFIGLOC= system option for the file. You can add it in one of the following two ways:

• Modify the configuration file in use by that SAS session.
• Invoke SAS by using the -logconfigloc command to specify the location of the attached file. Here is an example of the command:

–logconfigloc  \\directory\logging_mN.xml

(Note that \\directory is the directory path where your logging_mN.xml file is stored. Replace N in the file name with the correct value.)

2. The debug logging is written to an out.log file in the same directory from which SAS is launched. In Microsoft Windows, the location of the sas.exe program can be determined with this code:

   %put %sysget(sasroot);

You can change the location of the out.log file by editing the relevant XML file and specifying a directory as part of the VALUE= parameter, as shown below:

   <appender class="FileAppender" name="File">
      <param name="File" value="out.log"/>  

3. Enable the LOGCONFIGLOC= option before you run PROC HTTP. Place the following code before your PROC HTTP step:

   proc options option=logconfigloc;
   run;

4. Run your failing PROC HTTP code, which now contains the debug logging in effect. Then, send SAS Technical Support the resulting out.log file.

Note:  If you start SAS in batch mode or in server mode and the LOGCONFIGLOC= option is specified, logging is done by the SAS logging facility. The traditional LOGPARM= SAS log option is ignored. The traditional LOG= SAS log option is applied only when the %S{App.Log} conversion character is specified in the logging configuration file. For more information, see SAS Logging: Configuration and Programming Reference (from LOG System Option: Windows in SAS^® 9.4 Companion for Windows, Fifth Edition). This information also applies to UNIX environments.

Therefore, you must include -altlog on your command line if you start SAS in batch mode or in server mode:

   -altlog "/tmp/sas.log"

Starting in SAS^® 9.4M5 (TS1M5), PROC HTTP supports a DEBUG statement. Although the information that the DEBUG statement generates is helpful, the information that you retrieve from the out.log file is still necessary for troubleshooting PROC HTTP.

---

Downloads

logging_m2.xml (SAS^® 9.4M0, SAS^® 9.4M1, or SAS^® 9.4M2)
logging_m3.xml (SAS^® 9.4M3 or higher)