84 IBM Content Manager OnDemand Guide
Because this architecture enables a system to create tables when the maximum table size is 
reached, no logical limitation exists to the system; rather, the limitation is on the physical 
resources, such as processing power, disk space, object servers, and storage hardware.
4.4  Search sequence 
To better understand the relationship between the various Content Manager OnDemand 
tables, we describe a search sequence within a Content Manager OnDemand system in this 
section. A search sequence scans through multiple Content Manager OnDemand tables. We 
describe the logical flow that the system goes through during a Content Manager OnDemand 
search. 
By using the Content Manager OnDemand standard Windows client, you can open a search 
criteria window (see Figure 4-3). In our example, four index fields exist: Name, Account, 
Statement Date, and Balance. The example shows a search for a specific date and balance 
amount.
Figure 4-3   Content Manager OnDemand Client search criteria window
After you enter these values, Content Manager OnDemand uses the date information and 
searches the segment table ARSEG to find the application group data table that contains that 
date. Content Manager OnDemand then searches the identified table_name (in our example 
HAA1) for the index values (1994-03-07 and 104.18) and finds the matching Statement_date 
and the Balance and returns these values to the client in a search result list.
Any individual document from within this result list can then be retrieved for display on the 
client. Content Manager OnDemand locates the document in the archive by using the object 
name, document offset, and length. In the background, the document data is automatically 
decompressed before it is displayed.
Figure 4-4 on page 85 shows the details of this search sequence from a folder.