Hi Jeff,

In the lines given by Alejandro it is 2 times the same extents on the first RECSZ 512 and on the other RECSZ 1024, so ???
The extents for index are between the 2 extents of DATA

搁别苍é

Le vendredi 26 janvier 2024 à 16:13:27 UTC+1, Jeff Bassett <bassettj@...> a écrit :

Rene, Alejandro

?

While you are BOTH asking relevant questions – frankly – other than a basic understanding – you are IMHO getting down too deep into the weeds

?

There are VOLUMES of documentation on how VSAM and catalogs work – (in the OLD days – we used to have to occasionally dump and ZAP to fix )

I have forgotton so much of my training over the years –

?

There are entire careers been made on CATALOGS and CATALOG structures – and management of same – it is complicated –

There are multiple products that are designed and built to assist with management and maintenance of catalogs - - these products have proven their worth over the years – particularly in larger shops – where there are EXTREME numbers of data sets and LARGER numbers equate to many additional levels and pieces to manage.?

?

?

There are RED books and basic manuals (of course the RED books try to EXPLAIN the basic manuals are simply documentation)

So – for in depth explanations – the Red books are better source – ?(IMHO)

?

If I remember correctly – there is a section in the ABCs of System programming Volume 3 – on Catalogs ?- see this header

·????????
Volume 3: Introduction to DFSMS, data set basics, storage management, hardware and software, catalogs, and DFSMStvs

?

Rene

?

There are TWO different pieces –

The DATA portion and the INDEX

The DATA portion – there are 512 records per track

In the INDEX portion there are 1024 records per track -?

?

Alejandro,

IDCAMS is the tool to manage catalogs

YouMAY BE ABLE – in fact – as was pointed out – to ALTER the existing catalog – or maybe not –

OR ?you EXPORT – by unloading all the data – then re-load – to re-organize the catalog

?

As you have now learned – when you initially allocated the catalog – you specifically specified 10? cyl - - without any secondary allocation – ?this means when it gets full – it can NOT expand - - so – I would suggest – a next step – would be REORG – (unload – build a new larger catalog with the additional values – (including secondary extents) then re-load – the catalog -???

?

-J-

?

Jeff Bassett

Bassettj@...

(301) 424-3362 (office)

(240) 388-7148 Cell

?

Time spent flying? - isNOT deducted from one’s lifespan

?

From: [email protected] <[email protected]>On Behalf Of Rene BRANDT via
Sent: Friday, January 26, 2024 4:46 AM
To: [email protected]
Subject: Re: [H390-MVS] NOT CATLGD 4 | Unable to CATLG PDS under certain qualifier.

?

Hi Jeff,

Why is it PHYSICAL RECSZ 512 on the first and 1024 on the second one ?

搁别苍é

Le vendredi 26 janvier 2024 à 01:07:28 UTC+1, Jeff Bassett <bassettj@...> a écrit :

?

?

Rene,

I think your cut and paste got the same data twice…

?

If you look at the original LISTCAT –

?

The DATA portion consists of TWO internal allocations – total of 72 tracks

One VOLUME is 66 tracks followed by another of 6 tracks –

?

DATA ------- VSAM.CATALOG.BASE.DATA.RECORD

? ?HISTORY

? ? ?OWNER-IDENT-------(NULL) CREATION----------00.000

? ? ?RELEASE----------------2 EXPIRATION--------00.000

? ?ALLOCATION???

? ? ?SPACE-TYPE---------TRACK HI-ALLOC-RBA-----1130496

? ? ?SPACE-PRI-------------72 HI-USED-RBA------1083392????????????????????? <<<<<<<<<<<<<<<<<<<<<<<<<<<<<< TOTAL TRACKS

? ? ?SPACE-SEC--------------0

? ?VOLUME

? ? ?VOLSER------------USRDT0 PHYREC-SIZE----------512 HI-ALLOC-RBA-----1036288 EXTENT-NUMBER----------1

? ? ?DEVTYPE------X'3010200E' PHYRECS/TRK-----------46 HI-USED-RBA--------47104 EXTENT-TYPE--------X'00'

? ? ?VOLFLAG------------PRIME TRACKS/CA--------------3

? ? ?LOW-KEY---------------00

? ? ?HIGH-KEY--------------3F??? <<<<<<<<<<<<<<<<<<<<<<<<END RBA -

? ? ?HI-KEY-RBA----------6656

? ? ?EXTENTS:

? ? ? ?LOW-CCHH-----X'00010000' LOW-RBA----------------0 TRACKS----------------66???????????????????????? <<<<<< this is 66 tracks

? ? ? ?HIGH-CCHH----X'00050005' HIGH-RBA---------1036287

? ?VOLUME

? ? ?VOLSER------------USRDT0 PHYREC-SIZE----------512 HI-ALLOC-RBA-----1130496 EXTENT-NUMBER----------1

? ? ?DEVTYPE------X'3010200E' PHYRECS/TRK-----------46 HI-USED-RBA------1083392 EXTENT-TYPE--------X'00'

? ? ?VOLFLAG------------PRIME TRACKS/CA--------------3

? ? ?LOW-KEY---------------40??? <<<<<<<<<<<<<<<<<<<<<<<<<<NEXT BEGIN RBA

? ? ?HIGH-KEY--------------FF

? ? ?HI-KEY-RBA-------1036288

? ? ?EXTENTS:

? ? ? ?LOW-CCHH-----X'00050009' LOW-RBA----------1036288 TRACKS-----------------6?????????????????????????? <<<<<<<<<<this is 6 tracks

? ? ? ?HIGH-CCHH----X'0005000E' HIGH-RBA---------1130495

?

?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????TOTAL OF 72 TRACKS for the DATA PORTION

The ORIGINAL allocation was 5CYL - - or 80 TRACKS – (remember 3380 is 15 tracks per cyl)

Then there is the index….. as well – it all comes together -

?

-J-

?

Jeff Bassett

Bassettj@...

(301) 424-3362 (office)

(240) 388-7148 Cell

?

Time spent flying? - isNOTdeducted from one’s lifespan

?

From:[email protected] <[email protected]>On Behalf OfRene BRANDT via
Sent: Thursday, January 25, 2024 6:44 PM
To: [email protected]
Subject: Re: [H390-MVS] NOT CATLGD 4 | Unable to CATLG PDS under certain qualifier.

?

Hi,

I found something strange perhaps someone could explain me :
Why we see 2 times the sale allocation with different recsize ?


VOLUME
VOLSER------------USRDT0 PHYREC-SIZE----------512 HI-ALLOC-RBA-----1036288 EXTENT-NUMBER----------1
EXTENTS:
LOW-CCHH-----X'00010000' LOW-RBA----------------0 TRACKS----------------66
HIGH-CCHH----X'00050005' HIGH-RBA---------1036287
VOLUME
VOLSER------------USRDT0 PHYREC-SIZE----------512 HI-ALLOC-RBA-----1130496 EXTENT-NUMBER----------1
EXTENTS:
LOW-CCHH-----X'00050009' LOW-RBA----------1036288 TRACKS-----------------6
HIGH-CCHH----X'0005000E' HIGH-RBA---------1130495
and
VOLUME
VOLSER------------USRDT0 PHYREC-SIZE---------1024 HI-ALLOC-RBA------117760 EXTENT-NUMBER----------1
EXTENTS:
LOW-CCHH-----X'00010000' LOW-RBA------------95232 TRACKS----------------66
HIGH-CCHH----X'00050005' HIGH-RBA----------117759
VOLUME
VOLSER------------USRDT0 PHYREC-SIZE---------1024 HI-ALLOC-RBA------119808 EXTENT-NUMBER----------1
EXTENTS:
LOW-CCHH-----X'00050009' LOW-RBA-----------117760 TRACKS-----------------6
HIGH-CCHH----X'0005000E' HIGH-RBA----------119807

Le jeudi 25 janvier 2024 à 17:39:17 UTC+1, Alejandro olivan Alvarez <alejandro.olivan.alvarez@...> a écrit :

?

?

Hi folks!

I've been doing some research on the catalog subject, but my very superficial knowledge on VSAM matters (struggling to go through Demistifying VSAM redBook) prevents me to fully understand what my eyes are probably seeing. Anyways, after some reading , I ended up using CLIST TSO command to get on screen what I already had on print via JCL (fun!).
Either through TSO or JCL, CLIST ALL ENT('UCUSRDT0') CAT('UCUSRDT0') prints a ton of interesting information, specially the allocation, but I miserably fail on interpreting it...it is overwheelming (will dump it bellow)... although it allows me to do some especulations.

A list of the catalog entries name ends up with a brief summary after the big purge:

THE NUMBER OF ENTRIES PROCESSED WAS:

?AIX -------------------0

?ALIAS -----------------0

?CLUSTER ---------------1

?DATA ------------------1

?GDG -------------------0

?INDEX -----------------1

?NONVSAM --------------48

?PAGESPACE -------------0

?PATH ------------------0

?SPACE -----------------1

?USERCATALOG -----------0

?TOTAL ----------------52

While looking ath the allocation on the same catalog yelds the following:

CLUSTER ------- UCUSRDT0

? ? ?HISTORY

? ? ? ?OWNER-IDENT-------(NULL) CREATION----------23.258

? ? ? ?RELEASE----------------2 EXPIRATION--------00.000

??

?DATA ------- VSAM.CATALOG.BASE.DATA.RECORD

? ?HISTORY

? ? ?OWNER-IDENT-------(NULL) CREATION----------00.000

? ? ?RELEASE----------------2 EXPIRATION--------00.000

? ?ALLOCATION

? ? ?SPACE-TYPE---------TRACK HI-ALLOC-RBA-----1130496

? ? ?SPACE-PRI-------------72 HI-USED-RBA------1083392

? ? ?SPACE-SEC--------------0

? ?VOLUME

? ? ?VOLSER------------USRDT0 PHYREC-SIZE----------512 HI-ALLOC-RBA-----1036288 EXTENT-NUMBER----------1

? ? ?DEVTYPE------X'3010200E' PHYRECS/TRK-----------46 HI-USED-RBA--------47104 EXTENT-TYPE--------X'00'

? ? ?VOLFLAG------------PRIME TRACKS/CA--------------3

? ? ?LOW-KEY---------------00

? ? ?HIGH-KEY--------------3F

? ? ?HI-KEY-RBA----------6656

? ? ?EXTENTS:

? ? ? ?LOW-CCHH-----X'00010000' LOW-RBA----------------0 TRACKS----------------66

? ? ? ?HIGH-CCHH----X'00050005' HIGH-RBA---------1036287

? ?VOLUME

? ? ?VOLSER------------USRDT0 PHYREC-SIZE----------512 HI-ALLOC-RBA-----1130496 EXTENT-NUMBER----------1

? ? ?DEVTYPE------X'3010200E' PHYRECS/TRK-----------46 HI-USED-RBA------1083392 EXTENT-TYPE--------X'00'

? ? ?VOLFLAG------------PRIME TRACKS/CA--------------3

? ? ?LOW-KEY---------------40

? ? ?HIGH-KEY--------------FF

? ? ?HI-KEY-RBA-------1036288

? ? ?EXTENTS:

? ? ? ?LOW-CCHH-----X'00050009' LOW-RBA----------1036288 TRACKS-----------------6

? ? ? ?HIGH-CCHH----X'0005000E' HIGH-RBA---------1130495

? ? ? ?

?INDEX ------ VSAM.CATALOG.BASE.INDEX.RECORD

? ?HISTORY

? ? ?OWNER-IDENT-------(NULL) CREATION----------00.000

? ? ?RELEASE----------------2 EXPIRATION--------00.000

? ?ALLOCATION

? ? ?SPACE-TYPE---------TRACK HI-ALLOC-RBA------119808

? ? ?SPACE-PRI--------------3 HI-USED-RBA-------118784

? ? ?SPACE-SEC--------------3

? ?VOLUME

? ? ?VOLSER------------USRDT0 PHYREC-SIZE---------1024 HI-ALLOC-RBA-------95232 EXTENT-NUMBER----------1

? ? ?DEVTYPE------X'3010200E' PHYRECS/TRK-----------31 HI-USED-RBA---------1024 EXTENT-TYPE--------X'00'

? ? ?VOLFLAG------------PRIME TRACKS/CA--------------1

? ? ?EXTENTS:

? ? ? ?LOW-CCHH-----X'00050006' LOW-RBA----------------0 TRACKS-----------------3

? ? ? ?HIGH-CCHH----X'00050008' HIGH-RBA-----------95231

? ?VOLUME

? ? ?VOLSER------------USRDT0 PHYREC-SIZE---------1024 HI-ALLOC-RBA------117760 EXTENT-NUMBER----------1

? ? ?DEVTYPE------X'3010200E' PHYRECS/TRK-----------31 HI-USED-RBA--------96256 EXTENT-TYPE--------X'80'

? ? ?VOLFLAG------------PRIME TRACKS/CA--------------3

? ? ?LOW-KEY---------------00

? ? ?HIGH-KEY--------------3F

? ? ?EXTENTS:

? ? ? ?LOW-CCHH-----X'00010000' LOW-RBA------------95232 TRACKS----------------66

? ? ? ?HIGH-CCHH----X'00050005' HIGH-RBA----------117759

? ?VOLUME

? ? ?VOLSER------------USRDT0 PHYREC-SIZE---------1024 HI-ALLOC-RBA------119808 EXTENT-NUMBER----------1

? ? ?DEVTYPE------X'3010200E' PHYRECS/TRK-----------31 HI-USED-RBA-------118784 EXTENT-TYPE--------X'80'

? ? ?VOLFLAG------------PRIME TRACKS/CA--------------3

? ? ?LOW-KEY---------------40

? ? ?HIGH-KEY--------------FF

? ? ?EXTENTS:

? ? ? ?LOW-CCHH-----X'00050009' LOW-RBA-----------117760 TRACKS-----------------6

? ? ? ?HIGH-CCHH----X'0005000E' HIGH-RBA----------119807

- Those HI-ALLOC-RBA and HI-USED-RBA look often too close for comfort. Specially after a so significant decrease on the number of entries. I feel that I miss more underlying knowledge on the VSAM stuff to uderstand that data.
- I don't think the volume is full, I have to recall on the best way to get a printout of volume usage, but it is a 3380 and the amount of data held there can't sum that much bytes... still, I have to refresh
? on the way to get precisse info on that.
- Much like datasets, knowing how to scale a catalog, and also how to define its ability to expand is critical... a very interesting topic! but docs are hard to understand lacking preliminar knowledge.??
? Also much possibly, all this is going to be a good chance to learn how to perform a catalog migration.
- At least, I conclude that the default/vanilla 5 cyl usercatalog I created is falling short to host a reasonable amount of datasets for automatically provided sample data.?

Regarding my data gahering scripts:

- Output on job failure appeared to me consistent with that of yesterday... but i'm looking forward to catch a new failing job to compare outputs and share.
- I was holding 30 day data, of 11 sources of daily sample records (parsed linux log lines of some services), now i set it to 7, where the job itself took care of?
? deleting and uncataloging?the last dataset. The catalog now is pretty much printable, even at detail, with less than 100 entries in total.
? Number of records on datasets is far from massive, usually less than 100 records... no big data here... that's why I don't believe a whoping 3380 could be full.
- I don't create members on a fixed dataset, but rather, new datasets with few members are created (and wiped) daily.

Looking at examples such the one found at??makes me feel I need to further understand what happens under the hood as entries are written and deleted on the catalog.
??
Cheers!

?

Hi Jeff,

Why is it PHYSICAL RECSZ 512 on the first and 1024 on the second one ?

搁别苍é

Le vendredi 26 janvier 2024 à 01:07:28 UTC+1, Jeff Bassett <bassettj@...> a écrit :

Rene,

I think your cut and paste got the same data twice…

?

If you look at the original LISTCAT –

?

The DATA portion consists of TWO internal allocations – total of 72 tracks

One VOLUME is 66 tracks followed by another of 6 tracks –

?

DATA ------- VSAM.CATALOG.BASE.DATA.RECORD

? ?HISTORY

? ? ?OWNER-IDENT-------(NULL) CREATION----------00.000

? ? ?RELEASE----------------2 EXPIRATION--------00.000

? ?ALLOCATION???

? ? ?SPACE-TYPE---------TRACK HI-ALLOC-RBA-----1130496

? ? ?SPACE-PRI-------------72 HI-USED-RBA------1083392????????????????????? <<<<<<<<<<<<<<<<<<<<<<<<<<<<<< TOTAL TRACKS

? ? ?SPACE-SEC--------------0

? ?VOLUME

? ? ?VOLSER------------USRDT0 PHYREC-SIZE----------512 HI-ALLOC-RBA-----1036288 EXTENT-NUMBER----------1

? ? ?DEVTYPE------X'3010200E' PHYRECS/TRK-----------46 HI-USED-RBA--------47104 EXTENT-TYPE--------X'00'

? ? ?VOLFLAG------------PRIME TRACKS/CA--------------3

? ? ?LOW-KEY---------------00

? ? ?HIGH-KEY--------------3F??? <<<<<<<<<<<<<<<<<<<<<<<<END RBA -

? ? ?HI-KEY-RBA----------6656

? ? ?EXTENTS:

? ? ? ?LOW-CCHH-----X'00010000' LOW-RBA----------------0 TRACKS----------------66???????????????????????? <<<<<< this is 66 tracks

? ? ? ?HIGH-CCHH----X'00050005' HIGH-RBA---------1036287

? ?VOLUME

? ? ?VOLSER------------USRDT0 PHYREC-SIZE----------512 HI-ALLOC-RBA-----1130496 EXTENT-NUMBER----------1

? ? ?DEVTYPE------X'3010200E' PHYRECS/TRK-----------46 HI-USED-RBA------1083392 EXTENT-TYPE--------X'00'

? ? ?VOLFLAG------------PRIME TRACKS/CA--------------3

? ? ?LOW-KEY---------------40??? <<<<<<<<<<<<<<<<<<<<<<<<<<NEXT BEGIN RBA

? ? ?HIGH-KEY--------------FF

? ? ?HI-KEY-RBA-------1036288

? ? ?EXTENTS:

? ? ? ?LOW-CCHH-----X'00050009' LOW-RBA----------1036288 TRACKS-----------------6?????????????????????????? <<<<<<<<<<this is 6 tracks

? ? ? ?HIGH-CCHH----X'0005000E' HIGH-RBA---------1130495

?

?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????TOTAL OF 72 TRACKS for the DATA PORTION

The ORIGINAL allocation was 5CYL - - or 80 TRACKS – (remember 3380 is 15 tracks per cyl)

Then there is the index….. as well – it all comes together -

?

-J-

?

Jeff Bassett

Bassettj@...

(301) 424-3362 (office)

(240) 388-7148 Cell

?

Time spent flying? - isNOT deducted from one’s lifespan

?

From: [email protected] <[email protected]>On Behalf Of Rene BRANDT via
Sent: Thursday, January 25, 2024 6:44 PM
To: [email protected]
Subject: Re: [H390-MVS] NOT CATLGD 4 | Unable to CATLG PDS under certain qualifier.

?

Hi,

I found something strange perhaps someone could explain me :
Why we see 2 times the sale allocation with different recsize ?


VOLUME
VOLSER------------USRDT0 PHYREC-SIZE----------512 HI-ALLOC-RBA-----1036288 EXTENT-NUMBER----------1
EXTENTS:
LOW-CCHH-----X'00010000' LOW-RBA----------------0 TRACKS----------------66
HIGH-CCHH----X'00050005' HIGH-RBA---------1036287
VOLUME
VOLSER------------USRDT0 PHYREC-SIZE----------512 HI-ALLOC-RBA-----1130496 EXTENT-NUMBER----------1
EXTENTS:
LOW-CCHH-----X'00050009' LOW-RBA----------1036288 TRACKS-----------------6
HIGH-CCHH----X'0005000E' HIGH-RBA---------1130495
and
VOLUME
VOLSER------------USRDT0 PHYREC-SIZE---------1024 HI-ALLOC-RBA------117760 EXTENT-NUMBER----------1
EXTENTS:
LOW-CCHH-----X'00010000' LOW-RBA------------95232 TRACKS----------------66
HIGH-CCHH----X'00050005' HIGH-RBA----------117759
VOLUME
VOLSER------------USRDT0 PHYREC-SIZE---------1024 HI-ALLOC-RBA------119808 EXTENT-NUMBER----------1
EXTENTS:
LOW-CCHH-----X'00050009' LOW-RBA-----------117760 TRACKS-----------------6
HIGH-CCHH----X'0005000E' HIGH-RBA----------119807

Le jeudi 25 janvier 2024 à 17:39:17 UTC+1, Alejandro olivan Alvarez <alejandro.olivan.alvarez@...> a écrit :

?

?

Hi folks!

I've been doing some research on the catalog subject, but my very superficial knowledge on VSAM matters (struggling to go through Demistifying VSAM redBook) prevents me to fully understand what my eyes are probably seeing. Anyways, after some reading , I ended up using CLIST TSO command to get on screen what I already had on print via JCL (fun!).
Either through TSO or JCL, CLIST ALL ENT('UCUSRDT0') CAT('UCUSRDT0') prints a ton of interesting information, specially the allocation, but I miserably fail on interpreting it...it is overwheelming (will dump it bellow)... although it allows me to do some especulations.

A list of the catalog entries name ends up with a brief summary after the big purge:

THE NUMBER OF ENTRIES PROCESSED WAS:

?AIX -------------------0

?ALIAS -----------------0

?CLUSTER ---------------1

?DATA ------------------1

?GDG -------------------0

?INDEX -----------------1

?NONVSAM --------------48

?PAGESPACE -------------0

?PATH ------------------0

?SPACE -----------------1

?USERCATALOG -----------0

?TOTAL ----------------52

While looking ath the allocation on the same catalog yelds the following:

CLUSTER ------- UCUSRDT0

? ? ?HISTORY

? ? ? ?OWNER-IDENT-------(NULL) CREATION----------23.258

? ? ? ?RELEASE----------------2 EXPIRATION--------00.000

??

?DATA ------- VSAM.CATALOG.BASE.DATA.RECORD

? ?HISTORY

? ? ?OWNER-IDENT-------(NULL) CREATION----------00.000

? ? ?RELEASE----------------2 EXPIRATION--------00.000

? ?ALLOCATION

? ? ?SPACE-TYPE---------TRACK HI-ALLOC-RBA-----1130496

? ? ?SPACE-PRI-------------72 HI-USED-RBA------1083392

? ? ?SPACE-SEC--------------0

? ?VOLUME

? ? ?VOLSER------------USRDT0 PHYREC-SIZE----------512 HI-ALLOC-RBA-----1036288 EXTENT-NUMBER----------1

? ? ?DEVTYPE------X'3010200E' PHYRECS/TRK-----------46 HI-USED-RBA--------47104 EXTENT-TYPE--------X'00'

? ? ?VOLFLAG------------PRIME TRACKS/CA--------------3

? ? ?LOW-KEY---------------00

? ? ?HIGH-KEY--------------3F

? ? ?HI-KEY-RBA----------6656

? ? ?EXTENTS:

? ? ? ?LOW-CCHH-----X'00010000' LOW-RBA----------------0 TRACKS----------------66

? ? ? ?HIGH-CCHH----X'00050005' HIGH-RBA---------1036287

? ?VOLUME

? ? ?VOLSER------------USRDT0 PHYREC-SIZE----------512 HI-ALLOC-RBA-----1130496 EXTENT-NUMBER----------1

? ? ?DEVTYPE------X'3010200E' PHYRECS/TRK-----------46 HI-USED-RBA------1083392 EXTENT-TYPE--------X'00'

? ? ?VOLFLAG------------PRIME TRACKS/CA--------------3

? ? ?LOW-KEY---------------40

? ? ?HIGH-KEY--------------FF

? ? ?HI-KEY-RBA-------1036288

? ? ?EXTENTS:

? ? ? ?LOW-CCHH-----X'00050009' LOW-RBA----------1036288 TRACKS-----------------6

? ? ? ?HIGH-CCHH----X'0005000E' HIGH-RBA---------1130495

? ? ? ?

?INDEX ------ VSAM.CATALOG.BASE.INDEX.RECORD

? ?HISTORY

? ? ?OWNER-IDENT-------(NULL) CREATION----------00.000

? ? ?RELEASE----------------2 EXPIRATION--------00.000

? ?ALLOCATION

? ? ?SPACE-TYPE---------TRACK HI-ALLOC-RBA------119808

? ? ?SPACE-PRI--------------3 HI-USED-RBA-------118784

? ? ?SPACE-SEC--------------3

? ?VOLUME

? ? ?VOLSER------------USRDT0 PHYREC-SIZE---------1024 HI-ALLOC-RBA-------95232 EXTENT-NUMBER----------1

? ? ?DEVTYPE------X'3010200E' PHYRECS/TRK-----------31 HI-USED-RBA---------1024 EXTENT-TYPE--------X'00'

? ? ?VOLFLAG------------PRIME TRACKS/CA--------------1

? ? ?EXTENTS:

? ? ? ?LOW-CCHH-----X'00050006' LOW-RBA----------------0 TRACKS-----------------3

? ? ? ?HIGH-CCHH----X'00050008' HIGH-RBA-----------95231

? ?VOLUME

? ? ?VOLSER------------USRDT0 PHYREC-SIZE---------1024 HI-ALLOC-RBA------117760 EXTENT-NUMBER----------1

? ? ?DEVTYPE------X'3010200E' PHYRECS/TRK-----------31 HI-USED-RBA--------96256 EXTENT-TYPE--------X'80'

? ? ?VOLFLAG------------PRIME TRACKS/CA--------------3

? ? ?LOW-KEY---------------00

? ? ?HIGH-KEY--------------3F

? ? ?EXTENTS:

? ? ? ?LOW-CCHH-----X'00010000' LOW-RBA------------95232 TRACKS----------------66

? ? ? ?HIGH-CCHH----X'00050005' HIGH-RBA----------117759

? ?VOLUME

? ? ?VOLSER------------USRDT0 PHYREC-SIZE---------1024 HI-ALLOC-RBA------119808 EXTENT-NUMBER----------1

? ? ?DEVTYPE------X'3010200E' PHYRECS/TRK-----------31 HI-USED-RBA-------118784 EXTENT-TYPE--------X'80'

? ? ?VOLFLAG------------PRIME TRACKS/CA--------------3

? ? ?LOW-KEY---------------40

? ? ?HIGH-KEY--------------FF

? ? ?EXTENTS:

? ? ? ?LOW-CCHH-----X'00050009' LOW-RBA-----------117760 TRACKS-----------------6

? ? ? ?HIGH-CCHH----X'0005000E' HIGH-RBA----------119807

- Those HI-ALLOC-RBA and HI-USED-RBA look often too close for comfort. Specially after a so significant decrease on the number of entries. I feel that I miss more underlying knowledge on the VSAM stuff to uderstand that data.
- I don't think the volume is full, I have to recall on the best way to get a printout of volume usage, but it is a 3380 and the amount of data held there can't sum that much bytes... still, I have to refresh
? on the way to get precisse info on that.
- Much like datasets, knowing how to scale a catalog, and also how to define its ability to expand is critical... a very interesting topic! but docs are hard to understand lacking preliminar knowledge.??
? Also much possibly, all this is going to be a good chance to learn how to perform a catalog migration.
- At least, I conclude that the default/vanilla 5 cyl usercatalog I created is falling short to host a reasonable amount of datasets for automatically provided sample data.?

Regarding my data gahering scripts:

- Output on job failure appeared to me consistent with that of yesterday... but i'm looking forward to catch a new failing job to compare outputs and share.
- I was holding 30 day data, of 11 sources of daily sample records (parsed linux log lines of some services), now i set it to 7, where the job itself took care of?
? deleting and uncataloging?the last dataset. The catalog now is pretty much printable, even at detail, with less than 100 entries in total.
? Number of records on datasets is far from massive, usually less than 100 records... no big data here... that's why I don't believe a whoping 3380 could be full.
- I don't create members on a fixed dataset, but rather, new datasets with few members are created (and wiped) daily.

Looking at examples such the one found at??makes me feel I need to further understand what happens under the hood as entries are written and deleted on the catalog.
??
Cheers!

?