Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

Prior to SAS^® 9.1.3 Service Pack 4, a startup script set the options to create a log for the SAS Object Spawner. Starting with SAS 9.1.3, the options to create the SAS Object Spawner log were removed.

The reasons for this decision were based on the logs were useful only for the purpose of debugging and the logs required a very large amount of storage space.

If you wish to enable the SAS Object Spawner log, select one of the options below and follow the instructions for that option:

Option 1: Use SAS^® Management Console

1. Open SAS Management Console. From the Server Manager plug-in, open properties for the SASMain - Spawner.
2. From the Initialization tab, check the box beside Verbose; and enter the path and filename for the log file.
3. Restart the SAS Object Spawner.

Option 2: Telnet to the Operator Port

1. Telnet to the SAS Object Spawner's operator port (default is port 8581).
2. Enter the operator password sasobjspawn to establish the connection.
3. Issue the btrace (begin trace) command:
   btrace <filename>

   Note: <filename> is a fully qualified path to the file in which the spawner activity will be logged.

4. Issue the etrace (end trace) command to stop logging.

Note that information regarding the SAS servers is read from the SAS^® Open Metadata Repository by the SAS Object Spawner at invocation.

If you want this information to be recorded in the SAS Object Spawner logs, you must select an operating system and follow the instructions below for that operating system:

For UNIX:

1. Add the saslogfile (-slf) and sasverbose (-sv) options to the file:
   !SASROOT/BIArchitecture/Lev1/SASMain/ObjectSpawner/ObjectSpawner.sh

   Example:

      nohup $CMD -sasSpawnerCn "$SPWNNAME" -sv -slf $DIR/logs/ 
      objspawn.log -omrconfigfile $XMLCFG > $DIR/logs/ 
      objspawn_console.log 2>&1 & 
   

2. Stop the SAS Object Spawner process by executing:
   "ObjectSpawner.sh stop".
3. Restart the SAS Object Spawner process by executing
   "ObjectSpawner.sh start".

For WINDOWS:

1. Add the saslogfile (-slf) and sasverbose (-sv) options to the ":install" section of the following file:

      C:\SAS\bundle_name\Lev1\SASMain\ObjectSpawner\ObjectSpawner.bat
   

Example:

   :install 
   start /b "Object Spawner" "%sasdir%\objspawn" –sasSpawnerCn "%SPWNNAME%" 
   –OMRconfigfile "C:\SAS\EntBIServer\Lev1\SASMain\ObjectSpawner\OMRConfig.xml" –sv 
   –slf "C:\SAS\EntBIServer\Lev1\SASMain\ObjectSpawner\logs\objspawn.log" –install 
   –name "%SASServiceNAME%" %DEPENDS%
   goto end2 

NOTE: The second line in the example above and the five lines which follow it must be specified on the SAME LINE in your ObjectSpawner.bat file. The long line above was split into multiple lines for readability. So, the line begins with "start /b" and ends with "%DEPENDS".

2. Stop the SAS Object Spawner service through the Windows Services window.
3. Remove the SAS Object Spawner service by executing
   "ObjectSpawner.bat -remove".
4. Reinstall the SAS Object Spawner service by executing
   "ObjectSpawner.bat -install".
5. Start the SAS Object Spawner service through the Windows Services window.

Operating System and Release Information