I think it clear that Steve always meant OSVTOC and not CVOL. What I am not sure I agree with is the assertion that using ISKDSF to turn off the index and then turn it back on does not delete and rebuild the index?
> -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On > Behalf Of Pommier, Rex > Sent: Tuesday, January 03, 2023 3:05 PM > To: [email protected] > Subject: Re: [EXTERNAL] ICKDSF > > Hi Tony, > > I never had to deal with CVOLs or for that matter, VSAM catalogs. I cut my > teeth in the early XA days when ICF catalogs were still green. That said, I'm > trying to figure out what Steve means when he says he needs to convert the > indexed VTOC into a CVOL. As you concurred, the VTOC has nothing to do > with a CVOL (or VSAM catalog or ICF catalog). > > Steve is getting errors trying to use LSPACE. IDK if he posted the return > codes or errors he is receiving. If the LSPACE errors are related to the VTOC > index, I would think he should be able to run an ICKDSF BUILDIX OSVTOC > PURGE to (like Anthony alluded to), to shut off the VTOC index and the > PURGE is supposed to actually delete the VTOCIX dataset. Then running a > BUILDIX IXVTOC should put a new, pristine VTOC index back on the volume. > If he's getting an LSPACE on the actual VTOC, that's another matter. > > Rex > > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On > Behalf Of Tony Harminc > Sent: Tuesday, January 3, 2023 3:55 PM > To: [email protected] > Subject: Re: [EXTERNAL] ICKDSF > > On Tue, 3 Jan 2023 at 15:16, Pommier, Rex <[email protected]> > wrote: > > > Steve, > > > > Don't you simply mean converting the IXVTOC to an OSVTOC - ie an > > unindexed VTOC? If my old memory cells are recalling correctly, a > > CVOL was an ancient version of a VSAM catalog from before the ICF > catalogs existed. > > > > CVOL is a non-VSAM catalog (that is, it is not itself a VSAM dataset, and it > cannot point to VSAM datasets). It was the only kind of catalog prior to > OS/VS back in the 1970s, and it continued in common use well into the 1990s. > Perhaps more strictly, it is the *volume* that contains such a catalogue that > is > the CVOL (Control Volume). The catalog is a CVOL Catalog. > > That ancient *VSAM* catalog was the only kind of VSAM catalog in the early > days, and was a design disaster for a bunch of reasons. It was replaced long > ago by the ICF (Integrated Catalog Facility?) catalog, which with some tweaks > is pretty much what we have today. > > Regardless, these various catalogs have nothing at all to do with VTOCs, > indexed or not. > > Tony H. > > -----Original Message----- > > From: IBM Mainframe Discussion List <[email protected]> On > > Behalf Of Steve Beaver > > Sent: Tuesday, January 3, 2023 2:06 PM > > To: [email protected] > > Subject: Re: [EXTERNAL] ICKDSF > > > > What I have is a couple VOLUMES that are getting LSPACE errors > > > > Basically all the VOLUMES have indexed VTOCS that need to be Converted > > to a CVOL and returned to a indexed VTOC > > > > That the easy part. The painful part is I will have to the RO > > *ALL,UCB Offline > > > > Run the job > > > > RO *ALL,UCB Online > > > > Before anyon is the wiser > > > > > > > > ---------------------------------------------------------------------- > > ------ > > ---- > > > > This electronic mail (including any attachments) may contain > > information that is privileged, confidential, and/or otherwise > > protected from disclosure to anyone other than its intended > > recipient(s). Any dissemination or use of this electronic email or its > > contents (including any attachments) by persons other than the > > intended recipient(s) is strictly prohibited. If you have received > > this message in error, please notify us immediately by reply email so > > that we may correct our internal records. Please then delete the > > original message (including any > > attachments) in its entirety. Thank you > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:IBM- > [email protected]] > > On Behalf Of Pommier, Rex > > Sent: Tuesday, January 3, 2023 1:54 PM > > To: [email protected] > > Subject: Re: [EXTERNAL] ICKDSF > > > > The PURGE parameter deletes the VTOCIX dataset so using the BUILDIX > > will build a new one and not reuse the old, corrupt dataset. > > > > -----Original Message----- > > From: IBM Mainframe Discussion List <[email protected]> On > > Behalf Of Seymour J Metz > > Sent: Thursday, December 22, 2022 1:53 PM > > To: [email protected] > > Subject: Re: [EXTERNAL] ICKDSF > > > > That will work fine if the existing IXVTOC is good, but what if it is > > corrupted? > > > > > > -- > > Shmuel (Seymour J.) Metz > > > > > https://urldefense.com/v3/__http://mason.gmu.edu/*smetz3__;fg!!KjMRP > 1I > > xj6eLE > > 0Fj > > > <https://urldefense.com/v3/__http://mason.gmu.edu/*smetz3__;fg!!KjMR > P1 > > Ixj6eLE0Fj> > > !rQsxPmTo- > 3kSqLu15go6sNEUX8nn6PcuIZao7aZKuZ2xEN9BCZkpYpOn1HKVI96FWQXJ_ > > -p4 > > F3GGnpKkUQ$ > > > > ________________________________________ > > From: IBM Mainframe Discussion List [[email protected]] on > > behalf of Pommier, Rex [[email protected]] > > Sent: Thursday, December 22, 2022 2:34 PM > > To: [email protected] > > Subject: Re: [EXTERNAL] ICKDSF > > > > Steve, > > > > I'm not sure if a CVOL is the same as a non-indexed VTOC (I didn't > > think > > so) but to remove the IXVTOC, use ICKDSF BUILDIX OSVTOC PURGE which > > will unindex the VTOC and delete the VTOC index. Then run an ICKDSF > > BUILDIX INDXVTOC to rebuild a new one. > > > > If you have access to the ICKDSF manual, it's under the BUILDIX > > section of the manual. > > > > Rex > > > > -----Original Message----- > > From: IBM Mainframe Discussion List <[email protected]> On > > Behalf Of Steve Beaver > > Sent: Thursday, December 22, 2022 1:26 PM > > To: [email protected] > > Subject: [EXTERNAL] ICKDSF > > > > I worked in a stop the got sever LSPACE errors. > > > > > > > > Can anyone tell me the command to Convert a indexed vtoc to a CVOL and > > back to a INDEXED > > > > > > > > > > > > Regards, > > > > > > > > Steve > > > > > > > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > > The information contained in this message is confidential, protected > > from disclosure and may be legally privileged. If the reader of this > > message is not the intended recipient or an employee or agent > > responsible for delivering this message to the intended recipient, you > > are hereby notified that any disclosure, distribution, copying, or any > > action taken or action omitted in reliance on it, is strictly > > prohibited and may be unlawful. If you have received this > > communication in error, please notify us immediately by replying to > > this message and destroy the material in its entirety, whether in electronic > or hard copy format. Thank you. > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > > The information contained in this message is confidential, protected > > from disclosure and may be legally privileged. If the reader of this > > message is not the intended recipient or an employee or agent > > responsible for delivering this message to the intended recipient, you > > are hereby notified that any disclosure, distribution, copying, or any > > action taken or action omitted in reliance on it, is strictly > > prohibited and may be unlawful. If you have received this > > communication in error, please notify us immediately by replying to > > this message and destroy the material in its entirety, whether in electronic > or hard copy format. Thank you. > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > > The information contained in this message is confidential, protected > > from disclosure and may be legally privileged. If the reader of this > > message is not the intended recipient or an employee or agent > > responsible for delivering this message to the intended recipient, you > > are hereby notified that any disclosure, distribution, copying, or any > > action taken or action omitted in reliance on it, is strictly > > prohibited and may be unlawful. If you have received this > > communication in error, please notify us immediately by replying to > > this message and destroy the material in its entirety, whether in electronic > or hard copy format. Thank you. > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > The information contained in this message is confidential, protected from > disclosure and may be legally privileged. If the reader of this message is not > the intended recipient or an employee or agent responsible for delivering > this message to the intended recipient, you are hereby notified that any > disclosure, distribution, copying, or any action taken or action omitted in > reliance on it, is strictly prohibited and may be unlawful. If you have > received > this communication in error, please notify us immediately by replying to this > message and destroy the material in its entirety, whether in electronic or > hard copy format. Thank you. > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
