Reload Analyzer Manual
Tandem Reload Analyzer Manual    Page 35 of 42 
  The average blocks per chain 
  The percentage of total blocks in the average chain 
Reload Analyzer cannot tell you whether or not to reload a file. Instead, you must take 
the output, analyze it, and consider the conditions on your system to determine 
whether it is advantageous to reload a file. Reload Analyzer only gives you only the 
information you need to make an informed decision about reloading. Whether you 
reload a file and when you do so is up to you.  
After you reload a file, you should see how the file has changed. Run Reload Analyzer 
against the reloaded file to see how the output has changed.  
Output After Reloading 
Example 2-6 shows the Reload Analyzer output for SALESDB after the file was 
reloaded. Note that the values, especially in the Data Chain Information section, have 
changed. This section compares this output with the output before the file was 
reloaded. 
Example 2-6. Output from SALESDB After Reloading 
Tandem Reload Analyzer - T9516H01-AAF (31MAR2010) Start time - 17:02.35 
$DATA.INSURNC.SALESDB1 
General Information:  
 Enscribe Block 512 <-- 
Unchanged 
 Type K (Format 1) IBlock 512 
 Code 300 Rec 64 
 Ext 17, 32 Extents Allocated 3 
 Maxextents 16 Buffered 
 Owner 20, 33 Audited 
 EOF 106496 Security (RWEP) 0000 
Block Information:  
 Total blocks read 208 Free blocks 0 
 Index blocks read 10 Bitmap blocks 1 
 Data blocks read 197 Unrecognizable 0 
 Total Total Avg # Min Max Avg Avg 
Level Blocks Recs Recs Recs Recs Slack Slack 
 2 1 9 9 9 9 239 46 
 1 9 197 21 14 34 29 5 
 DATA 197 1572 7 4 8 33 6 
Data Chain Information: 
Number of chains 1 <-- 
Previously 203 










