text: *Figure 5-16 Defining a storage set for VSAM*
  
  Based on these parameters, Content Manager OnDemand creates VSAM datasets during 
  the**arsload**program. A catalog entry is created, as shown in Example 5-2. 
  
  *Example 5-2 VSAM dataset name*
  
  VSAMTST.FAA.L1.FAAA 
  
  This catalog entry is created automatically by the Content Manager OnDemand system. The 
  only part that you can create for yourself is the first-level qualifier. The space allocation during 
  the Define Cluster is performed by the Content Manager OnDemand code, as well. The 
  default object size that is set when you define the application group influences the number of 
  bytes for the primary allocation and the secondary allocation. The number of bytes is divided 
  by 16 for the primary allocation. Every time that an**arsload**command runs with this storage 
  set, this amount of data is allocated even if the objects are much smaller. 
  
  Every load creates two VSAM datasets: one VSAM dataset for the data, and one VSAM 
  dataset for the index. Every Define Cluster of a VSAM dataset is a catalog entry. If you have 
  several million loads with this storage set, your catalog grows large. 