Subject: RE: INSUFFICIENT SPACE IN CATALOG
RJacobson@decare.com
Date: Fri Aug 19 2011 - 10:23:45 EDT
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
"Mohammed Imam"
<mimam@co.cumberl
and.nc.us> To
Sent by: "VSE Discussion List"
owner-vse-l@Lehig <vse-l@Lehigh.EDU>
h.EDU cc
Subject
08/18/2011 04:51 RE: INSUFFICIENT SPACE IN CATALOG
PM
Please respond to
vse-l@Lehigh.EDU
Hi Bob,
Let me understand it right.
Isn't it that the catalog creates the catalog dataspace on each volume
that is being subsequently added to the catalog?
If this is not right, adding space/volume to catalog won't do any good
if there is not space available on the base volume of the catalog.
Thanks,
Mohammed A. Imam
-----Original Message-----
From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf
Of RJacobson@decare.com
Sent: Thursday, August 18, 2011 5:33 PM
To: VSE Discussion List
Subject: RE: INSUFFICIENT SPACE IN CATALOG
According to your LISTCAT, the catalog itself is defined on volume
ZISC1D,
but this volume has no free space at all. Free up some space on this
volume and then retry defining the files on ZISC3E.
Bob Jacobson
(651) 994-5329
"Mohammed Imam"
<mimam@co.cumberl
and.nc.us>
To
Sent by: "VSE Discussion List"
owner-vse-l@Lehig <vse-l@Lehigh.EDU>
h.EDU
cc
Subject
08/18/2011 04:19 RE: INSUFFICIENT SPACE IN CATALOG
PM
Please respond to
vse-l@Lehigh.EDU
Dave,
I think the DATASPACE gets created implicitly if not mentioned while
creating the catalog.
I've attached the last part of LISTCAT which reflects the fact that
first 3 volumes ZISC1D, ZISC1E and ZISC1F dedicated to catalog FINTST
did not have any issue like the one I am having today. It is only the
last volume ZISC3E is having this issue.
Mohammed A. Imam
-----Original Message-----
From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf
Of David Stuart
Sent: Thursday, August 18, 2011 4:51 PM
To: VSE Discussion List
Subject: RE: INSUFFICIENT SPACE IN CATALOG
Mohammed,
You didn't define any DATA space within your catalog.
According to the VSE/VSAM 6.4 Commands Manual, SC33-6731-00, Page 174:
DATA (options) - specifies attributes of the data component of the
catalog. The allocation of space for the data and index components of
the user catalog is discussed in "How Data Space is assigned to a
Catalog" on page 19. ...
And then:
Note: If DATA allocation parameters are not coded, the space specified
at the user catalog level is available to contain catalog entries only.
The total amount of space specified through DATA and INDEX parameters
can not be greater than that specified at the USERCATALOG level.
What all this tell me is that there is little, in any, room in your
catalog for the actual data contained in the file(s), since you didn't
specify the DATA option when you defined your Catalog.
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
David.Stuart@ventura.org
>>> "Mohammed Imam" <mimam@co.cumberland.nc.us> 8/18/2011 1:36 PM >>>
Here it is:
DEFINE UCAT ( DEDICATE -
NAME ( FINTST ) -
VOLUMES ( ZISC1D ) )
Mohammed A. Imam
-----Original Message-----
From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf
Of David Stuart
Sent: Thursday, August 18, 2011 4:33 PM
To: VSE Discussion List
Subject: RE: INSUFFICIENT SPACE IN CATALOG
Mohammed,
That's the definition for the Space owned by the catalog, but not for
the catalog file, itself. Your Catalog definition job should also have
some lines that look something like this:
DEDICATE -
VOL(T82CB2) -
FOR (9999)) -
DATA(TRACKS(200 200))
That actually defines the space for the KSDS file that contains all the
file definitions, space allocations, etc., for files residing in the
Catalog.
Dave
Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
David.Stuart@ventura.org
>>> "Mohammed Imam" <mimam@co.cumberland.nc.us> 8/18/2011 1:25 PM >>>
It is a DEDICATEd volume with USECLASS is 0.
DEFINE SPACE ( DEDICATE -
VOLUMES ( ZISC3E ) -
CLASS (0) )
All other volumes defined the same way are not complaining in this
manner.
From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf
Of Kevin Corkery
Sent: Thursday, August 18, 2011 4:20 PM
To: VSE Discussion List
Subject: RE: INSUFFICIENT SPACE IN CATALOG
Can you post the definition stream for the catalog? You might have
allocated all the space to the actual catalog dataset (I have seen this
done before). Also, you could have defined a USECLASS for the space
which is not the same a the default USECLASS.
From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf
Of Mohammed Imam
Sent: Thursday, August 18, 2011 3:51 PM
To: VSE Discussion List
Subject: INSUFFICIENT SPACE IN CATALOG
Hi,
Can someone solve the mystery here, it may be easy for you all:
I have only 2 files on this volume occupying only 334 tracks. This
volume still have 49735 tracks available FREE space and I am not able to
define any file on it with the message "IDC3017I INSUFFICIENT SPACE IN
CATALOG".
This volume has DEDICATEd space for this catalog.
// JOB SA1 DATE
08/18/2011, CLOCK 15/40/26
// OPTION LOG,NODUMP
// DLBL IJSYSUC,'FINTST',,VSAM
// DLBL INPUTF,'AFN2.TEMP.INPUTFX',,VSAM,CAT=FINTST
// EXEC IDCAMS,SIZE=AUTO
1S54I PHASE IDCAMS IS TO BE FETCHED FROM IJSYSRS.SYSLIB
IDCAMS SYSTEM SERVICES TIME:
15:40:26 08/18/2011 PAGE 1
DEL AFN2.TEMP.INPUTFX CAT(FINTST) PURGE
IDC3012I ENTRY AFN2.TEMP.INPUTFX NOT FOUND
IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLCG-6
IDC0551I **ENTRY AFN2.TEMP.INPUTFX NOT DELETED
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8
DEF CL( NAME(AFN2.TEMP.INPUTFX) RECSZ(343 343) -
TRK(10 2) NIXD SHR(1 3) VOL(ZISC3E) SPEED) CAT(FINTST)
IDC3017I INSUFFICIENT SPACE IN CATALOG
IDC3009I ** VSAM CATALOG RETURN CODE IS 20 - REASON CODE IS IGG0CLCG-28
IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12
IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 12
1S55I LAST RETURN CODE WAS 0012
EOJ SA1 MAX.RETURN CODE=0012 DATE
08/18/2011, CLOCK 15/40/26, DURATION 00/00/00
Thanks,
Mohammed A. Imam
County of Cumberland, NC
(910) 678-7680.
All correspondence to and from this address may be subject to the N.C.
Public Records Law and may be disclosed to third parties.
All correspondence to and from this address may be subject to the N.C.
Public Records Law and may be disclosed to third parties.
All correspondence to and from this address may be subject to the N.C.
Public Records Law and may be disclosed to third parties.
All correspondence to and from this address may be subject to the N.C.
Public Records Law and may be disclosed to third parties.
[attachment "Listcat FINTST.txt" deleted by Robert Jacobson/Decare]
All correspondence to and from this address may be subject to the N.C.
Public Records Law and may be disclosed to third parties.
This archive was generated by hypermail 2b25 : Wed Aug 31 2011 - 23:50:11 EDT