The SAS® Stored Process Server does not create a detailed log file by default. However, you can create a detailed SAS Stored Process Server log file (that will contain information about all of the code that was executed) by using this approach:
.../Lev1/SASApp/StoredProcessServer/sasv9_usermods.cfg
The -logconfigloc line would be similar to the following:
-logconfigloc "<your_path_here>/Lev1/SASApp/StoredProcessServer/logconfig.trace.xml"
If you are using an AUTOEXEC file for your SAS Stored Process Server, your SAS Stored Process Server log will not contain information about the execution of your AUTOEXEC file. You can capture the log entries for your AUTOEXEC file by using either one of the following two approaches.
<logger name="App.Program"> <level value="Fatal"/> </logger>
to this:
<logger name="App.Program"> <level value="Info"/> </logger>
One disadvantage of using this approach is that it will cause the SAS Stored Process Server log file to contain additional information for each request that is executed (including two copies of all SAS® Stored Process code statements that are executed). The SAS Stored Process Server log file will be approximately two times as large as a log file which uses an App.Program logger of "Fatal".
Modify your sasv9_usermods.cfg file (which is located in the same directory as your logconfig.trace.xml file which was described above). Add the following lines in your sasv9_usermods.cfg file:
-log "<Your_STP_Directory_Here>\logs\STPServer_Startup_%Y-%m-%d_%v.log" -logparm "write=immediate rollover=session"
On the -LOG option line, you must insert the site–specific location of your logs directory for your SAS Stored Process Server. For example, you might have:
-log "C:\SAS\EntBIServer\Lev1\SASApp\StoredProcessServer\logs\STPServer_Startup_%Y-%m-%d_%v.log"
If you use this approach, then two logs will be created for each SAS Stored Process Server process. For example, you might have:
SASApp_STPServer_2008_12_03_7316.log STPServer_Startup_2008_12_03_7316v.log
The first file contains the SAS Stored Process Server log without the AUTOEXEC entries. The second file contains the AUTOEXEC file log entries that are associated with the first file.
When running the SAS Stored Process Server on UNIX machines, the ObjectSpawner_console.log file might contain Stored Process Server log entries that were created during the execution of the AUTOEXEC for the SAS Stored Process Server.
For more information about SAS® 9.2 logging see SAS® 9.2 Enhanced Logging Facilities.
Product Family | Product | System | SAS Release | |
Reported | Fixed* | |||
SAS System | SAS Integration Technologies | Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.2 TS2M0 | |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.2 TS2M0 | |||
z/OS | 9.2 TS2M0 | |||
Microsoft Windows Server 2003 Datacenter Edition | 9.2 TS2M0 | |||
Microsoft® Windows® for x64 | 9.2 TS2M0 | |||
Microsoft Windows XP 64-bit Edition | 9.2 TS2M0 | |||
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.2 TS2M0 | |||
Windows Vista | 9.2 TS2M0 | |||
Microsoft Windows XP Professional | 9.2 TS2M0 | |||
Microsoft Windows Server 2003 Standard Edition | 9.2 TS2M0 | |||
Microsoft Windows Server 2003 Enterprise Edition | 9.2 TS2M0 | |||
64-bit Enabled AIX | 9.2 TS2M0 | |||
64-bit Enabled HP-UX | 9.2 TS2M0 | |||
64-bit Enabled Solaris | 9.2 TS2M0 | |||
HP-UX IPF | 9.2 TS2M0 | |||
Linux | 9.2 TS2M0 | |||
Linux for x64 | 9.2 TS2M0 | |||
OpenVMS on HP Integrity | 9.2 TS2M0 | |||
Solaris for x64 | 9.2 TS2M0 |
Type: | Usage Note |
Priority: | |
Topic: | System Administration ==> Servers ==> Integration Technologies |
Date Modified: | 2020-05-01 12:14:27 |
Date Created: | 2008-12-03 12:06:17 |