text: In particular, the**ARSYSPIN**Input Exit (UX03) and Separator Exit (UX06) provide substantially 
  more information about the job that produced the spool file that is being processed than what 
  is available at the time when**APKACIF**(or another indexer program) is driven by Content 
  Manager OnDemand. In addition, the processing impact of driving**ARSYSPIN**exit routines is 
  lower than the impact that is associated with the indexer exit routines, such as**ARSSPVIN**. 
  
  **ARSSPVIN**is a sample**APKACIF**input exit that is provided with**ARSYSPIN**to introduce additional 
  index values into the data stream, by using a “trailer” record. Trailer records are inserted at 
  the end of the JESMSGLG data. They reflect the highest severity condition (a step completion 
  code, an ABEND code, or another type of problem, such as a JCL error) that is observed in 
  messages that are contained within these spool files. 
  
  **Special considerations for APKACIF exits that are written in COBOL**
  The provided sample exit is written as a COBOL main program. To prevent the IBM Language 
  Environment® from creating and destroying the COBOL runtime environment each time that 
  **ARSSPVIN**is called, a CEEUOPT CSECT must be assembled and link-edited with the COBOL 
  object code. 