|
View previous topic :: View next topic
|
| Author |
Message |
mrgnndhmk
New User
Joined: 01 Feb 2006
Posts: 51
Location: India
|
|
|
|
I searched the forum about the "Extents" discussion and found a lot. But I could not get the exact answer I am looking for.
The Maximum Extent is 123 and per volume.
The Application is in VSE and VSAM files are managed manually in Catalog & Volumes - File Definitions explicitly mention Catalog Name & Volumes.
The Extents are numbered in sequence even if the file is spread across the volumes.
How can I confirm that the VSAM file is following 123/Volume? Or the file is managed differently here?
I have given a sample file definition and LSTCAT O/P after the file is loaded with the data.
| Code: |
// EXEC IDCAMS,SIZE=256K
DELETE RPCBASE.K.PRIMARY.AND.TARG.BASES CLUSTER -
PURGE -
CATALOG(LCLP.RTL.UCATBS1)
SET MAXCC = 0
DEFINE CLUSTER( -
NAME(RPCBASE.K.PRIMARY.AND.TARG.BASES) -
KEYS(10 0) -
FOR(9999) -
RECORDSIZE(302 302) -
XXL -
SHAREOPTIONS(2)) -
DATA( -
NAME(RPCBASE.K.PRIMARY.AND.TARG.BASES.DATA) -
FREESPACE(2 4) -
CONTROLINTERVALSIZE(20480) -
VOLUMES(BS101L BS102L BS103L BS104L BS105L BS106L -
BS107L BS108L BS109L BS110L BS111L BS112L -
BS113L BS114L BS115L BS116L) -
CYLINDERS(1100 550)) -
INDEX( -
NAME(RPCBASE.K.PRIMARY.AND.TARG.BASES.INDEX) -
CONTROLINTERVALSIZE(1024) -
VOLUMES(BS111L BS116L BS115L BS108L BS107L BS106L
BS105L BS104L BS103L BS102L BS101L BS109L) -
CYLINDERS(10 10)) -
CATALOG(LCLP.RTL.UCATBS1)
IF LASTCC > 0 THEN CANCEL JOB
/*
[u][b]LIST CAT O/P:[/b][/u]
RPCBASE.K.PRIMARY.AND.TARG.BASES (KSDS,CREATED-2013/207 EXPIRES-2099/999 TIME STAMP-2013/208 11:15AM GMT)
2,3 10 0 302 302 18432 1100C0 550C0 2 4 1106152629827803 4389 10937013241816630526 BS114L 99015 16500 99 1
EXLARG 1024I 10C0 10C0 % EXCPS=19502021 BUFFSPACE= 37888 BS114L 115515 8250 2
INDEX LEVELS= 4 BS114L 123765 8250 3
BS114L 132015 8250 4
BS114L 140265 8250 5
BS110L 15 16500 6
BS109L 15 16500 7
.
.
.
.
BS105L 132015 8250 80
BS105L 82515 8250 81
BS105L 90765 8250 82
BS105L 99015 8250 83
BS104L 16515 16500 84
BS104L 41265 8250 85
BS104L 57765 8250 86
BS113L NO ALLOCATION
|
|
|
| Back to top |
|
 |
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
Just when I was going to say we don't see much VSE here...
What DASD do you have that you might expect 123 extents of 1,100 cylinders anyway?
I think you should talk to your technical support and storage mangement people. If they can't help you, I seem to remember finding a couple of useful-looking VSE question sites "out there" a few months ago. Simple with Google. |
|
| Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 580
Location: London
|
|
|
|
Most of the references in this forum are probably for Z/OS VSAM and not relevant to VSE which still uses the old VSAM dataspace concept (yuck!). VSE (now z/VSE), wow, takes me back to the late 70's!
A guick Google throws up the following though:
ftp://ftp.boulder.ibm.com/s390/zos/vse/pdf3/zvse31/doc/iesvoe10.pdf
extract from that....
VSE/VSAM Data Organization
VSE/VSAM Fundamentals Page 17 Stev Glodowski (04/12/2010)
Size Limits: (rc x'1C' "No more available extents")
123 volumes per cluster component (data and index).
16 volumes from default model.
4.3 Giga-byte
4 byte RBA (Relative Byte Address):
4500 – 11000 cylinders on D/T3390 depending on CI-Size and track utilization
Compression can help
'ExtraLargeDataset' or 'XXL' max 286 GB ( No-RBA access )
Clusters are limited to 123 extents per component (Data/Index).
This is normally only a problem if you specify a very small secondary extent.
VSE/VSAM will sub-allocate an extent up to 5 times.
Catalogs, reusable files, and unique files are limited to 16 extents.
Large DASD Support
BIG-DASD supports dasd with up to 10017 cylinders.
FAT-DASD supports dasd with up to 65520 cylinders
Implementation is transparent to existing applications and JCL.
Dasd is flagged in LISTCAT as “BIG-3390” or “FAT-3390”
Automatic for BIG-DASD using FATDASD parm for DEFINE UCAT & SPACE
Allocations converted to CYLINDERS
Minimum data CISIZE increased to 1024 (depending on key size)
BUFSPACE parameter may be increased
Note: RECOVERABLE catalogs are not supported on “large dasd”.
Also worth looking at this IDCAMS manual in the Define Cluster section:
ftp://ftp.boulder.ibm.com/s390/zos/vse/pdf3/zvse31/doc/iesvoe10.pdf |
|
| Back to top |
|
|
|
|
