View previous topic :: View next topic
|
Author |
Message |
upendrasri
Active User
Joined: 28 Sep 2017 Posts: 121 Location: India
|
|
|
|
Hi,
In our environment we have thousands of VSAM files and we have got a requirement from client to identify all
VSAM files that are < 1 GB and used < 10% of allocated size?
We can get details from LISTCAT but i dont know how exactly to get allocated size and used size details?
Here am giving LISTCAT of one of our file..
Code: |
CLUSTER ------- TTSN.ZXC.TPOST
IN-CAT --- USER.MEPZSN.CATALOG
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2018.243
RELEASE----------------2 EXPIRATION------0000.000
SMSDATA
STORAGECLASS ---STANDARD MANAGEMENTCLASS-NOACTION
DATACLASS ------EXTENDED LBACKUP ---0000.000.0000
CA-RECLAIM---------(YES)
EATTR-------------(NULL)
BWO STATUS------00000000 BWO TIMESTAMP---00000 00:00:00.0
BWO---------------(NULL)
RLSDATA
LOG ----------------(NULL) RECOVERY REQUIRED --(NO) FRLOG --------
----(NULL)
VSAM QUIESCED -------(NO) RLS IN USE ---------(NO) LOGREPLICATE--
-----------(NO)
LOGSTREAMID-----------------------------(NULL)
RECOVERY TIMESTAMP LOCAL-----X'0000000000000000'
RECOVERY TIMESTAMP GMT-------X'0000000000000000'
PROTECTION-PSWD-----(NULL) RACF----------------(NO)
ASSOCIATIONS
DATA-----TTSN.ZXC.TPOST.DATA
INDEX----TTSN.ZXC.TPOST.INDEX
DATA ------- TTSN.ZXC.TPOST.DATA
IN-CAT --- USER.MEPZSN.CATALOG
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2018.243
RELEASE----------------2 EXPIRATION------0000.000
ACCOUNT-INFO-----------------------------------(NULL)
PROTECTION-PSWD-----(NULL) RACF----------------(NO)
ASSOCIATIONS
CLUSTER--TTSN.ZXC.TPOST
ATTRIBUTES
KEYLEN----------------20 AVGLRECL-------------512 BUFSPACE------
-----13824 CISIZE--------------6144
RKP--------------------0 MAXLRECL-------------512 EXCPEXIT------
----(NULL) CI/CA----------------120
STRIPE-COUNT-----------1
ACT-DIC-TOKEN----X'4000000A010001F005400702080108FE05FE0DFE0EFE0AFE00000
0000000000000000000'
SHROPTNS(2,3) SPEED UNIQUE NOERASE INDEXED
NOWRITECHK UNORDERED NOREUSE
NONSPANNED COMP-FORMT EXTENDED EXT-ADDR
STATISTICS
REC-TOTAL----------35048 SPLITS-CI--------------0 EXCPS---------
--------23
REC-DELETED------------0 SPLITS-CA--------------0 EXTENTS-------
---------1
REC-INSERTED-----------0 FREESPACE-%CI----------0 SYSTEM-TIMESTA
MP:
REC-UPDATED------------0 FREESPACE-%CA----------0 X'D4DD372
8DD62E66C'
REC-RETRIEVED------35049 FREESPC---------32501760
USER-DATA-SIZE-------------------------------17944576 COMP-USER-DATA
-SIZE---------------------------4218921
ALLOCATION
SPACE-TYPE------CYLINDER HI-A-RBA--------36864000
SPACE-PRI-------------50 HI-U-RBA---------5160960
SPACE-SEC-------------50
VOLUME
VOLSER------------O0N141 PHYREC-SIZE---------6144 HI-A-RBA------
--36864000 EXTENT-NUMBER----------1
DEVTYPE------X'3010200F' PHYRECS/TRK------------8 HI-U-RBA------
---5160960 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'030F0000' LOW-RBA----------------0 TRACKS--------
-------750
HIGH-CCHH----X'0340000E' HIGH-RBA--------36863999
INDEX ------ TTSN.ZXC.TPOST.INDEX
IN-CAT --- USER.MEPZSN.CATALOG
HISTORY
DATASET-OWNER-----(NULL) CREATION--------2018.243
RELEASE----------------2 EXPIRATION------0000.000
PROTECTION-PSWD-----(NULL) RACF----------------(NO)
ASSOCIATIONS
CLUSTER--TTSN.ZXC.TPOST
ATTRIBUTES
KEYLEN----------------20 AVGLRECL---------------0 BUFSPACE------
---------0 CISIZE--------------1536
RKP--------------------0 MAXLRECL------------1529 EXCPEXIT------
----(NULL) CI/CA-----------------25
SHROPTNS(2,3) RECOVERY UNIQUE NOERASE NOWRITECHK
UNORDERED NOREUSE EXTENDED
EXT-ADDR
STATISTICS
REC-TOTAL--------------8 SPLITS-CI--------------0 EXCPS---------
--------42 INDEX:
REC-DELETED------------0 SPLITS-CA--------------0 EXTENTS-------
---------1 LEVELS-----------------2
REC-INSERTED-----------0 FREESPACE-%CI----------0 SYSTEM-TIMESTA
MP: ENTRIES/SECT----------10
REC-UPDATED------------0 FREESPACE-%CA----------0 X'D4DD372
8DD62E66C' SEQ-SET-RBA----------------0
REC-RETRIEVED----------0 FREESPC----------1139712
HI-LEVEL-RBA------------3072
ALLOCATION
SPACE-TYPE------CYLINDER HI-A-RBA---------1152000
SPACE-PRI--------------2 HI-U-RBA-----------12288
SPACE-SEC--------------1
VOLUME
VOLSER------------O0N141 PHYREC-SIZE---------1536 HI-A-RBA------
---1152000 EXTENT-NUMBER----------1
DEVTYPE------X'3010200F' PHYRECS/TRK-----------25 HI-U-RBA------
-----12288 EXTENT-TYPE--------X'00'
VOLFLAG------------PRIME TRACKS/CA--------------1
EXTENTS:
LOW-CCHH-----X'00510000' LOW-RBA----------------0 TRACKS--------
--------30
HIGH-CCHH----X'0052000E' HIGH-RBA---------1151999
|
Thanks. |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
The manual tells you that HI-A-RBA is highest allocated byte and HI-U-RBA is highest used byte. This is a beginner's question -- are you sure you belong on this forum? |
|
Back to top |
|
|
upendrasri
Active User
Joined: 28 Sep 2017 Posts: 121 Location: India
|
|
|
|
Hi Robert,
I am confused with so many different ways of calculating space(verified in different forums). And I dont have proper Idea on how to calculate space of a Vsam dataset. I know may be this is a simple question but wan to get more clarity on it. Thats why I have posted here..
Thanks! |
|
Back to top |
|
|
steve-myers
Active Member
Joined: 30 Nov 2013 Posts: 917 Location: The Universe
|
|
|
|
Allocated space is no trouble. It's right there.
Code: |
ALLOCATION
SPACE-TYPE------CYLINDER HI-A-RBA--------36864000
SPACE-PRI-------------50 HI-U-RBA---------5160960 |
RBA is Relative Byte Address. The numbers are pretty raw and difficult to interpret visually. HI-A-RBA is the high allocated RBA. This data set has 36864000 bytes allocated. It gets more difficult when the space is divided into extents.
Used space is very flaky because of CA and CI splits. These inflate the used space. HI-U-RBA will get you started.
Good luck with your project. |
|
Back to top |
|
|
Nic Clouston
Global Moderator
Joined: 10 May 2007 Posts: 2455 Location: Hampshire, UK
|
|
|
|
I do not know why you posted in Dfsort instead of JCL & VSAM. Probably due to a lack of care over your posting. I hope that lack of care does not extend to your coding and testing!
Moved. |
|
Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009 Posts: 580 Location: London
|
|
|
|
I'd suggest you talk to your Storage Admin's or Capacity Planning people, who can probably do this in a matter of minutes using various solutions.
They'll also be aware how the figures should be presented, because HI-A-RBA needs to include indexes and other overheads. It is the physical allocated space that matters as there may be lots of freespace or part used tracks. |
|
Back to top |
|
|
|