Page 1 of 1

VSAM secondary extents.

Posted: Fri Feb 26, 2016 1:21 pm
by Vasundhara R
I seek a clarification on the below job. This job defines a cluster:= like this:

Code: Select all

//CRTECLUS   EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*                             
//SYSIN    DD *                                    
  DEFINE -                                         
       CLUSTER -                                   
         ( -                                       
             NAME(THE.VSAM.CLUSTER) -                    
             LINEAR -                              
             CYL(9000 9000) -                    
             DATACLASS(DBAGDC) -                   
             VOLUMES(Z3X170 Z2D171) -              
             SHAREOPTIONS(2,3) -                     
         )                                         
/*        


When a download job run, that populates this cluster and it goes to allocate additional extents, it is allocating 540 trks. I thought it would allocate the secondary allocation of 9000 cylinders. What wrong did I guess? Please help.

Re: VSAM secondary extents.

Posted: Fri Feb 26, 2016 6:23 pm
by Robert Sample
Talk to your site support group. Possible reasons include (but are not limited to):
- SMS policy restricting extent size on certain volumes
- the volume only has 540 cylinders available
- storage pool limitations