Re: IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET
You can trawl SMF to see what attributes were assigned. > -Original Message- > From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of > John Dawes > Sent: Thursday, November 11, 2010 9:25 AM > To: IBM-MAIN@bama.ua.edu > Subject: Re: [IBM-MAIN] IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET > > I verified the DATACLAS construct. The volume count is 20. I am unable to > confirm if the LISTCAT has a EXT-ADDR because the dsn has been deleted. > Sorry, I should have noted it before I made the post. Going by to my > observation in general, would coding the VOLSERS in the VOL field cause the > abend because the DATACLASS has the volume count of 20 and there were 56 > volumes in this particular STORAGE GROUP POOL? > > --- On Thu, 11/11/10, Darth Keller wrote: > > > From: Darth Keller > Subject: Re: IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET > To: IBM-MAIN@bama.ua.edu > Received: Thursday, 11 November, 2010, 7:52 AM > > > Looking at the 110 Reason code information, I question if your dataset was > actually assign a dataclass allowing extended format. The way I > understand the 110, you exceeded the 4GB limit on 'standard' VSAM. You'll > need to look at the SMS constructs actually being used for your dataset > here. You're not giving us enough information here for us to tell. > > Take a close look at the ListCat information for the file which was > defined & ensure that it actually was defined as extended format. If it > is, you should see "EXTENDED EXT-ADDR " in the ListCat > > dd keller > > > > G'Day, > > I encountered the following abend when attempting to define a VSAM > extended dsn. The SMS routines (STORAGE CLASS, STORAGE GROUP & > DATACLASS) have been correctly defined. I verified if the volumes(3390-3) > were empty and all seem okay. > > IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET > VSAMG1.Z56013.VVL000D.MASTER4.SNAP > RETURN CODE IS 140 REASON CODE IS 110 IGG0CLEV > IGD306I UNEXPECTED ERROR DURING IGG0CLEV PROCESSING > RETURN CODE 140 REASON CODE 110 > > Below is the DEFINE CLUSTER: > DEFINE CLUSTER (NAME(VSAMG1.Z56013.VVL000D.MASTER4.SNAP) - > INDEXED KEYS(64,0) - > SHR(2,3) - > REUSE - > RECORDSIZE (64,4068) - > FREESPACE(15,20) - > VOLUME(A24S11,A24S12,A24S13,A24S14,A24S17,A24S19)) - > DATA - > (NAME(VSAMG1.Z56013.VVL000D.MASTER4.SNAP.DATA) - > CONTROLINTERVALSIZE (16384) - > CYLINDERS (3815,36)) - > INDEX - > (NAME(VSAMG1.Z56013.VVL000D.MASTER4.SNAP.INDEX) - > CYLINDERS (97,4) - > CONTROLINTERVALSIZE (4096)) > I reran the job successfully after removing all the VOLSERS except for > A24S11. Was it a fluke that it worked? Was the cause of the abend due to > having 6 VOLSERS coded in the VOLUME parm? > / > > > > This e-mail message and all attachments transmitted with it may > contain legally privileged and/or confidential information intended > solely for the use of the addressee(s). If the reader of this > message is not the intended recipient, you are hereby notified that > any reading, dissemination, distribution, copying, forwarding or > other use of this message or its attachments is strictly > prohibited. If you have received this message in error, please > notify the sender immediately and delete this message and all > copies and backups thereof. Thank you. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET
John, You should run the define again and then look at the listcat output to look for the extended attribute that Darth asked about. You don't need to load data to get this information. I am not in a postion to experiment but you should have 20 volumes (actual plus candidate) in the listcat output. You get the greater of volume count from the data class or the number of volumes in the define, not the sum of those two numbers. Regards, John From: IBM Mainframe Discussion List [ibm-m...@bama.ua.edu] On Behalf Of John Dawes [jhn_da...@yahoo.com.au] Sent: Thursday, November 11, 2010 12:25 PM To: IBM-MAIN@bama.ua.edu Subject: Re: IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET I verified the DATACLAS construct. The volume count is 20. I am unable to confirm if the LISTCAT has a EXT-ADDR because the dsn has been deleted. Sorry, I should have noted it before I made the post. Going by to my observation in general, would coding the VOLSERS in the VOL field cause the abend because the DATACLASS has the volume count of 20 and there were 56 volumes in this particular STORAGE GROUP POOL? --- On Thu, 11/11/10, Darth Keller wrote: From: Darth Keller Subject: Re: IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET To: IBM-MAIN@bama.ua.edu Received: Thursday, 11 November, 2010, 7:52 AM Looking at the 110 Reason code information, I question if your dataset was actually assign a dataclass allowing extended format. The way I understand the 110, you exceeded the 4GB limit on 'standard' VSAM. You'll need to look at the SMS constructs actually being used for your dataset here. You're not giving us enough information here for us to tell. Take a close look at the ListCat information for the file which was defined & ensure that it actually was defined as extended format. If it is, you should see "EXTENDED EXT-ADDR " in the ListCat dd keller G'Day, I encountered the following abend when attempting to define a VSAM extended dsn. The SMS routines (STORAGE CLASS, STORAGE GROUP & DATACLASS) have been correctly defined. I verified if the volumes(3390-3) were empty and all seem okay. IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET VSAMG1.Z56013.VVL000D.MASTER4.SNAP RETURN CODE IS 140 REASON CODE IS 110 IGG0CLEV IGD306I UNEXPECTED ERROR DURING IGG0CLEV PROCESSING RETURN CODE 140 REASON CODE 110 Below is the DEFINE CLUSTER: DEFINE CLUSTER (NAME(VSAMG1.Z56013.VVL000D.MASTER4.SNAP) - INDEXED KEYS(64,0) - SHR(2,3) - REUSE - RECORDSIZE (64,4068) - FREESPACE(15,20) - VOLUME(A24S11,A24S12,A24S13,A24S14,A24S17,A24S19)) - DATA - (NAME(VSAMG1.Z56013.VVL000D.MASTER4.SNAP.DATA) - CONTROLINTERVALSIZE (16384) - CYLINDERS (3815,36)) - INDEX - (NAME(VSAMG1.Z56013.VVL000D.MASTER4.SNAP.INDEX) - CYLINDERS (97,4) - CONTROLINTERVALSIZE (4096)) I reran the job successfully after removing all the VOLSERS except for A24S11. Was it a fluke that it worked? Was the cause of the abend due to having 6 VOLSERS coded in the VOLUME parm? / This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html NOTICE: The information contained in this electronic mail transmission is intended by Convergys Corporation for the use of the named individual or entity to which it is directed and may contain information that is privileged or otherwise confidential. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by telephone (collect), so that the sender's address records can be corrected. -- For IBM-M
Re: IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET
From: John Dawes To: IBM-MAIN@bama.ua.edu Date: 11/11/2010 11:26 AM Subject:Re: IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET Sent by:IBM Mainframe Discussion List Sorry, I'm at DR today - so I don't have the time or the manuals to look, but my thinking is that under certain circumstances & SMS attributes, multiple volumes could cause an allocation to be greater than 4GB's. I really suspect that your dataset was being allocated as a standard VSAM dataset subject to the 4GB limit. I'd re-allocate the dataset & take a look at the allocation messages & attributes assigned to it. / I verified the DATACLAS construct. The volume count is 20. I am unable to confirm if the LISTCAT has a EXT-ADDR because the dsn has been deleted. Sorry, I should have noted it before I made the post. Going by to my observation in general, would coding the VOLSERS in the VOL field cause the abend because the DATACLASS has the volume count of 20 and there were 56 volumes in this particular STORAGE GROUP POOL? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET
I verified the DATACLAS construct. The volume count is 20. I am unable to confirm if the LISTCAT has a EXT-ADDR because the dsn has been deleted. Sorry, I should have noted it before I made the post. Going by to my observation in general, would coding the VOLSERS in the VOL field cause the abend because the DATACLASS has the volume count of 20 and there were 56 volumes in this particular STORAGE GROUP POOL? --- On Thu, 11/11/10, Darth Keller wrote: From: Darth Keller Subject: Re: IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET To: IBM-MAIN@bama.ua.edu Received: Thursday, 11 November, 2010, 7:52 AM Looking at the 110 Reason code information, I question if your dataset was actually assign a dataclass allowing extended format. The way I understand the 110, you exceeded the 4GB limit on 'standard' VSAM. You'll need to look at the SMS constructs actually being used for your dataset here. You're not giving us enough information here for us to tell. Take a close look at the ListCat information for the file which was defined & ensure that it actually was defined as extended format. If it is, you should see "EXTENDED EXT-ADDR " in the ListCat dd keller G'Day, I encountered the following abend when attempting to define a VSAM extended dsn. The SMS routines (STORAGE CLASS, STORAGE GROUP & DATACLASS) have been correctly defined. I verified if the volumes(3390-3) were empty and all seem okay. IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET VSAMG1.Z56013.VVL000D.MASTER4.SNAP RETURN CODE IS 140 REASON CODE IS 110 IGG0CLEV IGD306I UNEXPECTED ERROR DURING IGG0CLEV PROCESSING RETURN CODE 140 REASON CODE 110 Below is the DEFINE CLUSTER: DEFINE CLUSTER (NAME(VSAMG1.Z56013.VVL000D.MASTER4.SNAP) - INDEXED KEYS(64,0) - SHR(2,3) - REUSE - RECORDSIZE (64,4068) - FREESPACE(15,20) - VOLUME(A24S11,A24S12,A24S13,A24S14,A24S17,A24S19)) - DATA - (NAME(VSAMG1.Z56013.VVL000D.MASTER4.SNAP.DATA) - CONTROLINTERVALSIZE (16384) - CYLINDERS (3815,36)) - INDEX - (NAME(VSAMG1.Z56013.VVL000D.MASTER4.SNAP.INDEX) - CYLINDERS (97,4) - CONTROLINTERVALSIZE (4096)) I reran the job successfully after removing all the VOLSERS except for A24S11. Was it a fluke that it worked? Was the cause of the abend due to having 6 VOLSERS coded in the VOLUME parm? / This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET
Looking at the 110 Reason code information, I question if your dataset was actually assign a dataclass allowing extended format. The way I understand the 110, you exceeded the 4GB limit on 'standard' VSAM. You'll need to look at the SMS constructs actually being used for your dataset here. You're not giving us enough information here for us to tell. Take a close look at the ListCat information for the file which was defined & ensure that it actually was defined as extended format. If it is, you should see "EXTENDED EXT-ADDR " in the ListCat dd keller G'Day, I encountered the following abend when attempting to define a VSAM extended dsn. The SMS routines (STORAGE CLASS, STORAGE GROUP & DATACLASS) have been correctly defined. I verified if the volumes(3390-3) were empty and all seem okay. IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET VSAMG1.Z56013.VVL000D.MASTER4.SNAP RETURN CODE IS 140 REASON CODE IS 110 IGG0CLEV IGD306I UNEXPECTED ERROR DURING IGG0CLEV PROCESSING RETURN CODE 140 REASON CODE 110 Below is the DEFINE CLUSTER: DEFINE CLUSTER (NAME(VSAMG1.Z56013.VVL000D.MASTER4.SNAP) - INDEXED KEYS(64,0) - SHR(2,3) - REUSE - RECORDSIZE (64,4068) - FREESPACE(15,20) - VOLUME(A24S11,A24S12,A24S13,A24S14,A24S17,A24S19)) - DATA - (NAME(VSAMG1.Z56013.VVL000D.MASTER4.SNAP.DATA) - CONTROLINTERVALSIZE (16384) - CYLINDERS (3815,36)) - INDEX - (NAME(VSAMG1.Z56013.VVL000D.MASTER4.SNAP.INDEX) - CYLINDERS (97,4) - CONTROLINTERVALSIZE (4096)) I reran the job successfully after removing all the VOLSERS except for A24S11. Was it a fluke that it worked? Was the cause of the abend due to having 6 VOLSERS coded in the VOLUME parm? / This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET
G'Day, I encountered the following abend when attempting to define a VSAM extended dsn. The SMS routines (STORAGE CLASS, STORAGE GROUP & DATACLASS) have been correctly defined. I verified if the volumes(3390-3) were empty and all seem okay. IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET VSAMG1.Z56013.VVL000D.MASTER4.SNAP RETURN CODE IS 140 REASON CODE IS 110 IGG0CLEV IGD306I UNEXPECTED ERROR DURING IGG0CLEV PROCESSING RETURN CODE 140 REASON CODE 110 Below is the DEFINE CLUSTER: DEFINE CLUSTER (NAME(VSAMG1.Z56013.VVL000D.MASTER4.SNAP) - INDEXED KEYS(64,0) - SHR(2,3) - REUSE - RECORDSIZE (64,4068) - FREESPACE(15,20) - VOLUME(A24S11,A24S12,A24S13,A24S14,A24S17,A24S19)) - DATA - (NAME(VSAMG1.Z56013.VVL000D.MASTER4.SNAP.DATA) - CONTROLINTERVALSIZE (16384) - CYLINDERS (3815,36)) - INDEX - (NAME(VSAMG1.Z56013.VVL000D.MASTER4.SNAP.INDEX) - CYLINDERS (97,4) - CONTROLINTERVALSIZE (4096)) I reran the job successfully after removing all the VOLSERS except for A24S11. Was it a fluke that it worked? Was the cause of the abend due to having 6 VOLSERS coded in the VOLUME parm? Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Catalog Error - Definiting non-vsam dataset
"Jacky Bright" wrote in message news:... > Hi, > > I am getting messages while defining non-vsam datasets : > > IEC331I 020-000(2908001C),H2FAIPA3,UTIL0003,IGG0CLEG > > IEC331I CATALOG.TEST01.USER > > IEC331I FCIS.ZZZ.ON.CCISCHZZ.P7.D100130 > IEC332I PADD,NVSM,IDVR,CDVR,ACD1 > > IEC333I L028(041),08,CATALOG.TEST01.USER,FCIS.ZZZ.ON.CCISCHZZ.P7.D100130 > > > > IGD17102I CATALOG ERROR IN DEFINING NONVSAM DATA SET > FCIS.ZZZ.ON.DCISMAS1.CCISCHZZ.P7.D100130 > RETURN CODE IS 20 REASON CODE IS 0 IGG0CLEG > IGD306I UNEXPECTED ERROR DURING IGG0CLEG PROCESSING > RETURN CODE 20 REASON CODE 0 > THE MODULE THAT DETECTED THE ERROR IS IGDVTSCU > SMS MODULE TRACE BACK - VTSCU VTSCT VTSCR SSIRT > SYMPTOM RECORD CREATED, PROBLEM ID IS IGD03201 > > Any idea about this error ? > > JAcky > Your catalog is full. See IDC3009I: : RETURN CODE20 : Explanation:There is insufficient space in the catalog to perform the : requested update or addition. : Reason CodeDescription 0 Explanation:The catalog cannot be extended for one of the following reasons: ~ There is no more space on the volume on which the catalog resides ~ The maximum number of extents has been reached ~ The catalog has reached the 4GB limit ~ There is not enough contiguous space on the volume (required when the catalog's secondary allocation is defined in tracks). Programmer Response: Scratch unneeded data sets from the volume. Delete all unnecessary entries from the catalog. The catalog may need to be reallocated and rebuilt if these steps do not resolve the space shortage. ** 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Catalog Error - Definiting non-vsam dataset
Hi, I am getting messages while defining non-vsam datasets : IEC331I 020-000(2908001C),H2FAIPA3,UTIL0003,IGG0CLEG IEC331I CATALOG.TEST01.USER IEC331I FCIS.ZZZ.ON.CCISCHZZ.P7.D100130 IEC332I PADD,NVSM,IDVR,CDVR,ACD1 IEC333I L028(041),08,CATALOG.TEST01.USER,FCIS.ZZZ.ON.CCISCHZZ.P7.D100130 IGD17102I CATALOG ERROR IN DEFINING NONVSAM DATA SET FCIS.ZZZ.ON.DCISMAS1.CCISCHZZ.P7.D100130 RETURN CODE IS 20 REASON CODE IS 0 IGG0CLEG IGD306I UNEXPECTED ERROR DURING IGG0CLEG PROCESSING RETURN CODE 20 REASON CODE 0 THE MODULE THAT DETECTED THE ERROR IS IGDVTSCU SMS MODULE TRACE BACK - VTSCU VTSCT VTSCR SSIRT SYMPTOM RECORD CREATED, PROBLEM ID IS IGD03201 Any idea about this error ? JAcky -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Catalog Error - Can't delete dataset
>Why don't you just zap the VTOC entry for this dataset to PS? The catalog >structure is much simpler then and bypasses VVDS. You should be familiar >with VTOP dump, zap and format-x DSCBs. Don't try it at home if you are not >familiar with it! If you have CA-Disk, you can use a utility to this for >you. There was no VTOC entry for the dataset on the volume. Jeffrey Deaver, Engineer Systems Engineering [EMAIL PROTECTED] 651-665-4231(v) IS - "Creating competitive advantage with technology. Providing service that excels." OSS - " Where Innovation Happens" -- 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: Catalog Error - Can't delete dataset
Why don't you just zap the VTOC entry for this dataset to PS? The catalog structure is much simpler then and bypasses VVDS. You should be familiar with VTOP dump, zap and format-x DSCBs. Don't try it at home if you are not familiar with it! If you have CA-Disk, you can use a utility to this for you. ITschak On 8/25/08, Brian Peterson <[EMAIL PROTECTED]> wrote: > > I've had good luck with IBM's unsupported VVDSFIX tool, to delete an > otherwise un-delete-able data set. The VVDSFIX tool's DELBCSR command did > the trick for me. > > //*DELBCSR - DELETE BCS RECORD will erase a BCS record.** > //* The purpose of this command is to erase a catalog ** > //* record that has a bad name such as a special ** > //* character imbedded within the name that IDCAMS thinks ** > //* is bad and prevents the DELETE from working. ** > //*** > > Google VVDSFIX which shows the following link as the tool source: > > www-1.ibm.com/support/docview.wss?uid=isg3S1000618 > > Brian > > On Mon, 25 Aug 2008 10:15:42 -0500, Jeffrey Deaver wrote: > > >Well, I'd love to try the zap, but I don't have CatalogRecovery > +. Bummer. > >Nothing else is working. > > > >Thanks for all the tips so far, I'll keep trying stuff and let you know > >what becomes of this. > > > >Jeffrey Deaver, Engineer > > -- > 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: Catalog Error - Can't delete dataset
>I've had good luck with IBM's unsupported VVDSFIX tool, to delete an >otherwise un-delete-able data set. The VVDSFIX tool's DELBCSR command did >the trick for me. SHAZAM! It worked. Thanks! Jeffrey Deaver, Engineer Systems Engineering [EMAIL PROTECTED] 651-665-4231(v) IS - "Creating competitive advantage with technology. Providing service that excels." OSS - " Where Innovation Happens" -- 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: Catalog Error - Can't delete dataset
I've had good luck with IBM's unsupported VVDSFIX tool, to delete an otherwise un-delete-able data set. The VVDSFIX tool's DELBCSR command did the trick for me. //*DELBCSR - DELETE BCS RECORD will erase a BCS record.** //* The purpose of this command is to erase a catalog ** //* record that has a bad name such as a special ** //* character imbedded within the name that IDCAMS thinks ** //* is bad and prevents the DELETE from working. ** //*** Google VVDSFIX which shows the following link as the tool source: www-1.ibm.com/support/docview.wss?uid=isg3S1000618 Brian On Mon, 25 Aug 2008 10:15:42 -0500, Jeffrey Deaver wrote: >Well, I'd love to try the zap, but I don't have CatalogRecovery +. Bummer. >Nothing else is working. > >Thanks for all the tips so far, I'll keep trying stuff and let you know >what becomes of this. > >Jeffrey Deaver, Engineer -- 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: Catalog Error - Can't delete dataset
>4. For this one you need to leave the ver… as is. > >//SYSINDD * > ZAP BCS(USERCAT.NAME) - > DELETE(KEY(DATASET.NAME) - > VER(04,C'A')) > Well, I'd love to try the zap, but I don't have CatalogRecovery +. Bummer. Nothing else is working. Thanks for all the tips so far, I'll keep trying stuff and let you know what becomes of this. Jeffrey Deaver, Engineer Systems Engineering [EMAIL PROTECTED] 651-665-4231(v) IS - "Creating competitive advantage with technology. Providing service that excels." OSS - " Where Innovation Happens" -- 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: Catalog Error - Can't delete dataset
DELETE 'dataset name' nvr FILE(DD1) DD1 points to the correct UCAT HTH, So just to try renaming it to something... Seems like everything I try really wants the physical file there - which doesn't make sense since I've run into rouge catalog entries before and not had trouble cleaning them up. This one is being stubborn. ALTER GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 - NEWNAME(GROUP.PCLAIMS.LOA.JUNK) - CAT(ISV.SICF.USERCAT.VSYSP35) IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE IS 94 - REASON CODE IS IGG0CLRN-8 8 Explanation: OBTAIN did not find requested format-1 DSCB on specified volume. Programmer Response: Ensure that the correct volume is -- 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: Catalog Error - Can't delete dataset
Jeffrey, here are a few of the parameters that I have tried and have gotten the file deleted. Since, you didn’t post the commands that you’ve used. I figure that I send you what has worked for me in the pass. Hope this helps. Just review the parms in manual before using to make sure that we’ll work for you. 1. //DELNVR EXEC PGM=IDCAMS //DD1 DD VOL=SER=XX,UNIT=3390,DISP=OLD //SYSPRINT DD SYSOUT=* //SYSINDD * DELETE DATASET NAME - FILE(DD1) - NVR 2. //DELNOSC EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSINDD * DELETE DATASET.NAME.MAR0707 - PURGE - CAT(USERCAT.NAME) 3. //STEP13 EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DELETE DATASET.NAME NSCR 4. For this one you need to leave the ver… as is. //SYSINDD * ZAP BCS(USERCAT.NAME) - DELETE(KEY(DATASET.NAME) - VER(04,C'A')) -- 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: Catalog Error - Can't delete dataset
>Problem with the instruction set above - rename it to what? So just to try renaming it to something... Seems like everything I try really wants the physical file there - which doesn't make sense since I've run into rouge catalog entries before and not had trouble cleaning them up. This one is being stubborn. ALTER GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 - NEWNAME(GROUP.PCLAIMS.LOA.JUNK) - CAT(ISV.SICF.USERCAT.VSYSP35) IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE IS 94 - REASON CODE IS IGG0CLRN-8 8 Explanation: OBTAIN did not find requested format-1 DSCB on specified volume. Programmer Response: Ensure that the correct volume is mounted Jeffrey Deaver, Engineer Systems Engineering [EMAIL PROTECTED] 651-665-4231(v) IS - "Creating competitive advantage with technology. Providing service that excels." OSS - " Where Innovation Happens" -- 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: Catalog Error - Can't delete dataset
> How can you PURGE a non-existant dataset? Tried it both ways. I get the same result without the PURGE. Jeffrey Deaver, Engineer Systems Engineering [EMAIL PROTECTED] 651-665-4231(v) IS - "Creating competitive advantage with technology. Providing service that excels." OSS - " Where Innovation Happens" -- 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: Catalog Error - Can't delete dataset
>Had to go to 1.9 manual to find 90-54. Does this make any sense to you? > >| 54 Explanation: DELETE failed because the data set is > being renamed but it has not completed. > > | Programmer Response: Rename the data set with the > | IDCAMS ALTER command and then delete it. Sort of. The name tells me that this file is probably left over from a simple process we have which automates the reallocation of files. People use it to expand/change the allocation. File is temp copied to the file in question, original file is deleted and reallocated, temp copy is copied back and then (suppose to be) deleted. Problem with the instruction set above - rename it to what? Jeffrey Deaver, Engineer Systems Engineering [EMAIL PROTECTED] 651-665-4231(v) IS - "Creating competitive advantage with technology. Providing service that excels." OSS - " Where Innovation Happens" -- 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: Catalog Error - Can't delete dataset
DSN looks like it could be an HSM level 1 migrate. Is it? Perhaps there is a recovery action needed for a failed migrate from HSM? Linda Mooney -- Original message -- From: "Johnston, Robert E" <[EMAIL PROTECTED]> > Had to go to 1.9 manual to find 90-54. Does this make any sense to you? > > | 54 Explanation: DELETE failed because the data set is > being renamed but it has not completed. > > | Programmer Response: Rename the data set with the > | IDCAMS ALTER command and then delete it. > > > > > -Original Message- > > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > > Behalf Of Jeffrey Deaver > > Sent: Friday, August 22, 2008 3:22 PM > > To: IBM-MAIN@BAMA.UA.EDU > > Subject: Re: Catalog Error - Can't delete dataset > > > > >Have you tried delete noscratch. > > > > Yep. Got this... > > > > IDCAMS SYSTEM SERVICES TIME: 15 > > > > DELETE - > > GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 - > > PURGE - > > NOSCRATCH > > IDC3014I CATALOG ERROR > > IDC3009I ** VSAM CATALOG RETURN CODE IS 90 - REASON CODE IS IGG0CLFO-54 > > IDC0551I ** ENTRY GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 NOT > > IDC0551I DELETED > > IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8 > > > > IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 8 > > > > > > Jeffrey Deaver, Engineer > > Systems Engineering > > [EMAIL PROTECTED] > > 651-665-4231(v) > > IS - "Creating competitive advantage with technology. Providing service > > that excels." > > OSS - " Where Innovation Happens" > > > > > Confidentiality Notice: This e-mail message, including any attachments, is > for > the sole use of the intended recipient(s) and may contain confidential and > privileged information. Any unauthorized review, use, disclosure or > distribution is prohibited. If you are not the intended recipient, please > contact the sender by reply e-mail and destroy all copies of the original > message. > > -- > 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: Catalog Error - Can't delete dataset
Had to go to 1.9 manual to find 90-54. Does this make any sense to you? | 54 Explanation: DELETE failed because the data set is being renamed but it has not completed. | Programmer Response: Rename the data set with the | IDCAMS ALTER command and then delete it. > -Original Message- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Jeffrey Deaver > Sent: Friday, August 22, 2008 3:22 PM > To: IBM-MAIN@BAMA.UA.EDU > Subject: Re: Catalog Error - Can't delete dataset > > >Have you tried delete noscratch. > > Yep. Got this... > > IDCAMS SYSTEM SERVICES TIME: 15 > >DELETE - >GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 - >PURGE - >NOSCRATCH > IDC3014I CATALOG ERROR > IDC3009I ** VSAM CATALOG RETURN CODE IS 90 - REASON CODE IS IGG0CLFO-54 > IDC0551I ** ENTRY GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 NOT > IDC0551I DELETED > IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8 > > IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 8 > > > Jeffrey Deaver, Engineer > Systems Engineering > [EMAIL PROTECTED] > 651-665-4231(v) > IS - "Creating competitive advantage with technology. Providing service > that excels." > OSS - " Where Innovation Happens" > Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. -- 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: Catalog Error - Can't delete dataset
How can you PURGE a non-existant dataset? From: Jeffrey Deaver [mailto:[EMAIL PROTECTED] Sent: Fri 8/22/2008 4:22 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Catalog Error - Can't delete dataset >Have you tried delete noscratch. Yep. Got this... IDCAMS SYSTEM SERVICES TIME: 15 DELETE - GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 - PURGE - NOSCRATCH IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE IS 90 - REASON CODE IS IGG0CLFO-54 IDC0551I ** ENTRY GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 NOT IDC0551I DELETED IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8 IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 8 Jeffrey Deaver, Engineer Systems Engineering [EMAIL PROTECTED] 651-665-4231(v) IS - "Creating competitive advantage with technology. Providing service that excels." OSS - " Where Innovation Happens" -- 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: Catalog Error - Can't delete dataset
>Have you tried delete noscratch. Yep. Got this... IDCAMS SYSTEM SERVICES TIME: 15 DELETE - GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 - PURGE - NOSCRATCH IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE IS 90 - REASON CODE IS IGG0CLFO-54 IDC0551I ** ENTRY GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 NOT IDC0551I DELETED IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8 IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 8 Jeffrey Deaver, Engineer Systems Engineering [EMAIL PROTECTED] 651-665-4231(v) IS - "Creating competitive advantage with technology. Providing service that excels." OSS - " Where Innovation Happens" -- 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: Catalog Error - Can't delete dataset
Did you try: Idcams Delete dataset.name NSCR From: Jeffrey Deaver [mailto:[EMAIL PROTECTED] Sent: Fri 8/22/2008 4:05 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Catalog Error - Can't delete dataset I can't delete a dataset which is cataloged, but no longer physically exists. I've tried every trick I can think of to delete the catalog entry, nothing is working. Ideas? Ran a Diag on the catalog, got this... IDC21364I ERROR DETECTED BY DIAGNOSE: ICFCAT ENTRY: GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 (A) RECORD: GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 /00 OFFSET: X'0063' REASON: 51 - VVDS ENTRY NOT FOUND. SCAN VVDS FAILED. IDC21365I ICFCAT RECORD DISPLAY: RECORD: GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 /00 00 007D004D C101 2DC7D9D6 E4D74BD7 C3D3C1C9 D4E24BD3 D6C14BE3 D1D1F4F9 *.'.(AGROUP.PCLAIMS.LOA.TJJ49* 20 D4C9C74B C4F2F0F0 F2F2F6F2 4BE3F1F4 F3F9F2F5 F519 2607 D7D9C9D4 *MIG.D2002262.T1439255...PRIM* 40 C1D9E800 08E2 E3C1D5C4 C1D9C400 1401 0890 243F *ARYSTANDARD.* 60 0C00 1A0480D7 D9D2F0F0 F1301020 0F880001 0020 00 *...PRK001 * Thanks. Jeffrey Deaver, Engineer Systems Engineering [EMAIL PROTECTED] 651-665-4231(v) IS - "Creating competitive advantage with technology. Providing service that excels." OSS - " Where Innovation Happens" -- 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: Catalog Error - Can't delete dataset
Have you tried delete noscratch. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Jeffrey Deaver Sent: Friday, August 22, 2008 4:05 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Catalog Error - Can't delete dataset I can't delete a dataset which is cataloged, but no longer physically exists. I've tried every trick I can think of to delete the catalog entry, nothing is working. Ideas? Ran a Diag on the catalog, got this... IDC21364I ERROR DETECTED BY DIAGNOSE: ICFCAT ENTRY: GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 (A) RECORD: GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 /00 OFFSET: X'0063' REASON: 51 - VVDS ENTRY NOT FOUND. SCAN VVDS FAILED. IDC21365I ICFCAT RECORD DISPLAY: RECORD: GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 /00 00 007D004D C101 2DC7D9D6 E4D74BD7 C3D3C1C9 D4E24BD3 D6C14BE3 D1D1F4F9 *.'.(AGROUP.PCLAIMS.LOA.TJJ49* 20 D4C9C74B C4F2F0F0 F2F2F6F2 4BE3F1F4 F3F9F2F5 F519 2607 D7D9C9D4 *MIG.D2002262.T1439255...PRIM* 40 C1D9E800 08E2 E3C1D5C4 C1D9C400 1401 0890 243F *ARYSTANDARD.* 60 0C00 1A0480D7 D9D2F0F0 F1301020 0F880001 0020 00 *...PRK001 * Thanks. Jeffrey Deaver, Engineer Systems Engineering [EMAIL PROTECTED] 651-665-4231(v) IS - "Creating competitive advantage with technology. Providing service that excels." OSS - " Where Innovation Happens" -- 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 - The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. -- 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
Catalog Error - Can't delete dataset
I can't delete a dataset which is cataloged, but no longer physically exists. I've tried every trick I can think of to delete the catalog entry, nothing is working. Ideas? Ran a Diag on the catalog, got this... IDC21364I ERROR DETECTED BY DIAGNOSE: ICFCAT ENTRY: GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 (A) RECORD: GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 /00 OFFSET: X'0063' REASON: 51 - VVDS ENTRY NOT FOUND. SCAN VVDS FAILED. IDC21365I ICFCAT RECORD DISPLAY: RECORD: GROUP.PCLAIMS.LOA.TJJ49MIG.D2002262.T1439255 /00 00 007D004D C101 2DC7D9D6 E4D74BD7 C3D3C1C9 D4E24BD3 D6C14BE3 D1D1F4F9 *.'.(AGROUP.PCLAIMS.LOA.TJJ49* 20 D4C9C74B C4F2F0F0 F2F2F6F2 4BE3F1F4 F3F9F2F5 F519 2607 D7D9C9D4 *MIG.D2002262.T1439255...PRIM* 40 C1D9E800 08E2 E3C1D5C4 C1D9C400 1401 0890 243F *ARYSTANDARD.* 60 0C00 1A0480D7 D9D2F0F0 F1301020 0F880001 0020 00 *...PRK001 * Thanks. Jeffrey Deaver, Engineer Systems Engineering [EMAIL PROTECTED] 651-665-4231(v) IS - "Creating competitive advantage with technology. Providing service that excels." OSS - " Where Innovation Happens" -- 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: CATALOG ERROR
>The reason I used the LOCK to prevent updates to this CATALOG because it is >shared. That's not the purpose of LOCK. It's for recovery/operational purposes, IIRC. - Too busy driving to stop for gas! -- 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: CATALOG ERROR
Thanks to all. I removed the LOCK and it worked. The reason I used the LOCK to prevent updates to this CATALOG because it is shared. Larry Crilley <[EMAIL PROTECTED]> wrote: RETURN CODE 186 Explanation: Error attempting to lock a catalog or access a locked catalog. 2 Explanation: Access was denied for one of the following reasons: ° No profile IGG.CATLOCK of class type FACILITY was found ° RACF, or an equivalent product, was not active ° No MVS router exit was found Why the LOCK parm on the define? LOCK specifies that the catalog identified by entryname is to be defined with the lock attribute on. Defining the catalog with the lock on restricts catalog access to authorized personnel. Specification of this parameter requires read authority to the profile name, IGG.CATLOCK, with class type FACILITY. Integrated catalog facility catalogs are normally defined with the lock attribute on only after a DELETE RECOVERY during catalog recovery operations. You need READ authority for IGG.CATLOCK. Larry Crilley Dino-Software Corporation 800.480.DINO 412.366.3566 www.dino-software.com Dino-Software Utilities T-REX Superior catalog management tool inclusive of HSM & Tape audits REORGadon First REORG While-OPEN tool for HSM Teradon First ever OnLine REPRO MERGECAT utility Xtinct - DASD Data purge RTD - DASD Real Time Defrag DAL Analysis for Legato in an easy to view format -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of esmie moo Sent: Tuesday, December 04, 2007 10:26 AM To: IBM-MAIN@BAMA.UA.EDU Subject: CATALOG ERROR Good Day Gentle Readers, I am trying to define a user catalog and I am unsuccessful. The error message (please see below) points to a Security problem. I checked with Security and they say that it is not a Security issue. Could anybody tell me where I can look? DEFINE - USERCATALOG - (NAME (SYS1.PROD.UCAT) - CYL(5,2) - VOLUME(UCAT01) - ICFCATALOG - STRNO(3) - FREESPACE(20 20) - NOIMBED - LOCK - SHAREOPTIONS(3 4)) - DATA( - CONTROLINTERVALSIZE(4096)) IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE IS 186 - REASON CODE IS IGG0CLFT-2 IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12 - Looking for the perfect gift? Give the gift of Flickr! -- 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 - Looking for the perfect gift? Give the gift of Flickr! -- 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: CATALOG ERROR
RETURN CODE 186 Explanation: Error attempting to lock a catalog or access a locked catalog. 2 Explanation: Access was denied for one of the following reasons: ° No profile IGG.CATLOCK of class type FACILITY was found ° RACF, or an equivalent product, was not active ° No MVS router exit was found Why the LOCK parm on the define? LOCK specifies that the catalog identified by entryname is to be defined with the lock attribute on. Defining the catalog with the lock on restricts catalog access to authorized personnel. Specification of this parameter requires read authority to the profile name, IGG.CATLOCK, with class type FACILITY. Integrated catalog facility catalogs are normally defined with the lock attribute on only after a DELETE RECOVERY during catalog recovery operations. You need READ authority for IGG.CATLOCK. Larry Crilley Dino-Software Corporation 800.480.DINO 412.366.3566 www.dino-software.com Dino-Software Utilities T-REX Superior catalog management tool inclusive of HSM & Tape audits REORGadon First REORG While-OPEN tool for HSM Teradon First ever OnLine REPRO MERGECAT utility Xtinct - DASD Data purge RTD - DASD Real Time Defrag DAL Analysis for Legato in an easy to view format -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of esmie moo Sent: Tuesday, December 04, 2007 10:26 AM To: IBM-MAIN@BAMA.UA.EDU Subject: CATALOG ERROR Good Day Gentle Readers, I am trying to define a user catalog and I am unsuccessful. The error message (please see below) points to a Security problem. I checked with Security and they say that it is not a Security issue. Could anybody tell me where I can look? DEFINE- USERCATALOG - (NAME (SYS1.PROD.UCAT) - CYL(5,2) - VOLUME(UCAT01)- ICFCATALOG- STRNO(3) - FREESPACE(20 20) - NOIMBED - LOCK - SHAREOPTIONS(3 4))- DATA( - CONTROLINTERVALSIZE(4096)) IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE IS 186 - REASON CODE IS IGG0CLFT-2 IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12 - Looking for the perfect gift? Give the gift of Flickr! -- 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: CATALOG ERROR
> -Original Message- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of esmie moo > Sent: Tuesday, December 04, 2007 9:26 AM > To: IBM-MAIN@BAMA.UA.EDU > Subject: CATALOG ERROR > > Good Day Gentle Readers, > > I am trying to define a user catalog and I am unsuccessful. > The error message (please see below) points to a Security > problem. I checked with Security and they say that it is not > a Security issue. Could anybody tell me where I can look? > DEFINE- > USERCATALOG - > (NAME (SYS1.PROD.UCAT) - > CYL(5,2) - > VOLUME(UCAT01)- > ICFCATALOG- > STRNO(3) - > FREESPACE(20 20) - > NOIMBED - > LOCK - > SHAREOPTIONS(3 4))- > DATA( - > CONTROLINTERVALSIZE(4096)) > > IDC3014I CATALOG ERROR > > IDC3009I ** VSAM CATALOG RETURN CODE IS 186 - REASON CODE IS > IGG0CLFT-2 > IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12 It might work if you remove the LOCK parameter in the above DEFINE. or you must have READ authority to the IGG.CATLOCK profile in the FACILITY class in RACF. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- 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: CATALOG ERROR
You have a locked catalog - you did check the messages and codes manuals for IDC3009I, right? Rob Scott Rocket Software, Inc 275 Grove Street Newton, MA 02466 617-614-2305 [EMAIL PROTECTED] -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of esmie moo Sent: 04 December 2007 15:26 To: IBM-MAIN@BAMA.UA.EDU Subject: CATALOG ERROR Good Day Gentle Readers, I am trying to define a user catalog and I am unsuccessful. The error message (please see below) points to a Security problem. I checked with Security and they say that it is not a Security issue. Could anybody tell me where I can look? DEFINE- USERCATALOG - (NAME (SYS1.PROD.UCAT) - CYL(5,2) - VOLUME(UCAT01)- ICFCATALOG- STRNO(3) - FREESPACE(20 20) - NOIMBED - LOCK - SHAREOPTIONS(3 4))- DATA( - CONTROLINTERVALSIZE(4096)) IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE IS 186 - REASON CODE IS IGG0CLFT-2 IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12 - Looking for the perfect gift? Give the gift of Flickr! -- 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
CATALOG ERROR
Good Day Gentle Readers, I am trying to define a user catalog and I am unsuccessful. The error message (please see below) points to a Security problem. I checked with Security and they say that it is not a Security issue. Could anybody tell me where I can look? DEFINE- USERCATALOG - (NAME (SYS1.PROD.UCAT) - CYL(5,2) - VOLUME(UCAT01)- ICFCATALOG- STRNO(3) - FREESPACE(20 20) - NOIMBED - LOCK - SHAREOPTIONS(3 4))- DATA( - CONTROLINTERVALSIZE(4096)) IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE IS 186 - REASON CODE IS IGG0CLFT-2 IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12 - Looking for the perfect gift? Give the gift of Flickr! -- 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: CATALOG ERROR
John I checked and the dsn is not there. I will check with IBM for assistance. Thanks for your help. Thanks to all who offered their suggestions and help. John Kington <[EMAIL PROTECTED]> wrote: Esmie, I recommend you check the dasd volume(s) to make sure the dataset that you deleted using noscratch is not still there. I am out of ideas. If no one else figures it out, you could search ibmlink or open a problem with IBM for assistance. Sorry, John > - Ask a question on any topic and get answers from real people. Go to Yahoo! Answers. -- 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: CATALOG ERROR
Esmie, I recommend you check the dasd volume(s) to make sure the dataset that you deleted using noscratch is not still there. I am out of ideas. If no one else figures it out, you could search ibmlink or open a problem with IBM for assistance. Sorry, John esmie moo <[EMAIL PROTECTED]> wrote: > The dsn is created on dasd and SMS managed. I checked the disk > status and it is always online. The job creates the dsn in the SMS > pool which has 23 dasds in that storage pool. > > John Kington <[EMAIL PROTECTED]> wrote: Keeping with top posting: > Esmie, > Do you recall whether the oldest generation was on dasd or tape? The > scratch error > indicates that it was dasd and the volume was not online. Maybe you > reclaimed a > dasd volume or have a dasd volume offline? > Regards, > John > > >Thanks John. Yes, I noticed that the catalog entry was present. I then > scratched the entry (del noscr). But I >cannot understand why this > happened. I checked the syslog but found nothing that would indicate any > type of a >problem. Any other suggestions? > >>My job put out the >> following error: >> >>IEC331I 042-006(04280039),JS3BATCH,SOFVMA05,SCRT,IGG0CLH0 >>IEC331I VOL,INST49,NAME,DATAALL.REND.PC5.PROD.VMAXTD.G0553V00 >>IEC331I 050-092(0484,INST49),SOFVMA05,XTRACT,VALO,IGG0CLE3 >>IGD07001I GDG ROLL IN ERROR - RETURN CODE 50 REASON CODE 0 MODULE >>IGD104I DATAALL.REND.PC5.PROD.VMAXTD.G0593V00 RETAINED, D >>I ran a diagnose on the volume (compared catalog with vvds and vvds with >>the catalog) but no errors were found catalog. The job creates a gdg with >>a limit of 40 generations. I am not sure why this error occurred. Any >>suggestions? >> -- 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: CATALOG ERROR
Esmie, If I were you, I would open an ETR with IBM. At this point you are being pulled in several directions by well meaning persons on this list. The inability to catalog a new generation of a GDG has nothing to do with whether a dataset has been migrated or not. Check with IBM. They wrote the code that produced the message. -- 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: CATALOG ERROR
Reynalodo, The management class is NOMIGRATE. The user didn't want the dsns migrated because he views them daily to compile reports. Also, a new gdg is created daily. reynaldo nobre muntoreanu <[EMAIL PROTECTED]> wrote: Esmie If the dataset is under control of DFSMSHSM, check the values for the attributes GDS defined in MGMTCLAS. Verify itself trials involved without the duty permission exist RACF, of access update upon I cataloguing. RMUNTOR 2007/1/16, esmie moo : > > Thanks John. Yes, I noticed that the catalog entry was present. I then > scratched the entry (del noscr). But I cannot understand why this > happened. I checked the syslog but found nothing that would indicate any > type of a problem. Any other suggestions? > > John Kington wrote: >My job put out the > following error: > > IEC331I 042-006(04280039),JS3BATCH,SOFVMA05,SCRT,IGG0CLH0 > IEC331I VOL,INST49,NAME,DATAALL.REND.PC5.PROD.VMAXTD.G0553V00 > IEC331I 050-092(0484,INST49),SOFVMA05,XTRACT,VALO,IGG0CLE3 > IGD07001I GDG ROLL IN ERROR - RETURN CODE 50 REASON CODE 0 MODULE > IGD104I DATAALL.REND.PC5.PROD.VMAXTD.G0593V00 RETAINED, D > I ran a diagnose on the volume (compared catalog with vvds and vvds with > the catalog) but no errors were found catalog. The job creates a gdg with > a limit of 40 generations. I am not sure why this error occurred. Any > suggestions? > > > Esmie, > It looks like you failed to scratch the oldest generation so that you > could > roll the new generation into the GDG. Check the oldest generation and > verify that the volume where it resides is online. > > Regards, > John > > -- > 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 > > > > - > Now you can have a huge leap forward in email: get the new Yahoo! Mail. > > -- > 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 - The best gets better. See why everyone is raving about the All-new Yahoo! Mail. -- 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: CATALOG ERROR
The dsn is created on dasd and SMS managed. I checked the disk status and it is always online. The job creates the dsn in the SMS pool which has 23 dasds in that storage pool. John Kington <[EMAIL PROTECTED]> wrote: Keeping with top posting: Esmie, Do you recall whether the oldest generation was on dasd or tape? The scratch error indicates that it was dasd and the volume was not online. Maybe you reclaimed a dasd volume or have a dasd volume offline? Regards, John >Thanks John. Yes, I noticed that the catalog entry was present. I then scratched the entry (del noscr). But I >cannot understand why this happened. I checked the syslog but found nothing that would indicate any type of a >problem. Any other suggestions? >>John Kington wrote: >My job put out the following error: >>IEC331I 042-006(04280039),JS3BATCH,SOFVMA05,SCRT,IGG0CLH0 >>IEC331I VOL,INST49,NAME,DATAALL.REND.PC5.PROD.VMAXTD.G0553V00 >>IEC331I 050-092(0484,INST49),SOFVMA05,XTRACT,VALO,IGG0CLE3 >>IGD07001I GDG ROLL IN ERROR - RETURN CODE 50 REASON CODE 0 MODULE >>IGD104I DATAALL.REND.PC5.PROD.VMAXTD.G0593V00 RETAINED, D >>I ran a diagnose on the volume (compared catalog with vvds and vvds with >>the catalog) but no errors were found catalog. The job creates a gdg with >>a limit of 40 generations. I am not sure why this error occurred. Any >>suggestions? >> >Esmie, >It looks like you failed to scratch the oldest generation so that you could >roll the new generation into the GDG. Check the oldest generation and >verify that the volume where it resides is online. -- 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 - Ask a question on any topic and get answers from real people. Go to Yahoo! Answers. -- 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: CATALOG ERROR
John, I did a listcat of the GDG base and it has a limit of 40 with SCRATCH and NOEMPTY parms. John Kington <[EMAIL PROTECTED]> wrote: >Do you have noscratch specified in the GDG define? It should be scratch to have the oldest gdg automatically roll off to allow the next generation to be catalogued. The listcat should look as follows: ATTRIBUTES LIMIT-10 SCRATCH NOEMPTY David, He must have had scratch in the GDG or the job would not have had a problem cataloging the new GDS. I do not have DFHSM so I don't know how management class attributes work in this situation. Regards, John -- 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 - Share your photos with the people who matter at Yahoo! Canada Photos -- 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: CATALOG ERROR
The index limit is built for 40. I checked the production run from the past 2 days and everything seems to be in order. I am still stumped as to what had happened. "O'Brien, David W. (NIH/CIT) [C]" <[EMAIL PROTECTED]> wrote: No, if noscratch was specified and the gdg wrapped around then the dataset would not be able to roll in. Esmie, how many catalog entries exist under the base gdg name? Just do a 3.4 display under ispf. From: John Kington [mailto:[EMAIL PROTECTED] Sent: Tue 1/16/2007 8:36 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: CATALOG ERROR >Do you have noscratch specified in the GDG define? It should be scratch to have the oldest gdg automatically roll off to allow the next generation to be catalogued. The listcat should look as follows: ATTRIBUTES LIMIT-10 SCRATCH NOEMPTY David, He must have had scratch in the GDG or the job would not have had a problem cataloging the new GDS. I do not have DFHSM so I don't know how management class attributes work in this situation. Regards, John -- 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 - The best gets better. See why everyone is raving about the All-new Yahoo! Mail. -- 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: CATALOG ERROR
Tom Marchant wrote: The oldest GDS will roll off regardless of SCRATCH. If neither SCRATCH nor EMPTY is specified, the oldest GDS will be in rolled-out status and will no longer be part of the GDG. In the pre-SMS days it would have been uncataloged but not scratched. That said, I agree with David that *the GDG should be defined with SCRATCH. * This seems to be one of those weird SMS scenarios that crop up from time to time; either you spend "days" trying to work out exactly what caused the problem or you correct the problem by normal means and assume that this was an unforeseen situation caused when X and Y happened at the same time that SMS or HSM was doing Z. NOSCRATCH might be useful if you easily need to process a GDG after the limit on the rolled-in GDSes has been exceeded following a failure where you are processing data that arrives at +1. Also there is a limit in the number of GDS names that can exist: http://www-1.ibm.com/support/docview.wss?uid=isg1II07276 and peculiar effects can be observed if you have "holes" in your GDS numbers. This is how we discovered that our SMS settings for GDGs and/or GDSes were wrong. -- 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: CATALOG ERROR
No, if noscratch was specified and the gdg wrapped around then the dataset would not be able to roll in. Esmie, how many catalog entries exist under the base gdg name? Just do a 3.4 display under ispf. From: John Kington [mailto:[EMAIL PROTECTED] Sent: Tue 1/16/2007 8:36 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: CATALOG ERROR >Do you have noscratch specified in the GDG define? It should be scratch to have the oldest gdg automatically roll off to allow the next generation to be catalogued. The listcat should look as follows: ATTRIBUTES LIMIT-10 SCRATCH NOEMPTY David, He must have had scratch in the GDG or the job would not have had a problem cataloging the new GDS. I do not have DFHSM so I don't know how management class attributes work in this situation. Regards, John -- 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: CATALOG ERROR
>Do you have noscratch specified in the GDG define? It should be scratch to have the oldest gdg automatically roll off to allow the next generation to be catalogued. The listcat should look as follows: ATTRIBUTES LIMIT-10 SCRATCH NOEMPTY David, He must have had scratch in the GDG or the job would not have had a problem cataloging the new GDS. I do not have DFHSM so I don't know how management class attributes work in this situation. Regards, John -- 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: CATALOG ERROR
Thanks Tom, I mis-spoke. Dave From: Tom Marchant [mailto:[EMAIL PROTECTED] Sent: Tue 1/16/2007 8:19 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: CATALOG ERROR On Tue, 16 Jan 2007 07:37:25 -0500, O'Brien, David W. (NIH/CIT) [C] wrote: > >Do you have noscratch specified in the GDG define? It should be >scratch to have the oldest gdg automatically roll off to allow the >next generation to be catalogued. > The oldest GDS will roll off regardless of SCRATCH. If neither SCRATCH nor EMPTY is specified, the oldest GDS will be in rolled-out status and will no longer be part of the GDG. In the pre-SMS days it would have been uncataloged but not scratched. That said, I agree with David that the GDG should be defined with SCRATCH. -- Tom Marchant -- 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: CATALOG ERROR
Keeping with top posting: Esmie, Do you recall whether the oldest generation was on dasd or tape? The scratch error indicates that it was dasd and the volume was not online. Maybe you reclaimed a dasd volume or have a dasd volume offline? Regards, John >Thanks John. Yes, I noticed that the catalog entry was present. I then scratched the entry (del noscr). But I >cannot understand why this happened. I checked the syslog but found nothing that would indicate any type of a >problem. Any other suggestions? >>John Kington <[EMAIL PROTECTED]> wrote: >My job put out the following error: >>IEC331I 042-006(04280039),JS3BATCH,SOFVMA05,SCRT,IGG0CLH0 >>IEC331I VOL,INST49,NAME,DATAALL.REND.PC5.PROD.VMAXTD.G0553V00 >>IEC331I 050-092(0484,INST49),SOFVMA05,XTRACT,VALO,IGG0CLE3 >>IGD07001I GDG ROLL IN ERROR - RETURN CODE 50 REASON CODE 0 MODULE >>IGD104I DATAALL.REND.PC5.PROD.VMAXTD.G0593V00 RETAINED, D >>I ran a diagnose on the volume (compared catalog with vvds and vvds with >>the catalog) but no errors were found catalog. The job creates a gdg with >>a limit of 40 generations. I am not sure why this error occurred. Any >>suggestions? >> >Esmie, >It looks like you failed to scratch the oldest generation so that you could >roll the new generation into the GDG. Check the oldest generation and >verify that the volume where it resides is online. -- 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: CATALOG ERROR
On Tue, 16 Jan 2007 07:37:25 -0500, O'Brien, David W. (NIH/CIT) [C] wrote: > >Do you have noscratch specified in the GDG define? It should be >scratch to have the oldest gdg automatically roll off to allow the >next generation to be catalogued. > The oldest GDS will roll off regardless of SCRATCH. If neither SCRATCH nor EMPTY is specified, the oldest GDS will be in rolled-out status and will no longer be part of the GDG. In the pre-SMS days it would have been uncataloged but not scratched. That said, I agree with David that the GDG should be defined with SCRATCH. -- Tom Marchant -- 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: CATALOG ERROR
Esmie If the dataset is under control of DFSMSHSM, check the values for the attributes GDS defined in MGMTCLAS. Verify itself trials involved without the duty permission exist RACF, of access update upon I cataloguing. RMUNTOR 2007/1/16, esmie moo <[EMAIL PROTECTED]>: Thanks John. Yes, I noticed that the catalog entry was present. I then scratched the entry (del noscr). But I cannot understand why this happened. I checked the syslog but found nothing that would indicate any type of a problem. Any other suggestions? John Kington <[EMAIL PROTECTED]> wrote: >My job put out the following error: IEC331I 042-006(04280039),JS3BATCH,SOFVMA05,SCRT,IGG0CLH0 IEC331I VOL,INST49,NAME,DATAALL.REND.PC5.PROD.VMAXTD.G0553V00 IEC331I 050-092(0484,INST49),SOFVMA05,XTRACT,VALO,IGG0CLE3 IGD07001I GDG ROLL IN ERROR - RETURN CODE 50 REASON CODE 0 MODULE IGD104I DATAALL.REND.PC5.PROD.VMAXTD.G0593V00 RETAINED, D I ran a diagnose on the volume (compared catalog with vvds and vvds with the catalog) but no errors were found catalog. The job creates a gdg with a limit of 40 generations. I am not sure why this error occurred. Any suggestions? > Esmie, It looks like you failed to scratch the oldest generation so that you could roll the new generation into the GDG. Check the oldest generation and verify that the volume where it resides is online. Regards, John -- 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 - Now you can have a huge leap forward in email: get the new Yahoo! Mail. -- 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: CATALOG ERROR
If your gdg is sms managed then the management class should be specified as follows: GDG Management Attributes # GDG Elements on Primary : 6 or any number to avoid undue recalls Rolled-off GDS Action . . : EXPIRE From: esmie moo [mailto:[EMAIL PROTECTED] Sent: Tue 1/16/2007 7:11 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: CATALOG ERROR Thanks John. Yes, I noticed that the catalog entry was present. I then scratched the entry (del noscr). But I cannot understand why this happened. I checked the syslog but found nothing that would indicate any type of a problem. Any other suggestions? John Kington <[EMAIL PROTECTED]> wrote: >My job put out the following error: IEC331I 042-006(04280039),JS3BATCH,SOFVMA05,SCRT,IGG0CLH0 IEC331I VOL,INST49,NAME,DATAALL.REND.PC5.PROD.VMAXTD.G0553V00 IEC331I 050-092(0484,INST49),SOFVMA05,XTRACT,VALO,IGG0CLE3 IGD07001I GDG ROLL IN ERROR - RETURN CODE 50 REASON CODE 0 MODULE IGD104I DATAALL.REND.PC5.PROD.VMAXTD.G0593V00 RETAINED, D I ran a diagnose on the volume (compared catalog with vvds and vvds with the catalog) but no errors were found catalog. The job creates a gdg with a limit of 40 generations. I am not sure why this error occurred. Any suggestions? > Esmie, It looks like you failed to scratch the oldest generation so that you could roll the new generation into the GDG. Check the oldest generation and verify that the volume where it resides is online. Regards, John -- 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 - Now you can have a huge leap forward in email: get the new Yahoo! Mail. -- 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: CATALOG ERROR
Esmie, Do you have noscratch specified in the GDG define? It should be scratch to have the oldest gdg automatically roll off to allow the next generation to be catalogued. The listcat should look as follows: ATTRIBUTES LIMIT-10 SCRATCH NOEMPTY From: esmie moo [mailto:[EMAIL PROTECTED] Sent: Tue 1/16/2007 7:11 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: CATALOG ERROR Thanks John. Yes, I noticed that the catalog entry was present. I then scratched the entry (del noscr). But I cannot understand why this happened. I checked the syslog but found nothing that would indicate any type of a problem. Any other suggestions? John Kington <[EMAIL PROTECTED]> wrote: >My job put out the following error: IEC331I 042-006(04280039),JS3BATCH,SOFVMA05,SCRT,IGG0CLH0 IEC331I VOL,INST49,NAME,DATAALL.REND.PC5.PROD.VMAXTD.G0553V00 IEC331I 050-092(0484,INST49),SOFVMA05,XTRACT,VALO,IGG0CLE3 IGD07001I GDG ROLL IN ERROR - RETURN CODE 50 REASON CODE 0 MODULE IGD104I DATAALL.REND.PC5.PROD.VMAXTD.G0593V00 RETAINED, D I ran a diagnose on the volume (compared catalog with vvds and vvds with the catalog) but no errors were found catalog. The job creates a gdg with a limit of 40 generations. I am not sure why this error occurred. Any suggestions? > Esmie, It looks like you failed to scratch the oldest generation so that you could roll the new generation into the GDG. Check the oldest generation and verify that the volume where it resides is online. Regards, John -- 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 - Now you can have a huge leap forward in email: get the new Yahoo! Mail. -- 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: CATALOG ERROR
Thanks John. Yes, I noticed that the catalog entry was present. I then scratched the entry (del noscr). But I cannot understand why this happened. I checked the syslog but found nothing that would indicate any type of a problem. Any other suggestions? John Kington <[EMAIL PROTECTED]> wrote: >My job put out the following error: IEC331I 042-006(04280039),JS3BATCH,SOFVMA05,SCRT,IGG0CLH0 IEC331I VOL,INST49,NAME,DATAALL.REND.PC5.PROD.VMAXTD.G0553V00 IEC331I 050-092(0484,INST49),SOFVMA05,XTRACT,VALO,IGG0CLE3 IGD07001I GDG ROLL IN ERROR - RETURN CODE 50 REASON CODE 0 MODULE IGD104I DATAALL.REND.PC5.PROD.VMAXTD.G0593V00 RETAINED, D I ran a diagnose on the volume (compared catalog with vvds and vvds with the catalog) but no errors were found catalog. The job creates a gdg with a limit of 40 generations. I am not sure why this error occurred. Any suggestions? > Esmie, It looks like you failed to scratch the oldest generation so that you could roll the new generation into the GDG. Check the oldest generation and verify that the volume where it resides is online. Regards, John -- 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 - Now you can have a huge leap forward in email: get the new Yahoo! Mail. -- 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: CATALOG ERROR
>My job put out the following error: IEC331I 042-006(04280039),JS3BATCH,SOFVMA05,SCRT,IGG0CLH0 IEC331I VOL,INST49,NAME,DATAALL.REND.PC5.PROD.VMAXTD.G0553V00 IEC331I 050-092(0484,INST49),SOFVMA05,XTRACT,VALO,IGG0CLE3 IGD07001I GDG ROLL IN ERROR - RETURN CODE 50 REASON CODE 0 MODULE IGD104I DATAALL.REND.PC5.PROD.VMAXTD.G0593V00RETAINED, D I ran a diagnose on the volume (compared catalog with vvds and vvds with the catalog) but no errors were found catalog. The job creates a gdg with a limit of 40 generations. I am not sure why this error occurred. Any suggestions? > Esmie, It looks like you failed to scratch the oldest generation so that you could roll the new generation into the GDG. Check the oldest generation and verify that the volume where it resides is online. Regards, John -- 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
CATALOG ERROR
My job put out the following error: IEC331I 042-006(04280039),JS3BATCH,SOFVMA05,SCRT,IGG0CLH0 IEC331I VOL,INST49,NAME,DATAALL.REND.PC5.PROD.VMAXTD.G0553V00 IEC331I 050-092(0484,INST49),SOFVMA05,XTRACT,VALO,IGG0CLE3 IGD07001I GDG ROLL IN ERROR - RETURN CODE 50 REASON CODE 0 MODULE IGD104I DATAALL.REND.PC5.PROD.VMAXTD.G0593V00RETAINED, D I ran a diagnose on the volume (compared catalog with vvds and vvds with the catalog) but no errors were found catalog. The job creates a gdg with a limit of 40 generations. I am not sure why this error occurred. Any suggestions? Thanks in advance. - Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail -- 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: CATALOG ERROR - Defining VVDS
I took a look at a few here and they are small than my CYL(5,1) and I know we have at least Mod-27s. DR is a consideration about size. Does your DR service provider support them?? Bob Richards -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Darth Keller Sent: Monday, September 18, 2006 2:02 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: CATALOG ERROR - Defining VVDS Now there's a timely question! >>For the record, I have used CYL(5,1) for the last 15 years. I may need >>to consider upping that for Mod-27s and -54s. What are others using >>these days on the large volumes? We're going through a bid process for new DASD right now. We'll be moving from 3 Sun V2X's to a single box. I have a boss who I've argued with, cajoled, and just generally lambasted for 5 years or so trying to wean him away from mod-3's. While I've gotten him to allow me mod-9's in limited application, it's been a struggle. But now with the new box coming in, something has happened and all of a sudden he's talking -27's and -54's with PAV's and such! So I'm also wondering what other's are using on the larger volumes and what kinds of gotcha's might be waiting for me. LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. Seeing Beyond Money is a service mark of SunTrust Banks, Inc. [ST:XCL] -- 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: CATALOG ERROR - Defining VVDS
>For the record, I am no spring chicken either. I have hit the 50+ age >bracket, needless to say not only the gray cells are graying. The only people in IT, that I work with, that are even close to my age, are the mainframers. I'm old enough to be the father of the IT people responsible for the toys. In a lot of cases, I'm older than their fathers. When in doubt. PANIC!! -- 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: CATALOG ERROR - Defining VVDS
>I can live with that (vvds in extents). It is a user test volume. I do not have exclusive ownership of that canine. But, I would have one canned job that inits all general storage volumes the same. Putting all the VTOC, VTOCIX, VVDS (and CATALOGUE if it exists) at the front with a standard size based on the size of the volume. I would not make a distinction based on prod/test. I may based on system, spool, page, database, etc. But, as we dumb down the sysprog and the storage admin, I would leave less and less decisions out there to make. Also, I have seen system volumes re-claimed to use as user volumes and watch batch croak due to a single track VTOC. At the cost of DASD, these days, I would init even system volumes with them all. When in doubt. PANIC!! -- 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: CATALOG ERROR - Defining VVDS
So with the default of TRK(10,10), the VVDS goes into secondary extents on a volume with a lot of VSAM (the volume size is irrelevant, only the numer of clusters). The VVDS can go to 123 extents, and there is no problem if it does so. There is no performance hit or other problems. So the default is fine unless you expect a HUGE number of very small clusters. -- Bruce A. Black Senior Software Developer for FDR Innovation Data Processing 973-890-7300 personal: [EMAIL PROTECTED] sales info: [EMAIL PROTECTED] tech support: [EMAIL PROTECTED] web: www.innovationdp.fdr.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: CATALOG ERROR - Defining VVDS
Now there's a timely question! >>For the record, I have used CYL(5,1) for the last 15 years. I may need >>to consider upping that for Mod-27s and -54s. What are others using >>these days on the large volumes? We're going through a bid process for new DASD right now. We'll be moving from 3 Sun V2X's to a single box. I have a boss who I've argued with, cajoled, and just generally lambasted for 5 years or so trying to wean him away from mod-3's. While I've gotten him to allow me mod-9's in limited application, it's been a struggle. But now with the new box coming in, something has happened and all of a sudden he's talking -27's and -54's with PAV's and such! So I'm also wondering what other's are using on the larger volumes and what kinds of gotcha's might be waiting for me. ddkeller ** This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. ** -- 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: CATALOG ERROR - Defining VVDS
For the record, I have used CYL(5,1) for the last 15 years. I may need to consider upping that for Mod-27s and -54s. What are others using these days on the large volumes? Willie, the CONVERTV suggestion was a good one if you can't find a period of light allocation activity. Bob Richards -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of willie bunter Sent: Monday, September 18, 2006 11:59 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: CATALOG ERROR - Defining VVDS David, I can live with that (vvds in extents). It is a user test volume. I will have to examine the process of allocating a vvds in the same job as the initialize of the volume. This would save a lot of headaches. LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. Seeing Beyond Money is a service mark of SunTrust Banks, Inc. [ST:XCL] -- 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: CATALOG ERROR - Defining VVDS
Tom, Okay, my misinterpretation of what you said. No apologies necessary, except from me for my bad attempt at humor. Maybe there is a good reason why I typed that response and then went to a Toastmasters meeting as a first-time guest. I absolutely need to work on my communications skills! :-) By the way, for those interested, the Toastmasters club looks like a winner for anyone looking to improve how they come across to others. I like to talk so it shouldn't be a huge stretch for me! But then again, they get to rag, er "evaluate" you and your speech. Sounds like fun! And in closing, yes, Willie needs to read more...as we all do. Bob Richards -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Tom Marchant Sent: Monday, September 18, 2006 11:57 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: CATALOG ERROR - Defining VVDS Sorry, Bob... I meant to say that Willie needs to RTFB and consider all data sets. I know you were trying to help. The book goes into considerable detail about how to figure space requirements. LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. Seeing Beyond Money is a service mark of SunTrust Banks, Inc. [ST:XCL] -- 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: CATALOG ERROR - Defining VVDS
On Mon, 18 Sep 2006 09:04:01 -0700, willie bunter <[EMAIL PROTECTED]> wrote: >I am not sure what RTFB. However, how do I go about doing it... Read the book. Some people use RTFM (Manual). -- 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: CATALOG ERROR - Defining VVDS
On Mon, 18 Sep 2006 16:01:06 +, Ted MacNEIL <[EMAIL PROTECTED]> wrote: >>It's been so long since it was (4 4). I don't even remember when the >>default changed. I want to say that it's about the time SMS first >>became available. > > >I never saw the update, but even (10 10) is too small on larger volumes. Maybe. How much space do your biggest VVDSes use? Tom Marchant -- 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: CATALOG ERROR - Defining VVDS
I am not sure what RTFB. However, how do I go about doing it... "Richards.Bob" <[EMAIL PROTECTED]> wrote: Well, xxxcccuuussseee me, Tom! :-) You are right of course. I would RTFB except that I am not allowed to play "storage administrator" anymore. I was just trying to be helpful to Willie. When my memory fades a little more on storage management issues, I'll stop answering those questions and leave to you young-uns to answer! Bob Richards -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Tom Marchant Sent: Monday, September 18, 2006 11:43 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: CATALOG ERROR - Defining VVDS Snippage Stop thinking only of VSAM! On an SMS managed volume, ALL data sets have an entry in the VVDS. The default allocation is 10 tracks primary and 10 tracks secondary. You need to RTFB in Managing catalogs. A KSDS needs 530 bytes. Non-VSAM needs 100 bytes. If you have SMS volumes that are used for similar data sets, you might be able to get an idea by looking at their VVDSes. LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. Seeing Beyond Money is a service mark of SunTrust Banks, Inc. [ST:XCL] -- 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 - Get your email and more, right on the new 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: CATALOG ERROR - Defining VVDS
To answer Bob, thanks for being very helpful. For the record, I am no spring chicken either. I have hit the 50+ age bracket, needless to say not only the gray cells are graying. Thanks again. Tom Marchant <[EMAIL PROTECTED]> wrote: Sorry, Bob... I meant to say that Willie needs to RTFB and consider all data sets. I know you were trying to help. The book goes into considerable detail about how to figure space requirements. Tom Marchant On Mon, 18 Sep 2006 11:49:02 -0400, Richards.Bob wrote: >Well, xxxcccuuussseee me, Tom! :-) > >You are right of course. I would RTFB except that I am not allowed to >play "storage administrator" anymore. I was just trying to be helpful to >Willie. When my memory fades a little more on storage management issues, >I'll stop answering those questions and leave to you young-uns to >answer! > >Bob Richards > > >-Original Message- >From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On >Behalf Of Tom Marchant >Sent: Monday, September 18, 2006 11:43 AM >To: IBM-MAIN@BAMA.UA.EDU >Subject: Re: CATALOG ERROR - Defining VVDS > >Snippage > >Stop thinking only of VSAM! > >On an SMS managed volume, ALL data sets have an entry in the VVDS. > >The default allocation is 10 tracks primary and 10 tracks secondary. > >You need to RTFB in Managing catalogs. A KSDS needs 530 bytes. >Non-VSAM needs 100 bytes. If you have SMS volumes that are used >for similar data sets, you might be able to get an idea by looking >at their VVDSes. > -- 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 - Get your email and more, right on the new 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: CATALOG ERROR - Defining VVDS
>It's been so long since it was (4 4). I don't even remember when the default >changed. I want to say that it's about the time SMS first became available. I never saw the update, but even (10 10) is too small on larger volumes. When in doubt. PANIC!! -- 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: CATALOG ERROR - Defining VVDS
David, I can live with that (vvds in extents). It is a user test volume. I will have to examine the process of allocating a vvds in the same job as the initialize of the volume. This would save a lot of headaches. Thanks for the reassurance and advice from all. "O'Brien, David W. (NIH/CIT) [C]" <[EMAIL PROTECTED]> wrote: Willie, CI size for the VVDS is 4096. For 10 trks that computes to 120 CIs in the VVDS. For a SMS managed volume each file will require the following # of bytes: KSDS 530 ESDS 370 Linear 340 Non-VSAM 100 I suspect you're not going to have a problem. Worst case your VVDS goes into extents. -- 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 - Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2¢/min or less. -- 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: CATALOG ERROR - Defining VVDS
Sorry, Bob... I meant to say that Willie needs to RTFB and consider all data sets. I know you were trying to help. The book goes into considerable detail about how to figure space requirements. Tom Marchant On Mon, 18 Sep 2006 11:49:02 -0400, Richards.Bob <[EMAIL PROTECTED]> wrote: >Well, xxxcccuuussseee me, Tom! :-) > >You are right of course. I would RTFB except that I am not allowed to >play "storage administrator" anymore. I was just trying to be helpful to >Willie. When my memory fades a little more on storage management issues, >I'll stop answering those questions and leave to you young-uns to >answer! > >Bob Richards > > >-Original Message- >From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On >Behalf Of Tom Marchant >Sent: Monday, September 18, 2006 11:43 AM >To: IBM-MAIN@BAMA.UA.EDU >Subject: Re: CATALOG ERROR - Defining VVDS > >Snippage > >Stop thinking only of VSAM! > >On an SMS managed volume, ALL data sets have an entry in the VVDS. > >The default allocation is 10 tracks primary and 10 tracks secondary. > >You need to RTFB in Managing catalogs. A KSDS needs 530 bytes. >Non-VSAM needs 100 bytes. If you have SMS volumes that are used >for similar data sets, you might be able to get an idea by looking >at their VVDSes. > -- 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: CATALOG ERROR - Defining VVDS
Willie, CI size for the VVDS is 4096. For 10 trks that computes to 120 CIs in the VVDS. For a SMS managed volume each file will require the following # of bytes: KSDS 530 ESDS 370 Linear 340 Non-VSAM 100 I suspect you're not going to have a problem. Worst case your VVDS goes into extents. -- 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: CATALOG ERROR - Defining VVDS
Well, xxxcccuuussseee me, Tom! :-) You are right of course. I would RTFB except that I am not allowed to play "storage administrator" anymore. I was just trying to be helpful to Willie. When my memory fades a little more on storage management issues, I'll stop answering those questions and leave to you young-uns to answer! Bob Richards -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Tom Marchant Sent: Monday, September 18, 2006 11:43 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: CATALOG ERROR - Defining VVDS Snippage Stop thinking only of VSAM! On an SMS managed volume, ALL data sets have an entry in the VVDS. The default allocation is 10 tracks primary and 10 tracks secondary. You need to RTFB in Managing catalogs. A KSDS needs 530 bytes. Non-VSAM needs 100 bytes. If you have SMS volumes that are used for similar data sets, you might be able to get an idea by looking at their VVDSes. LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. Seeing Beyond Money is a service mark of SunTrust Banks, Inc. [ST:XCL] -- 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: CATALOG ERROR - Defining VVDS
On Mon, 18 Sep 2006 08:13:55 -0700, willie bunter <[EMAIL PROTECTED]> wrote: >The user is not sure. I checked and the VVDS is at 10 trks (default?). How many VSAMS dsns can this accomodate? > >"Richards.Bob" <[EMAIL PROTECTED]> wrote: Willie, > >DO NOT DELETE THAT VVDS unless you can empty that volume! > >Besides, how many VSAM datasets do you plan to allocate there that the >defaults are not enough? Stop thinking only of VSAM! On an SMS managed volume, ALL data sets have an entry in the VVDS. The default allocation is 10 tracks primary and 10 tracks secondary. You need to RTFB in Managing catalogs. A KSDS needs 530 bytes. Non-VSAM needs 100 bytes. If you have SMS volumes that are used for similar data sets, you might be able to get an idea by looking at their VVDSes. Tom Marchant -- 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: CATALOG ERROR - Defining VVDS
You still could be fine. But, what the heck, if it were me, I'd probably just put up another volume the way I wanted it to be and move all datasets off the one with the small VVDS (and re-init the first volume). Yes, I can be anal at times. I suppose an ounce of problem prevention is easier than a pound of problem resolution. Bob Richards -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of willie bunter Sent: Monday, September 18, 2006 11:34 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: CATALOG ERROR - Defining VVDS Bad news it is. It is a 3390-9. "Richards.Bob" <[EMAIL PROTECTED]> wrote: Not sure I know the answer to that, but unless this volume is larger than a 3390-3, you are probably fine. Bob Richards Search the archives at http://bama.ua.edu/archives/ibm-main.html LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. Seeing Beyond Money is a service mark of SunTrust Banks, Inc. [ST:XCL] -- 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: CATALOG ERROR - Defining VVDS
Bad news it is. It is a 3390-9. "Richards.Bob" <[EMAIL PROTECTED]> wrote: Not sure I know the answer to that, but unless this volume is larger than a 3390-3, you are probably fine. Bob Richards -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of willie bunter Sent: Monday, September 18, 2006 11:14 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: CATALOG ERROR - Defining VVDS The user is not sure. I checked and the VVDS is at 10 trks (default?). How many VSAMS dsns can this accomodate? "Richards.Bob" wrote: Willie, DO NOT DELETE THAT VVDS unless you can empty that volume! Besides, how many VSAM datasets do you plan to allocate there that the defaults are not enough? Bob Richards LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. Seeing Beyond Money is a service mark of SunTrust Banks, Inc. [ST:XCL] -- 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 - Get your email and more, right on the new 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: CATALOG ERROR - Defining VVDS
Not sure I know the answer to that, but unless this volume is larger than a 3390-3, you are probably fine. Bob Richards -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of willie bunter Sent: Monday, September 18, 2006 11:14 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: CATALOG ERROR - Defining VVDS The user is not sure. I checked and the VVDS is at 10 trks (default?). How many VSAMS dsns can this accomodate? "Richards.Bob" <[EMAIL PROTECTED]> wrote: Willie, DO NOT DELETE THAT VVDS unless you can empty that volume! Besides, how many VSAM datasets do you plan to allocate there that the defaults are not enough? Bob Richards LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. Seeing Beyond Money is a service mark of SunTrust Banks, Inc. [ST:XCL] -- 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: CATALOG ERROR - Defining VVDS
The user is not sure. I checked and the VVDS is at 10 trks (default?). How many VSAMS dsns can this accomodate? "Richards.Bob" <[EMAIL PROTECTED]> wrote: Willie, DO NOT DELETE THAT VVDS unless you can empty that volume! Besides, how many VSAM datasets do you plan to allocate there that the defaults are not enough? Bob Richards -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of willie bunter Sent: Monday, September 18, 2006 10:53 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: CATALOG ERROR - Defining VVDS Since the VVDS entry is there can I expand it? Or do I have to delete it and retry the allocation? LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. Seeing Beyond Money is a service mark of SunTrust Banks, Inc. [ST:XCL] -- 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 - All-new Yahoo! Mail - Fire up a more powerful email and get things done faster. -- 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: CATALOG ERROR - Defining VVDS
Willie, DO NOT DELETE THAT VVDS unless you can empty that volume! Besides, how many VSAM datasets do you plan to allocate there that the defaults are not enough? Bob Richards -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of willie bunter Sent: Monday, September 18, 2006 10:53 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: CATALOG ERROR - Defining VVDS Since the VVDS entry is there can I expand it? Or do I have to delete it and retry the allocation? LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. Seeing Beyond Money is a service mark of SunTrust Banks, Inc. [ST:XCL] -- 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: CATALOG ERROR - Defining VVDS
Since the VVDS entry is there can I expand it? Or do I have to delete it and retry the allocation? Tom Marchant <[EMAIL PROTECTED]> wrote: On Mon, 18 Sep 2006 14:12:15 +, Ted MacNEIL wrote: > >The equivalent of SPACE=(TRK,(4,4)) is used. Ancient history! Tracks(10 10) It's been so long since it was (4 4). I don't even remember when the default changed. I want to say that it's about the time SMS first became available. -- 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 - Stay in the know. Pulse on the new Yahoo.com. Check it out. -- 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: CATALOG ERROR - Defining VVDS
On Mon, 18 Sep 2006 14:12:15 +, Ted MacNEIL <[EMAIL PROTECTED]> wrote: > >The equivalent of SPACE=(TRK,(4,4)) is used. Ancient history! Tracks(10 10) It's been so long since it was (4 4). I don't even remember when the default changed. I want to say that it's about the time SMS first became available. -- 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: CATALOG ERROR - Defining VVDS
According to the z/OS V1R7.0 Managing Catalogs manual: "Explicitly defining a VVDS is usually appropriate when you are initializing a new volume. If you are not running SMS, and a volume already contains some non-VSAM data sets, it is appropriate to allow the VVDS to be defined implicitly with the default space allocation of TRACKS(10 10)." http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2c140/3.6?SHEL F=&DT=20050616141325 Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List On Behalf Of Ted MacNEIL Sent: Monday, September 18, 2006 9:12 AM >Yes, the first time a data set gets placed on an SMS-managed volume, a VVDS will be created if one does not already exist. (This is true whether the data set is VSAM or not.) The equivalent of SPACE=(TRK,(4,4)) is used. This doesn't get you much on large packs. As of January 1, 2007, Ben E. Keith Company will no longer accept emails addressed to our "bekco.com" address. Please change your information for all Ben E. Keith contacts to our new email address, "benekeith.com". Thank you. -- 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: CATALOG ERROR - Defining VVDS
>You can change it with F CATALOG,VVDSSPACE(pri,sec). This must be done at >every IPL of the system. If not, it goes back to the default. That's why I prefer it to be part of initialising DASD. When in doubt. PANIC!! -- 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: CATALOG ERROR - Defining VVDS
You can INIT the volume without the STORAGEGROUP option, Define the VVDS, CONVERTV the volume. This takes no time at all to do. If you are Z/OS 1.7 you can change the default VVDS space. F CATALOG,REPORT will show you what VVDS SPACE is set at. You can change it with F CATALOG,VVDSSPACE(pri,sec). This must be done at every IPL of the system. If not, it goes back to the default. Richard Habres AVP; Enterprise Storage Technology Merrill Lynch -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Friske, Michael Sent: Monday, September 18, 2006 10:01 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: CATALOG ERROR - Defining VVDS Initialize the volume, vary it online, define the VVDS, and then add it to the SMS configuration. If it has not been added to an SMS storage group, SMS will not try to allocate a data set on it. -- 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: CATALOG ERROR - Defining VVDS
>Yes, the first time a data set gets placed on an SMS-managed volume, a VVDS >will be created if one does not already exist. (This is true whether the data set is VSAM or not.) The equivalent of SPACE=(TRK,(4,4)) is used. This doesn't get you much on large packs. When in doubt. PANIC!! -- 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: CATALOG ERROR - Defining VVDS
Initialize the volume, vary it online, define the VVDS, and then add it to the SMS configuration. If it has not been added to an SMS storage group, SMS will not try to allocate a data set on it. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of willie bunter Sent: Monday, September 18, 2006 7:14 AM To: IBM-MAIN@BAMA.UA.EDU Subject: CATALOG ERROR - Defining VVDS Good Day, I encountered the following error while I was attempting to define the VVDS on a 3390-9 disk which is SMS managed: IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE IS 50 - REASON CODE IS IGG0CLE3-8 IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12 I checked the error code and it points out to the fact that "a VVDS already exists on the volume" I am not sure how that can happen because I initialized the volume (ICKDSF) and put it online and attempted to define the VVDS. Can it be because as soon as I put the volume online a VSAM file may have been allocated on that volume? If so, how can I avoid this problem in the future. Here is my init job INIT - UNITADDRESS(BC50) VOLID(PAS904) - VTOC(0,1,149) - VERIFY(SPAC50) - INDEX(10,0,45) - STORAGEGROUP -- 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: CATALOG ERROR - Defining VVDS
On Mon, 18 Sep 2006 09:19:35 -0400, Dave <[EMAIL PROTECTED]> wrote: >Yes. On an SMS volume if there is no VVDS and SMS wishes to put a dsn on >the volume (that is empty...) SMS will put a VVDS on the volume for you - >albeit a tiny VVDS Tiny? It's been quite a while since I was doing dasd management, but I always preferred to let the VVDS default. I always thought the 10 track primary and secondary was plenty. In any case, as of z/OS 1.7, you can override the default space allocation for the VVDS. Tom Marchant -- 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: CATALOG ERROR - Defining VVDS
Yes, the first time a data set gets placed on an SMS-managed volume, a VVDS will be created if one does not already exist. (This is true whether the data set is VSAM or not.) Regards, Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of willie bunter Sent: Monday, September 18, 2006 7:58 AM Could the problem have been caused because a VSAM dsn was allocated on that volume as soon as I put it ONLINE? As of January 1, 2007, Ben E. Keith Company will no longer accept emails addressed to our "bekco.com" address. Please change your information for all Ben E. Keith contacts to our new email address, "benekeith.com". Thank you. -- 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: CATALOG ERROR - Defining VVDS
Yes. On an SMS volume if there is no VVDS and SMS wishes to put a dsn on the volume (that is empty...) SMS will put a VVDS on the volume for you - albeit a tiny VVDS -- 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: CATALOG ERROR - Defining VVDS
Could the problem have been caused because a VSAM dsn was allocated on that volume as soon as I put it ONLINE? "Richards.Bob" <[EMAIL PROTECTED]> wrote: Oops, I forgot. I do this in REXX and issue a Vary online from within that code and then do the define VVDS. You may want to bring the volume online at a period of low activity. Bob Richards Add the DEFINE of the VVDS as the 2nd step of your INIT jcl. Bob Richards - Get your email and more, right on the new 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: CATALOG ERROR - Defining VVDS
Oops, I forgot. I do this in REXX and issue a Vary online from within that code and then do the define VVDS. You may want to bring the volume online at a period of low activity. Bob Richards -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Richards.Bob Sent: Monday, September 18, 2006 8:43 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: CATALOG ERROR - Defining VVDS Add the DEFINE of the VVDS as the 2nd step of your INIT jcl. Bob Richards -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of willie bunter Sent: Monday, September 18, 2006 8:14 AM To: IBM-MAIN@BAMA.UA.EDU Subject: CATALOG ERROR - Defining VVDS Good Day, I encountered the following error while I was attempting to define the VVDS on a 3390-9 disk which is SMS managed: IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE IS 50 - REASON CODE IS IGG0CLE3-8 IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12 I checked the error code and it points out to the fact that "a VVDS already exists on the volume" I am not sure how that can happen because I initialized the volume (ICKDSF) and put it online and attempted to define the VVDS. Can it be because as soon as I put the volume online a VSAM file may have been allocated on that volume? If so, how can I avoid this problem in the future. Here is my init job INIT - UNITADDRESS(BC50) VOLID(PAS904) - VTOC(0,1,149) - VERIFY(SPAC50) - INDEX(10,0,45) - STORAGEGROUP LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. Seeing Beyond Money is a service mark of SunTrust Banks, Inc. [ST:XCL] -- 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: CATALOG ERROR - Defining VVDS
Add the DEFINE of the VVDS as the 2nd step of your INIT jcl. Bob Richards -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of willie bunter Sent: Monday, September 18, 2006 8:14 AM To: IBM-MAIN@BAMA.UA.EDU Subject: CATALOG ERROR - Defining VVDS Good Day, I encountered the following error while I was attempting to define the VVDS on a 3390-9 disk which is SMS managed: IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE IS 50 - REASON CODE IS IGG0CLE3-8 IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12 I checked the error code and it points out to the fact that "a VVDS already exists on the volume" I am not sure how that can happen because I initialized the volume (ICKDSF) and put it online and attempted to define the VVDS. Can it be because as soon as I put the volume online a VSAM file may have been allocated on that volume? If so, how can I avoid this problem in the future. Here is my init job INIT - UNITADDRESS(BC50) VOLID(PAS904) - VTOC(0,1,149) - VERIFY(SPAC50) - INDEX(10,0,45) - STORAGEGROUP LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. Seeing Beyond Money is a service mark of SunTrust Banks, Inc. [ST:XCL] -- 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
CATALOG ERROR - Defining VVDS
Good Day, I encountered the following error while I was attempting to define the VVDS on a 3390-9 disk which is SMS managed: IDC3014I CATALOG ERROR IDC3009I ** VSAM CATALOG RETURN CODE IS 50 - REASON CODE IS IGG0CLE3-8 IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12 I checked the error code and it points out to the fact that "a VVDS already exists on the volume" I am not sure how that can happen because I initialized the volume (ICKDSF) and put it online and attempted to define the VVDS. Can it be because as soon as I put the volume online a VSAM file may have been allocated on that volume? If so, how can I avoid this problem in the future. Here is my init job INIT - UNITADDRESS(BC50) VOLID(PAS904) - VTOC(0,1,149) - VERIFY(SPAC50) - INDEX(10,0,45) - STORAGEGROUP Thanks. - Stay in the know. Pulse on the new Yahoo.com. Check it out. -- 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
