250 IBM Content Manager OnDemand Guide
The report administrator provides a program name for the index exit.
No restrictions exist for the type of processing that can be performed in an index exit, except 
that the exit must pass the standard parameter list back to the capture program. A sample 
COBOL exit is provided in ARSEXNDX, with the COBOL copybook ARSINDBK. A sample C 
exit is provided in ARSECNDX with the C header file ARSINDBH.
For more information about the OS/390 indexer, see IBM Content Manager OnDemand for 
z/OS and OS/390 - Indexing Reference, SC27-1375. 
11.4  System administration
In this section, we describe exits that are used for system administration: system message 
logging and server printer configuration. These exits are in the bin directory of the Content 
Manager OnDemand installation. 
11.4.1  System log exit for Multiplatforms 
The Content Manager OnDemand system log is a tool that is used by administrators. Y ou can 
use the Content Manager OnDemand Administrator Client to configure Content Manager 
OnDemand to record information, warning, and error messages in the system log. Content 
Manager OnDemand records messages, such as when users log on and log off the system. 
Content Manager OnDemand also records messages for application group activity, such as 
when clients query and retrieve data. Each operation that is performed by a user that involves 
a connection to the Content Manager OnDemand server can be logged. The detail that is 
captured within the system log can be configured so that only certain messages are retained, 
and other messages can be discarded. 
In addition, you can configure Content Manager OnDemand to send these messages to the 
arslog exit. The system log exit is supplied in the arslog file that is in the bin directory of the 
Content Manager OnDemand installation root for each platform. If the arslog file is opened in 
a text editor, it contains comments that provide a brief description of the exit and the order of 
the parameters that Content Manager OnDemand supplies to this exit. By default, the system 
log exit is not initialized within Content Manager OnDemand. Therefore, if you edit the arslog 
file to capture information, the exit does not run automatically. 
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.