text: – No request exists for the currently mounted optical disk volume that is waiting to be 
  processed on the OAM optical dispatcher queue. 
  
  – The OAM optical dispatcher found a read request for another optical disk volume 
  
  (either the opposite side of the currently mounted volume or an unmounted optical disk 
  volume) and is about to dispatch this unit of work. 
  
  – A nonzero optical dispatcher delay value is specified with the**OPTICALDISPATCHERDELAY**
  keyword on the**SETOPT**statement in the CBROAMxx PARMLIB member. 
  
  If another read request for the currently mounted optical disk volume arrives within the delay 
  interval, that unit of work is dispatched immediately upon arrival. If no read request for the 
  currently mounted optical disk volume arrives within the delay interval, another request for a 
  different optical disk volume (either the opposite side of the currently mounted optical disk 
  volume or an unmounted optical disk volume) is dispatched. Valid values for seconds are 
  decimal numbers 1 - 60. If usage of this parameter is necessary, use of a low value, 1 - 5, is 
  suggested. 
  
  **ARS.CFG setting**
  If you are configuring a Content Manager OnDemand for z/OS system to use OAM for archive 
  storage, you must ensure that the ars.cfg file is updated to reflect that OAM is used as the 
  storage manager. Example 5-1 shows an example of the settings to configure for OAM 
  archive storage enablement for Content Manager OnDemand. 