VTOC INDEX STATUS : DISABLED
Good __ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/ -- 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
VTOC INDEX STATUS : DISABLED
Good Morning Gentle Readers, I noticed (via ISMF) that one of our dasd is in DISABLED status under INDEX STATUS. When in TSO option 3.4 I do a "V" I receive a "Free space error". I attempted to perform the following BUILDIX DDNAME(D01) OSVTOC - I receive : ICK31529I ALLOCATE ERROR: RETURN CODE = 0148 ICK31515I 61E5 BUILDIX COMMAND FAILED. I tried BUILDIX DDNAME(VOLDD) IX but I was not successful. I received : ICK31529I ALLOCATE ERROR: RETURN CODE = 0148 ICK31515I 61E5 BUILDIX COMMAND FAILED. Is there something else I can try short of reinitializing the pack, which is presently 75% full. Thanks __ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now at http://ca.toolbar.yahoo.com. -- 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: VTOC INDEX STATUS : DISABLED
On Mon, 22 Sep 2008, esmie moo wrote: > Good Morning Gentle Readers, > > I noticed (via ISMF) that one of our dasd is in DISABLED status under INDEX STATUS. > When in TSO option 3.4 I do a "V" I receive a "Free space error". I > attempted to perform the following > > BUILDIX DDNAME(D01) OSVTOC - I receive : > ICK31529I ALLOCATE ERROR: RETURN CODE = 0148 > ICK31515I 61E5 BUILDIX COMMAND FAILED. > > I tried BUILDIX DDNAME(VOLDD) IX but I was not successful. I received : > ICK31529I ALLOCATE ERROR: RETURN CODE = 0148 > ICK31515I 61E5 BUILDIX COMMAND FAILED. > > Is there something else I can try short of reinitializing the pack, which is > presently 75% full. > > Thanks The 0148 is the DADSM allocate return code. From the manual, that means that there are "overlapping extents". Or, basically, that the VTOC has some corruption in because one or more tracks are allocated to more than one dataset. The safe thing to do is to use DFDSS to copy and recatalog all the datasets to another pack, then reinitialize the pack. If you do this, you should have somebody examine the data in the datasets copied because you likely have a corrupted datasets somewhere. -- Q: What do theoretical physicists drink beer from? A: Ein Stein. Maranatha! John McKown -- 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: VTOC INDEX STATUS : DISABLED
"John McKown" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > On Mon, 22 Sep 2008, esmie moo wrote: > > > Good Morning Gentle Readers, > > > > I noticed (via ISMF) that one of our dasd is in DISABLED status under > INDEX STATUS. > > When in TSO option 3.4 I do a "V" I receive a "Free space error". I > > attempted to perform the following > > > > BUILDIX DDNAME(D01) OSVTOC - I receive : > > ICK31529I ALLOCATE ERROR: RETURN CODE = 0148 > > ICK31515I 61E5 BUILDIX COMMAND FAILED. > > > > I tried BUILDIX DDNAME(VOLDD) IX but I was not successful. I received : > > ICK31529I ALLOCATE ERROR: RETURN CODE = 0148 > > ICK31515I 61E5 BUILDIX COMMAND FAILED. > > > > Is there something else I can try short of reinitializing the pack, which > > is presently 75% full. > > > > Thanks > > The 0148 is the DADSM allocate return code. From the manual, that means > that there are "overlapping extents". Or, basically, that the VTOC has > some corruption in because one or more tracks are allocated to more than > one dataset. > > The safe thing to do is to use DFDSS to copy and recatalog all the > datasets to another pack, then reinitialize the pack. If you do this, you > should have somebody examine the data in the datasets copied because you > likely have a corrupted datasets somewhere. > > -- > Maranatha! > John McKown > And: find out how the VTOC could get currupted, I can't remember ever seeing this problem. Check your DASD sharing options, including loopholes in sharing Dasd that should not be shared and your GRS/MIM parameters. Kees. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ** -- 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: VTOC INDEX STATUS : DISABLED
Thanks Gents for your input. I will take your advice and I will dig further as to the cause. --- On Tue, 9/23/08, Vernooy, C.P. - SPLXM <[EMAIL PROTECTED]> wrote: From: Vernooy, C.P. - SPLXM <[EMAIL PROTECTED]> Subject: Re: VTOC INDEX STATUS : DISABLED To: IBM-MAIN@BAMA.UA.EDU Received: Tuesday, September 23, 2008, 1:20 AM "John McKown" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > On Mon, 22 Sep 2008, esmie moo wrote: > > > Good Morning Gentle Readers, > > > > I noticed (via ISMF) that one of our dasd is in DISABLED status under > INDEX STATUS. > > When in TSO option 3.4 I do a "V" I receive a "Free space error". I attempted to perform the following > > > > BUILDIX DDNAME(D01) OSVTOC - I receive : > > ICK31529I ALLOCATE ERROR: RETURN CODE = 0148 > > ICK31515I 61E5 BUILDIX COMMAND FAILED. > > > > I tried BUILDIX DDNAME(VOLDD) IX but I was not successful. I received : > > ICK31529I ALLOCATE ERROR: RETURN CODE = 0148 > > ICK31515I 61E5 BUILDIX COMMAND FAILED. > > > > Is there something else I can try short of reinitializing the pack, which is presently 75% full. > > > > Thanks > > The 0148 is the DADSM allocate return code. From the manual, that means > that there are "overlapping extents". Or, basically, that the VTOC has > some corruption in because one or more tracks are allocated to more than > one dataset. > > The safe thing to do is to use DFDSS to copy and recatalog all the > datasets to another pack, then reinitialize the pack. If you do this, you > should have somebody examine the data in the datasets copied because you > likely have a corrupted datasets somewhere. > > -- > Maranatha! > John McKown > And: find out how the VTOC could get currupted, I can't remember ever seeing this problem. Check your DASD sharing options, including loopholes in sharing Dasd that should not be shared and your GRS/MIM parameters. Kees. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ** -- 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 __ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/ -- 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: VTOC INDEX STATUS : DISABLED
In a message dated 9/22/2008 8:10:59 A.M. Central Daylight Time, [EMAIL PROTECTED] writes: The safe thing to do is to use DFDSS to copy and recatalog all the datasets to another pack, then reinitialize the pack. If you do this, you should have somebody examine the data in the datasets copied because you likely have a corrupted datasets somewhere. >> I'd do a full pack backup then LISTVTOC to find overlapping extents. Delete the dups and restore what was left. When the dust settles need to find out what caused it. Have to go back in LOG and see when the disabled flag popped. It could be backups were running during reorgs or concurrent updates from non-shared systems and GRS/MIM parms need adjusting. **Looking for simple solutions to your real-life financial challenges? Check out WalletPop for the latest news and information, tips and calculators. (http://www.walletpop.com/?NCID=emlcntuswall0001) -- 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: VTOC INDEX STATUS : DISABLED
Given the overlapping extents, at least two of your datasets (assuming you don't have a dataset that overlays itself) are suspect as is the free space map. Step 1: Prevent any new allocations. This includes both new datasets and additional extents for existing datasets. "V SMS,VOL(xx),DISABLE,NEW" restricts new datasets if the pack is SMS managed. Step 2: Obtain a list of extents/associated datasets and identify the datasets that overlap. Step 3: Move all the non-overlapping datasets off this volume and restore the overlapping datasets from the most recent "good" backup. (Possibly the owners of the overlapping datasets could tell you if either is still good.) Step 4: Find out how this occurred and take corrective action. Depending on the cause, you may want to examine other packs for possible overlap. -Original Message- From: esmie moo Sent: Monday, September 22, 2008 5:59 AM To: IBM-MAIN@BAMA.UA.EDU Subject: VTOC INDEX STATUS : DISABLED Good Morning Gentle Readers, I noticed (via ISMF) that one of our dasd is in DISABLED status under INDEX STATUS. When in TSO option 3.4 I do a "V" I receive a "Free space error". I attempted to perform the following BUILDIX DDNAME(D01) OSVTOC - I receive : ICK31529I ALLOCATE ERROR: RETURN CODE = 0148 ICK31515I 61E5 BUILDIX COMMAND FAILED. I tried BUILDIX DDNAME(VOLDD) IX but I was not successful. I received : ICK31529I ALLOCATE ERROR: RETURN CODE = 0148 ICK31515I 61E5 BUILDIX COMMAND FAILED. Is there something else I can try short of reinitializing the pack, which is presently 75% full. -- 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
