The other option might be the SPACE CONSTRAINT Parameter within the DATA CLASS.
Spreading the requested quantity over multiple volumes
Allocating a percentage of the requested quantity
Using more than 5 extents
Space Constraint Relief specifies whether or not to retry an allocation that
was unsuccessful due to space constraints on the volume. Note that allocation
is attempted on all candidate volumes before it is retried. This attribute
applies only to system- managed data sets, and is limited to new data set
allocations, and while extending the data set on new volumes.
Y specifies that SMS retry the allocation.
N specifies that SMS does not retry the allocation, so that allocation is not
attempted on multiple volumes. This is the default.
Reduce Space Up to (%) specifies the amount by which you want to reduce the
requested space quantity when the allocation is retried. You must specify Y for
the Space Constraint Relief attribute. Valid values are 0 to 99.
If you request space constraint relief but do not specify a percentage value
(either 0 or blank), SMS does not reduce the requested space quantity. This
implies your application cannot tolerate a reduction in the space to be
allocated, so only the 5 extent limit is relieve
Data Class Name . . : DB2VOLS
Data Set Name Type . . . . . :
If Extended . . . . . . . . :
Extended Addressability . . : NO
Record Access Bias . . . . :
Space Constraint Relief . . . : YES
Reduce Space Up To (%) . . : 20
Dynamic Volume Count . . . :
Compaction . . . . . . . . . :
Spanned / Nonspanned . . . . :
Media Interchange
Media Type . . . . . . . . :
Recording Technology . . . :
Performance Scaling . . . . :
Performance Segmentation . :
And the last area you might look at is EXTENT CONSTRAINT REMOVAL
Data Class Name : DB2VOLS
Reuse . . . . . . . . . . . : NO
Initial Load . . . . . . . . : RECOVERY
BWO . . . . . . . . . . . . :
Log . . . . . . . . . . . . :
Logstream Id . . . . . . . . :
FRlog . . . . . . . . . . . :
RLS CF Cache Value . . . . . : ALL
RLS Above the 2-GB Bar . . . : NO
Extent Constraint Removal . : NO
Lizette
>> A B37-04 says you did not successfully get all the space needed for
>the primary allocation on the 1st volumes. Products like DTS Software,
>STOPX37, etc can also help prevent these types of failures.
>>
>> When SPACE= is coded you have 5 extents to get the primary allocation
>on the volume. The secondary space allocation has upto (I think) 123
>extents to get it. But when you go after the primary allocation, you
>need to do it in 5 extents. This can be avoided by codind VOLUME COUNT
>in Data class, or using a software product like STOPX37.
>>
>> When the pack or pool is fragmented, small chunks of storage is
>available, then it is possible you can not get 2000 cylinders in 5
>extents. Hence the SB37-04
>>
>> To correct this you can code your Data Class to allow more volumes
>(canidates) to be available to your files.
>>
>
>Correction: "this" cannot be corrected with multivolume datasets. A next
>volume will be taken when a *secondary* extent does not fit anymore.
>
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
