text: *Figure 10-5 Two ways ARSEXPIR expires OAM and VSAM objects*
  
  The**ARSEXPIR**program uses SMF type 65 (for VSAM objects) or SMF type 85 (for OAM 
  objects). The installation must collect and install**ARSSMFWR**as the CBRHADUX OAM 
  auto-delete exit. For more information, see “Deleting OAM and VSAM Objects” in the*IBM*
  *Content Manager OnDemand for z/OS: Administration Guide*, SC19-1213. 
  
  **ARSSMFWR**determines which objects were deleted. The**ARSEXPIR**program then instructs the 
  Content Manager OnDemand server to remove the index entries. 
  
  <html>
          <head> <meta charset="UTF-8">
          <style>
          table, th, td {
              border: 1px solid black;
              font-size: 10px;
          }
          </style> </head>
          <body>
          <table frame="hsides" rules="groups" width="100%%">
              [html]<thead><tr><td>NOtes :</td></tr></thead><tbody><tr><td>• If one object for a load ID is deleted, all of the index entries for that load ID are deleted.</td></tr><tr><td>• Index errities of all objects that are recorded as being pelvisined by the SBF records are deleted regardless of the settings in the Life of Data and Indexes section on the Storage Management teat of the application proup. If you want to us w</td></tr><tr></tr></tbody>
          </table> </body> </html>