text: To activate the system log exit, complete the following steps: 
  
  1. Start the Administrator Client and log on to the server on which you intend to use the 
  system logging exit. 
  
  2. Right-click the name of the server in the list and select**System Parameters**, as shown in 
  Figure 11-1 on page 251. 
  
  *Figure 11-1 Select Content Manager OnDemand system parameters*
  
  3. To choose a User Exit Logging option, select the option. 
  
  **Tip:**The arslog exit file is run by the same user that owns the**arssockd**process that 
  calls this exit. A common reason for receiving no response from this exit is*access*
  *permissions*on either the arslog file itself or files and directories that are accessed 
  within**arslog**. 
  
  Content Manager OnDemand provides an exit for each of the four system logging event 
  points. Use these exits to filter the messages and act when a particular event occurs. For 
  example, you can provide a user exit program that sends a message to a security 
  administrator when an unsuccessful logon attempt occurs. 
  
  **System log exit samples**
  To demonstrate the common uses for the system log exit, we provide two typical examples: 
  
  (cid:2) Capturing failed logon attempts (AIX) 
  (cid:2) Notifying another system when a load completes (AIX) 
  
  For simplicity, we do not demonstrate the system log exits across all supported platforms. We 
  recognize that the scripting languages between platforms vary, but the principles that we 
  describe here are uniform across all supported platforms; only the syntax differs. 