- Ok This is one of my buttons
PRI = 1000
SEC = 500
The best practice in todays storage arena, is to allocate the small on Primary
and Large on Secondary
Why - because the primary allocation can take away for the number of secondary
allocations that can be made
Because the Primary allocation can only be obtained once and upto 5
extents to acquire it
But using a small primary and large secondary you provide breathing room for
your dataset
Also, you might want to calculate how much storage you might need and determine
the allocation needed from it
So for this file, I would recommend, Primary = 100 Secondary = 1000. Then
monitor the file for growth. If it looks like it is taking on too many
secondary extents, then reallocate and double or triple the secondary
If it is truly going to be over 4gb - then make the secondary huge
Lizette
> -----Original Message-----
> From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
> Peter
> Sent: Tuesday, April 10, 2018 10:49 AM
> To: [email protected]
> Subject: Dummy question on VSAM multivolume
>
> Hi
>
> I have defined a KSDS with primary 1000 and secondary 500 with the extended
> addressability.
>
> It got created as multivolume with 2 volcount.
>
> Can I alter volume count ?
>
> Peter
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
