Subject: RE: INSUFFICIENT SPACE IN CATALOG
From: Kevin Corkery (kcorkery@live.com)
Date: Fri Aug 19 2011 - 12:13:04 EDT
Bob ...
Good suggestion to move one of the files residing on the catalog volume so
that the catalog can expand. I think that eventually the catalog will need
to be completely rebuilt, especially if only the minimal default catalog is
built. I too recommend a private catalog dataspace, i.e. I don't use
DEDICATE when defining my catalog space and I make the space CLASS(7) to
help prevent other object from being defined within that space. I also
define the catalog space sufficiently large to permit space acquisition for
the catalog dataset; I then monitor the extensions as an indication of the
need for catalog maintenance.
Kevin P Corkery
Independent Consultant
Voorhees, New Jersey
-----Original Message-----
From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf Of
RJacobson@decare.com
Sent: Friday, August 19, 2011 10:24 AM
To: VSE Discussion List
Subject: RE: INSUFFICIENT SPACE IN CATALOG
I think this discussion suffers from ambiguity in the use of the term
"catalog". For purposes of this answer, I am going to use "catalog" to
refer to just the KSDS file that VSAM creates within the data space that is
managed by the catalog. I am specifically NOT going to use "catalog" to
refer to all the data space managed by a catalog.
When a VSAM catalog is defined, it can be done in a variety of ways. I
happen to prefer to give a catalog a separate data space that can only be
used by the catalog file itself. This data space has a separate VTOC entry
from all other data spaces managed by that catalog.
>From the LISTCAT that you provided it is clear that you have done it
>the
other way. That is, when you defined your catalog as a file that exists
within a larger data space. Therefore, it competes for space with other
VSAM files that exist in that data space. Your LISTCAT shows that the data
space on volume ZISC1D is completely allocated. There is not even one free
track left. Therefore, when you went to define some more files in any of
the data spaces managed by the catalog, VSAM found that it had no free
records in the catalog and tried to acquire more space from the data space
on ZISC1D to be able to accommodate the new file definitions. Because the
data space in which the catalog resides had no free space either, you got
the error message that is the subject line of this thread.
The solution is still to move some files off ZISC1D to some other volumes
with space managed by the catalog.
BTW, in your catalog definition, which I have reproduced below, you do not
specify any size information for the catalog itself, just that VSAM is to
grab all the free space on the volume and build a catalog within that data
space. According to the VSE/VSAM Commands (SC33-8315-00), page 19, VSAM
will respond to this type of definition by creating a MINIMUM size catalog
within the data space. You may want to read the entire "How Data Space is
Assigned to a Catalog" in this book. It is only about 4 pages and contains
numerous examples.
DEFINE UCAT ( DEDICATE -
NAME ( FINTST ) -
VOLUMES ( ZISC1D ) )
Bob Jacobson
(651) 994-5329
This archive was generated by hypermail 2b25 : Wed Aug 31 2011 - 23:50:11 EDT