Chapter 11. Exits 251
Figure 11-1   Select Content Manager OnDemand system parameters
3. To choose a User Exit Logging option, select the option. 
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:
/SM590000Capturing failed logon attempts (AIX)
/SM590000Notifying 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.
Capturing failed logon attempts (AIX)
Example 11-4 on page 252 is an extract from a simple system logging exit that captures 
message code 31 (a failed logon attempt) and writes the user ID that was used and 
information about the network address of this user to a file. In this case, the file name is a 
combination of the system date and the string failedlogon.log. This system log exit writes 
all of the failed logon attempts for each day to a file that can then be sorted and analyzed by 
other utilities to alert for possible security risks. 
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.