maximum number of extent



JES, JES2, JCL utilities, IDCAMS, Compile & Run JCLs, PROCs etc...

maximum number of extent

Postby samb01 » Tue Jun 25, 2013 1:04 pm

hello,

when i read the ibm doc, i can see the maximum number of extent for a dasd multivolume is 255 :


http://publib.boulder.ibm.com/infocente ... ts_156.htm

Space for a disk data set is assigned in extents. An extent is a contiguous number of disk drive tracks, cylinders, or blocks. Data sets can increase in extents as they grow. Older types of data sets can have up to 16 extents per volume. Newer types of data sets can have up to 128 extents per volume or 255 extents total on multiple volumes.


Actually i have a dataset with 479 extent!! I thouth i t was not possible...

Command ===>                                                  Scroll ===> PAGE
                                                                             
Command - Enter "/" to select action                        Tracks %Used   XT
------------------------------------------------------------------------------
         YCVNJ.JKHG.HULKJHGF.GHH.GHT                    378585  100   479
***************************** End of Data Set list ***************************



It abended in B37... :

VAM0096                                                                 
DOES IT FIT SUPPORT REDUCE TO FIT OPERATION STARTING FOR               
VAM0096 JLMPYE05 sORT93,SORTOUT,YCVNJ.JKHG.HULKJHGF.GHH.GHT             
VAM0096 REDUCE TO FIT OPERATION SUCCESSFUL FOR                         
VAM0096 JLMPYE05,SORT93,SORTOUT,YCVNJ.JKHG.HULKJHGF.GHH.GHT             
VAM0096 SECONDARY REDUCED FROM 273 CYL TO 246 CYL                       
VAM0096 DOES IT FIT SUPPORT REDUCE TO FIT OPERATION STARTING FOR       
VAM0096 JLMPYE05,SORT93,SORTOUT,YCVNJ.JKHG.HULKJHGF.GHH.GHT             
VAM0096 REDUCE TO FIT OPERATION SUCCESSFUL FOR                         
VAM0096 JLMPYE05,SORT93,SORTOUT,YCVNJ.JKHG.HULKJHGF.GHH.GHT             
VAM0096 SECONDARY REDUCED FROM 273 CYL TO 37 CYL                       
IEC030I B37-04,IFG0554A,JLMPYE05,SORT93,SORTOUT,A40E,VPRP09,YCVNJ.JKHG.H
IEA995I SYMPTOM DUMP OUTPUT  121                                       
SYSTEM COMPLETION CODE=B37  REASON CODE=00000004                       



the sort step is :

//SORT93   EXEC PGM=SORT,COND=(08,LE)                           
//*                                                             
//SORTIN    DD DISP=SHR,DSN=YCVNJ.JKHG.HULKJHGF.GHH.GHT.S87   
//SORTOUT   DD DSN=YCVNJ.JKHG.HULKJHGF.GHH.GHT,           
//          DISP=(NEW,CATLG,CATLG),DSORG=PS,                     
//          DCB=(*.SORTIN),UNIT=3390,                           
//          SPACE=(CYL,(273,273),RLSE)                           
//SYSOUT    DD SYSOUT=*                                         
//SYSPRINT  DD SYSOUT=*                                         
//SYSIN     DD *                                                 
 SORT FIELDS=(0270,0010,A),FORMAT=CH                             
/*                                                               



the dataset in entry : YCVNJ.JKHG.HULKJHGF.GHH.GHT.S87 ha the following space :

DSLIST - Data Sets Matching UVALG9.FIGEFLF1.JPKMDE1$.SORT87         Row 1 of 1
Command ===>                                                  Scroll ===> PAGE
                                                                             
Command - Enter "/" to select action                        Tracks %Used   XT
------------------------------------------------------------------------------
         YCVNJ.JKHG.HULKJHGF.GHH.GHT.S87                    415275   99   108
***************************** End of Data Set list ***************************




I saw the dataclass and the volcount is 30...

May be changing it is a good solution because the dataset YCVNJ.JKHG.HULKJHGF.GHH.GHT is in 30 volume (not more...)

I could try with 59 (it's the maximum) :

http://publib.boulder.ibm.com/infocente ... xddvol.htm

Volume Count for System-Managed DASD Data Sets: You cannot specify a volume count for an existing system-managed DASD data set. (If you do, the system will ignore it.) When you create a new system-managed DASD data set, the volume count defined in the data class may be overridden by using the volume-count subparameter. However, if the volume-count subparameter specifies a value greater then 59, the system will set the volume count to a maximum of 59. The maximum volume count for a VSAM or System-Managed DASD data set is 59.


If you have an other idea...

Thank's for your help.
samb01
 
Posts: 236
Joined: Mon Nov 16, 2009 7:24 pm
Has thanked: 0 time
Been thanked: 0 time

Re: maximum number of extent

 

Re: maximum number of extent

Postby Robert Sample » Tue Jun 25, 2013 3:01 pm

As the manual quote you posted indicates,
Older types of data sets can have up to 16 extents per volume.
A disk data set may reside on 59 volumes, times 16 extents per volume, or 944 total extents.
Robert Sample
Global moderator
 
Posts: 3367
Joined: Sat Dec 19, 2009 8:32 pm
Location: East Dubuque, Illinois
Has thanked: 1 time
Been thanked: 222 times

Re: maximum number of extent

Postby samb01 » Tue Jun 25, 2013 5:51 pm

OK but what is the difference between Older Type and newer type of dataset ?
samb01
 
Posts: 236
Joined: Mon Nov 16, 2009 7:24 pm
Has thanked: 0 time
Been thanked: 0 time

Re: maximum number of extent

Postby Robert Sample » Tue Jun 25, 2013 6:32 pm

VSAM files I know qualify as "newer" data sets. Up through z/OS 1.7, VSAM data sets were limited to 123 extents per volume and 255 total extents; the updated limit for VSAM is 7257 (123 extents times 59 volumes). I'm not sure about PDSE nor HFS nor ZFS -- I suspect they all might qualify as "newer" data sets but can't research the question right now.
Robert Sample
Global moderator
 
Posts: 3367
Joined: Sat Dec 19, 2009 8:32 pm
Location: East Dubuque, Illinois
Has thanked: 1 time
Been thanked: 222 times

Re: maximum number of extent

Postby steve-myers » Wed Jun 26, 2013 4:39 am

PDS is restricted to one volume, and 65535 tracks. Period. Full stop. End of story.

PDSE is restricted to one volume. There is no limit on data set size on the volume. Period. Full stop. End of story.

I suspect the Topic Starter's problem is he ran out of volumes in the storage group and didn't exceed the maximum number of volumes.
steve-myers
Global moderator
 
Posts: 1886
Joined: Thu Jun 03, 2010 6:21 pm
Has thanked: 4 times
Been thanked: 197 times


Return to JCL

 


  • Related topics
    Replies
    Views
    Last post