The SAS Federation Server enables you to execute DS2 code from within a Java application. In order to do this, you use Java SQL CALL statements to create a JDBC call to the SAS Federation Server. In the JDBC call, you specify which DS2 code you want to run as well as the location within the SAS Federation Server where the DS2 code is stored. This method of executing DS2 code is used by SAS solutions such as SAS^® Real-Time Decision Manager.

If errors occur during execution of the DS2 code, the errors are not logged as they would be for PROC DS2 execution within Base SAS^®.

To work around this problem, add the following logger to your SAS Federation Server logging configuration file (dfs_log.xml or dfs_log4sas.xml):

<logger name="App.Statement.Statement.GetDiagRecs">
       <level value="trace"/>
    </logger>

Adding these lines causes SAS Federation Server to log all of the DS2 SQL statement diagnostic records to the SAS Federation Server log file. If the diagnostic records are not sufficient, you can install a hot fix for SAS Federation Server that provides improved DS2 logging.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Federation Server 4.1 is available at:

A fix for this issue for SAS Federation Server 4.1_M1 is available at: