samb01 wrote:It's a VSAM ... What is the maximum of extent ?
catalogs are VSAM these days.
I realize English is not your first language, but "What is the maximum of extent" is unintelligible.
Most VSAM usage statistics for catalogs are unreliable, and that appears to be the case here. They are unreliable because catalogs are seldom closed properly. For normal VSAM you look for high allocated RBA and high used RBA, though that's not reliable because high used RBA may not reflect deleted records very well. Here they are identical,
reliable test is to try to define a new catalog entry. If the result is a message about the catalog being full, you have to take it at its word.
Based on the extremely high allocated space for this catalog, I'd guess it's full, but it most likely has severe structural problems. I'd take this to your storage management people. Copying catalogs, especially catalogs with major structural problems, is not a task for a beginner. It's been at roughly 20 years since I did any catalog copying. I really didn't know enough to recover from a major problem then, and it's still true. There were issues I didn't understand then, especially reestablishing alias pointers, and I'd have to relearn that now. Like I said, dump this can of worms ("can of worms" is an idiom in English that usually means a difficult problem) on your storage management people. If you've inherited the storage management job, all I can say is, Good luck!