z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Support
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Exceeding the DRIVE STARTUP THRESHOLD

z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Support
SC23-6866-00

Figure 1 is an example of how OAM manages additional write requests for optical when the threshold is exceeded.

Figure 1. Another Drive is Started When DRIVE STARTUP THRESHOLD is Exceeded
SCENARIO:
 
# OF WRITE REQ.   # OF DRIVES           DRIVE STARTUP THRESHOLD
FOR STRGPA        CURRENTLY RUNNING     FOR STRGPA
 
12                1                     17
 
During the storage management cycle, more write requests are created 
for STRGPA that exceed the DRIVE STARTUP THRESHOLD set for this storage 
group.  The following occurs:
 
# OF WRITE REQ.   # OF DRIVES           DRIVE STARTUP THRESHOLD
FOR STRGPA        CURRENTLY RUNNING     FOR STRGPA
 
30                2                     17
 
OAM starts another drive to handle the excess requests for this
storage group as it continues to process requests on the first drive.
When the number of write requests drops below the threshold,
the number of drives decreases.

This parameter allows you to control the number of drives used concurrently for writing objects on optical volumes within a storage group. Setting the DRIVE STARTUP THRESHOLD to the maximum of 9999 with no more than one volume mounted for a storage group increases the likelihood that OAM will write the objects sequentially. The default value for DRIVE STARTUP THRESHOLD is 17.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014