Re: KSDS insert failed with out of space
Maybe the new record being added causes a CI (control interval) split and there is no free CIs in the CA (control area) causing a CA split which would possibly try to add a new extent to the file and there is no more space in the volume for the new extent. So you get an out of space condition in the volume. Also, maybe you do not have specified free CIs in a CA. On 1/18/08, Johnny Luo [EMAIL PROTECTED] wrote: Hi, I encountered a strange problem with a KSDS data set. At this time, I only have some description of the problem from my colleague. Since it's so urgent, I would like to get some hints before I get more detailed info. (Sorry for that, I never did things like this before. But it's urgent..) According to the description, an out of space error occurred while inserting a record from within CICS. It's a KSDS reproed from a PS data set. You can add records to the end of those 'old' records and after that you can insert records into the new block of records. However, if you try to insert a record into the existing block, you get an 'out of space' error. Anyone give me some advices? Thanks. Johnny -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- I am as you, in you, for you. One as you in all, as all, forever. My call is your call. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: KSDS insert failed with out of space
-Original Message- From: IBM Mainframe Discussion List On Behalf Of Johnny Luo Thanks for all the kind replies.. Space on the volumes should not be a problem. They have checked the storage group and space allocation. However, I missed to mention one info. Yes, they didn't specify any free CIs. Is this a problem? I mean, even I don't specify free CIs in a CA, CA-split can still happen. Right? Correct. Specifying freespace only postpones the CI and CA splits, and depending on the key ranges of inserted records, may even leave the KSDS with wasted space (i.e., space that is never subsequently needed or used). -jc- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: KSDS insert failed with out of space
Yes if the index does not have secondary extents I would give it secondary extents and think it may fix your problem. If I remember correctly adding records to the end will not cause a split until you fill up that extent or delete one out of the middle but if you insert records you cause the split sooner and fill you the extent sooner because of the wasted space. Michael Saraco Systems Consultant Baer Consulting, Inc. Work - 507-526-2566 Cell- 507-525-0530 From: Johnny Luo [EMAIL PROTECTED] To: IBM-MAIN@BAMA.UA.EDU Date: 01/18/2008 10:26 AM Subject: Re: KSDS insert failed with out of space Michael, I will check that. Does it matter? I mean, you can add records to the end of the KSDS. You just can not insert records.. On Jan 19, 2008 12:07 AM, Michael Saraco [EMAIL PROTECTED] wrote: Yes it can do a split but it has to have the space. Did they define secondary extents for the index? From: Johnny Luo [EMAIL PROTECTED] To: IBM-MAIN@BAMA.UA.EDU Date: 01/18/2008 10:01 AM Subject: Re: KSDS insert failed with out of space Thanks for all the kind replies.. Space on the volumes should not be a problem. They have checked the storage group and space allocation. However, I missed to mention one info. Yes, they didn't specify any free CIs. Is this a problem? I mean, even I don't specify free CIs in a CA, CA-split can still happen. Right? On Jan 18, 2008 11:50 PM, Roberto Halais [EMAIL PROTECTED] wrote: Maybe the new record being added causes a CI (control interval) split and there is no free CIs in the CA (control area) causing a CA split which would possibly try to add a new extent to the file and there is no more space in the volume for the new extent. So you get an out of space condition in the volume. Also, maybe you do not have specified free CIs in a CA. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- Best Regards, Johnny Luo -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: KSDS insert failed with out of space
Look at the index and see if it is full and if it is setup to allocate secondary extents. I had something similar before happen and it was the index. Also if it was created to span multiple volumes and it is NONSMS make sure the other volumes actually exist. Michael Saraco Systems Consultant Baer Consulting, Inc. Work - 507-526-2566 Cell- 507-525-0530 From: Johnny Luo [EMAIL PROTECTED] To: IBM-MAIN@BAMA.UA.EDU Date: 01/18/2008 09:39 AM Subject: KSDS insert failed with out of space Hi, I encountered a strange problem with a KSDS data set. At this time, I only have some description of the problem from my colleague. Since it's so urgent, I would like to get some hints before I get more detailed info. (Sorry for that, I never did things like this before. But it's urgent..) According to the description, an out of space error occurred while inserting a record from within CICS. It's a KSDS reproed from a PS data set. You can add records to the end of those 'old' records and after that you can insert records into the new block of records. However, if you try to insert a record into the existing block, you get an 'out of space' error. Anyone give me some advices? Thanks. Johnny -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: KSDS insert failed with out of space
Thanks for all the kind replies.. Space on the volumes should not be a problem. They have checked the storage group and space allocation. However, I missed to mention one info. Yes, they didn't specify any free CIs. Is this a problem? I mean, even I don't specify free CIs in a CA, CA-split can still happen. Right? On Jan 18, 2008 11:50 PM, Roberto Halais [EMAIL PROTECTED] wrote: Maybe the new record being added causes a CI (control interval) split and there is no free CIs in the CA (control area) causing a CA split which would possibly try to add a new extent to the file and there is no more space in the volume for the new extent. So you get an out of space condition in the volume. Also, maybe you do not have specified free CIs in a CA. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: KSDS insert failed with out of space
-Original Message- From: IBM Mainframe Discussion List On Behalf Of Johnny Luo Hi, I encountered a strange problem with a KSDS data set. At this time, I only have some description of the problem from my colleague. Since it's so urgent, I would like to get some hints before I get more detailed info. (Sorry for that, I never did things like this before. But it's urgent..) According to the description, an out of space error occurred while inserting a record from within CICS. It's a KSDS reproed from a PS data set. You can add records to the end of those 'old' records and after that you can insert records into the new block of records. However, if you try to insert a record into the existing block, you get an 'out of space' error. Anyone give me some advices? Several possibilities, some of which have already been mentioned by others: 1. Insufficient space on the volume to allocate a secondary extent 2. KSDS not defined for secondary extents 3. SHR(4,4) specified and the record to be inserted would cause a CI or CA split -jc- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: KSDS insert failed with out of space
Michael, I will check that. Does it matter? I mean, you can add records to the end of the KSDS. You just can not insert records.. On Jan 19, 2008 12:07 AM, Michael Saraco [EMAIL PROTECTED] wrote: Yes it can do a split but it has to have the space. Did they define secondary extents for the index? From: Johnny Luo [EMAIL PROTECTED] To: IBM-MAIN@BAMA.UA.EDU Date: 01/18/2008 10:01 AM Subject: Re: KSDS insert failed with out of space Thanks for all the kind replies.. Space on the volumes should not be a problem. They have checked the storage group and space allocation. However, I missed to mention one info. Yes, they didn't specify any free CIs. Is this a problem? I mean, even I don't specify free CIs in a CA, CA-split can still happen. Right? On Jan 18, 2008 11:50 PM, Roberto Halais [EMAIL PROTECTED] wrote: Maybe the new record being added causes a CI (control interval) split and there is no free CIs in the CA (control area) causing a CA split which would possibly try to add a new extent to the file and there is no more space in the volume for the new extent. So you get an out of space condition in the volume. Also, maybe you do not have specified free CIs in a CA. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- Best Regards, Johnny Luo -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: KSDS insert failed with out of space
Yes it can do a split but it has to have the space. Did they define secondary extents for the index? From: Johnny Luo [EMAIL PROTECTED] To: IBM-MAIN@BAMA.UA.EDU Date: 01/18/2008 10:01 AM Subject: Re: KSDS insert failed with out of space Thanks for all the kind replies.. Space on the volumes should not be a problem. They have checked the storage group and space allocation. However, I missed to mention one info. Yes, they didn't specify any free CIs. Is this a problem? I mean, even I don't specify free CIs in a CA, CA-split can still happen. Right? On Jan 18, 2008 11:50 PM, Roberto Halais [EMAIL PROTECTED] wrote: Maybe the new record being added causes a CI (control interval) split and there is no free CIs in the CA (control area) causing a CA split which would possibly try to add a new extent to the file and there is no more space in the volume for the new extent. So you get an out of space condition in the volume. Also, maybe you do not have specified free CIs in a CA. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: KSDS insert failed with out of space
To diagnose VSAM request errors one needs to report, via whatever means, the return (R15), function and feedback codes (from RPL) and interpret them (Using Datasets book?). Hth... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
