Page 1 of 1

Avoid extent in ten Huge File

PostPosted: Fri Feb 14, 2020 1:14 pm
by samb01
Hello,

i 'd like to avoid whed if ill ten Huge file (110 000 Cylinders) each one.
They all belon to the same Storage Group.

I use ten job (each job) fill one dataset.

They are guarantee space. It's the resason i'd like to fill then by using only the primary space to get one extent by volume

In the storage group, we have 59 volume. So ti fill each dataset, i need 1870 cylinders in primary space :


//HUGE01    DD DSN=HUGE.DATA.SET01,DISP=(,CATLG,DELETE),
//         DATACLAS=DCKOMP1,                                      
//         SPACE=((CYL,1870),RLSE),VOL=(,,,59),              
//         DCB=(RECFM=VB,LRECL=27994,BLKSIZE=27998)        
 


the dataclass is


Data Set Name Type  . . . . . : EXTENDED                    
  If Extended . . . . . . . . : REQUIRED                    
  Extended Addressability . . : NO                          
  Record Access Bias  . . . . : USER                        
  RMODE31 . . . . . . . . . . :                            
Space Constraint Relief . . . : YES                        
  Reduce Space Up To (%)  . . : 50                          
  Guaranteed Space Reduction  : NO                          
  Dynamic Volume Count  . . . :                            
                                                           
Compaction  . . . . . . . . . : YES                        
Spanned / Nonspanned  . . . . :    
 


My question is :
To avoid extent, may i have to run job one after one : I wait the end of the fisrt job to run the seconde, etc...
But this solution takes time.

If i run the fisrt job, and i wait 5 minutes (for example) to be sure the jobs the primary space in the 59 volumes)
And five minutes later, i run the second, etc...

I prefer this solution, because it doesn't take so much time (i don't have to wait then end of each job).
But with this solution, i'm not sure to avoid more than one extent in each volume.

Thank's for help and sorry my english.

Re: Avoid extent in ten Huge File

PostPosted: Fri Feb 14, 2020 1:30 pm
by enrico-sorichetti
Your english skills are the lesser of Your problems
the worse thing is the sloppy way You posted Your question

i 'd like to avoid whed if ill ten Huge file (110 000 Cylinders) each one.

what in &heaven does it mean ???

help people who spend their time helping You !

Re: Avoid extent in ten Huge File

PostPosted: Fri Feb 14, 2020 2:26 pm
by samb01
Hello, sorry.
I'd like to say :

i 'd like to avoid extent when i fill ten Huge files (110 000 Cylinders) each one :


X.HUGE.G0001V00                                  1650525   99    59
X.HUGE.G0002V00                                  1650525   99    59
X.HUGE.G0003V00                                  1650525   99    59
X.HUGE.G0004V00                                  1650525   99    59
X.HUGE.G0005V00                                  1650525   99    59
X.HUGE.G0006V00                                  1650525   99    59
X.HUGE.G0007V00                                  1650525   99    59
X.HUGE.G0008V00                                  1650525   99    59
X.HUGE.G0009V00                                  1650525   99    59
X.HUGE.G0010V00                                  1650525   99    59
 

Re: Avoid extent in ten Huge File

PostPosted: Fri Feb 14, 2020 8:32 pm
by willy jensen
It has been a while since I looked at it, but perhaps the CONTIG operand of the SPACE parameter helps?

Re: Avoid extent in ten Huge File

PostPosted: Mon Feb 17, 2020 7:37 am
by steve-myers
samb01 wrote:...
//HUGE01    DD DSN=HUGE.DATA.SET01,DISP=(,CATLG,DELETE),
//         DATACLAS=DCKOMP1,
//         SPACE=((CYL,1870),RLSE),VOL=(,,,59),
//         DCB=(RECFM=VB,LRECL=27994,BLKSIZE=27998) 

There are a few issues with the JCL too.
  • You specify a primary allocation but no secondary allocation. What this means is you fill the primary allocation, and then you ABEND because there is no secondary allocation AND it will not attempt to go to an additional volume since there is no secondary allocation.
  • You claim each data set NOT file goes to 110,000 cylinders, but, again, your primary (and since there is no secondary) is slightly less than 110,000 - well, it does not compute.
  • There are syntax issues with your SPACE parameter.
  • To get more than 4369 cylinders on one volume you have to specify DSNTYPE=LARGE, unless that is covered by the DCKOMP1 data class.
  • I'm too lazy to do the arithmetic, but I'm pretty sure you cannot get 110,000 cylinders even in the extended space of a 3390-27 type device. In other words, there is no way you're going to get 110,000 cylinders in one extent on one volume.