Debugging Stored Processes

Examining the SAS Log

The client interfaces that are provided to stored processes usually include a mechanism for retrieving the SAS log from a stored process. For example, passing the input parameter _DEBUG=LOG to the SAS Stored Process Web Application causes the SAS log to be returned with the stored process output. The SAS log is directly accessible from the Stored Process Service API. Assuming that your installation is configured correctly, most run-time stored process errors will appear in the SAS log.

If you are unable to access the SAS log from the client interface, you might be able to access the SAS log from the server log files. The server administrator controls the level of server logging that is used and the location of the server log files. Server log options vary depending on the server type.

Stored process and workspace servers enable you to capture the SAS log for each stored process in the server log. To enable logging for the server, perform the following steps:

In the .../Lev1/SASApp/StoredProcessServer/ directory, rename the logconfig.xml file as logconfig_orig.xml.

Note: For a workspace server, this file is located in the .../Lev1/SASApp/WorkspaceServer/ directory.
Make a copy of the logconfig.trace.xml file (which is located in the same directory), and name the copy logconfig.xml.
Restart the Object Spawner.

Note: If you enable logging for the workspace server, then all users who run workspace server requests must have write access to the location where the log files are written (because the workspace server runs under the client user's account). [cautionend]

For more information about SAS logging, see SAS Logging: Configuration and Programming Reference.

Top of Page