Re: Invalid dataset name in catalog, how to remove
On Wed, 13 Aug 2008 09:58:19 -0500, Tom Marchant m42tom-
[EMAIL PROTECTED] wrote:
If all else fails, you could REPRO MERGECAT everything else to a new catalog
and delete the catalog.
If there are no other datasets beyond the valid qualifier level, you might
also
be able to REPRO MERGECAT just the bad entry into a new catalog, then
delete that new catalog:
REPRO MERGECAT LEVEL(P.FSPOL.SBHF38AA) ...
I don't think a specific entry name will work any better here than with DELETE,
i.e. -
REPRO MERGECAT ENTRIES('P.FSPOL.SBHF38AA(0)') ...
and it doesn't look like this supports masking like DELETE, either (sigh), but
I
could be wrong (it happens, I've seen me do it).
Regards,
Art Gutowski
Ford Motor Company
--
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: Invalid dataset name in catalog, how to remove
On Thu, 7 Aug 2008 23:05:24 -0500, Joel C. Ewing wrote: Ken Leidner wrote: I have a tape dataset cataloged over 10 years ago with a very strange - invalid name. I am not sure how it was created, but I would like to remove it from the catalog. The tape has scratched years ago and I found this odd dataset name and would like to remove it from the catalog without having to zap the catalog to change its name first. Any suggestions? I have tried; In TSO a DELETE 'P.FSPOL.SBHF38AA(0)' noscratch IKJ56709I INVALID DATA SET NAME, 'P.FSPOL.SBHF38AA(0)' ISMF doesn't even find the dataset, even when looking for a prefix of the dataset name (like 'P.FSPOL.SB*.**) Running IEFBR14 in batch gives //STEP0EXEC PGM=IEFBR14 //DD1 DD DSN='P.FSPOL.SBHF38AA(0)',DISP=(OLD,UNCATLG) IEF212I CJ4130BT STEP0 DD1 - DATA SET NOT FOUND It was discussed here within the past couple years that IBM has done two or three about-faces on catalog syntax rules. In the oldest implementation, such a name could never have been catalogued. At some relatively recent release, IBM relaxed the constraints so practally any 44-character string could be catalogued, although I suspect most application-level software would have intervened to enforce the classic syntax rules -- a new-style name might not be catalogable except by an assembler call to catalog services. Some customers found this newly-granted liberty psychologically disturbing (Stockholm Syndrome?) and complained to the extent that IBM provided an option to reinstate the classic syntax rules. At first, the default was lenient; in a later release the default was changed to strict. Your offending data set may have been catalogued (by an assembler program) during the interval of freedom, or the catalog may have been zapped. So, you have at least two options: re-zap the catalog, or temporarily set the option to lenient syntax (PARMLIB? restart required?) and uncatalog the data set. If you then choose to reinstitute strict checking, you can only hope that during the interim no other users have catalogued nonconforming data set names or you will once again be in a similar situation. IBM made a poor design choice in the manner of implementing the strict checking option: the existence of an object should always overrule the invalidity of its name -- if it's there, don't quibble over grammar. (I'm reminded of a Woody Allen movie in which a teller disputes a bank robber over a misspelling in the holdup note.) At the very least, access to objects with unconventional names should be allowed if only for the purpose of deleting or renaming them. -- gil -- 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: Invalid dataset name in catalog, how to remove
On Wed, 13 Aug 2008 09:13:38 -0500, Paul Gilmartin [EMAIL PROTECTED] wrote: On Thu, 7 Aug 2008 23:05:24 -0500, Joel C. Ewing wrote: Ken Leidner wrote: I have a tape dataset cataloged over 10 years ago with a very strange - invalid name. I am not sure how it was created, but I would like to remove it from the catalog. The tape has scratched years ago and I found this odd dataset name and would like to remove it from the catalog without having to zap the catalog to change its name first. Any suggestions? I have tried; In TSO a DELETE 'P.FSPOL.SBHF38AA(0)' noscratch IKJ56709I INVALID DATA SET NAME, 'P.FSPOL.SBHF38AA(0)' ISMF doesn't even find the dataset, even when looking for a prefix of the dataset name (like 'P.FSPOL.SB*.**) Running IEFBR14 in batch gives //STEP0EXEC PGM=IEFBR14 //DD1 DD DSN='P.FSPOL.SBHF38AA(0)',DISP=(OLD,UNCATLG) IEF212I CJ4130BT STEP0 DD1 - DATA SET NOT FOUND It was discussed here within the past couple years that IBM has done two or three about-faces on catalog syntax rules. If all else fails, you could REPRO MERGECAT everything else to a new catalog and delete the catalog. -- 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: Invalid dataset name in catalog, how to remove
Ken Leidner wrote: I have a tape dataset cataloged over 10 years ago with a very strange - invalid name. I am not sure how it was created, but I would like to remove it from the catalog. The tape has scratched years ago and I found this odd dataset name and would like to remove it from the catalog without having to zap the catalog to change its name first. Any suggestions? I have tried; In TSO a DELETE 'P.FSPOL.SBHF38AA(0)' noscratch IKJ56709I INVALID DATA SET NAME, 'P.FSPOL.SBHF38AA(0)' ISMF doesn't even find the dataset, even when looking for a prefix of the dataset name (like 'P.FSPOL.SB*.**’) Running IEFBR14 in batch gives //STEP0EXEC PGM=IEFBR14 //DD1 DD DSN='P.FSPOL.SBHF38AA(0)',DISP=(OLD,UNCATLG) IEF212I CJ4130BT STEP0 DD1 - DATA SET NOT FOUND If the entry is the only one with the first two nodes of P.FSPOL, you might be able to delete it with idcams: DEL P.FSPOL.* This will delete any catalog entry with three nodes and the first two nodes are P and FSPOL (use with care!) If you have other three node catalog entries that start with P.FSPOL, you probably need to use something like mainstar or trex to get rid of the entry. 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: Invalid dataset name in catalog, how to remove
TSO doesn't support GDG dataset names.You should specify the REAL dataset name, the one with the generation number. Try IDCAMS delete noscratch. // exec pgm=idcams //sysprint dd sysout=* //sysin dd * Delete filename NOSCRATCH ITschak | Itschak Mugzach | Director | SecuriTeam Software | | Email: [EMAIL PROTECTED] | Mob: +972 522 986404 | Skype: Itschak Mugzach | Web: www.Securiteam.co.il | -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of John Kington Sent: Friday, August 08, 2008 2:05 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Invalid dataset name in catalog, how to remove Ken Leidner wrote: I have a tape dataset cataloged over 10 years ago with a very strange - invalid name. I am not sure how it was created, but I would like to remove it from the catalog. The tape has scratched years ago and I found this odd dataset name and would like to remove it from the catalog without having to zap the catalog to change its name first. Any suggestions? I have tried; In TSO a DELETE 'P.FSPOL.SBHF38AA(0)' noscratch IKJ56709I INVALID DATA SET NAME, 'P.FSPOL.SBHF38AA(0)' ISMF doesn't even find the dataset, even when looking for a prefix of the dataset name (like 'P.FSPOL.SB*.**') Running IEFBR14 in batch gives //STEP0EXEC PGM=IEFBR14 //DD1 DD DSN='P.FSPOL.SBHF38AA(0)',DISP=(OLD,UNCATLG) IEF212I CJ4130BT STEP0 DD1 - DATA SET NOT FOUND If the entry is the only one with the first two nodes of P.FSPOL, you might be able to delete it with idcams: DEL P.FSPOL.* This will delete any catalog entry with three nodes and the first two nodes are P and FSPOL (use with care!) If you have other three node catalog entries that start with P.FSPOL, you probably need to use something like mainstar or trex to get rid of the entry. 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 __ NOD32 3280 (20080718) Information __ This message was checked by NOD32 antivirus system. http://www.eset.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: Invalid dataset name in catalog, how to remove
You can do 3.4 in tso of the P.FSPOL.SBHF38AA and then next the entry type: DEL / NOSCR on the command line next to the full name line. If there are no more entries you can delete the GDG entry from the catalog. BB -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of John Kington Sent: Friday, August 08, 2008 8:05 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Invalid dataset name in catalog, how to remove Ken Leidner wrote: I have a tape dataset cataloged over 10 years ago with a very strange - invalid name. I am not sure how it was created, but I would like to remove it from the catalog. The tape has scratched years ago and I found this odd dataset name and would like to remove it from the catalog without having to zap the catalog to change its name first. Any suggestions? I have tried; In TSO a DELETE 'P.FSPOL.SBHF38AA(0)' noscratch IKJ56709I INVALID DATA SET NAME, 'P.FSPOL.SBHF38AA(0)' ISMF doesn't even find the dataset, even when looking for a prefix of the dataset name (like 'P.FSPOL.SB*.**') Running IEFBR14 in batch gives //STEP0EXEC PGM=IEFBR14 //DD1 DD DSN='P.FSPOL.SBHF38AA(0)',DISP=(OLD,UNCATLG) IEF212I CJ4130BT STEP0 DD1 - DATA SET NOT FOUND If the entry is the only one with the first two nodes of P.FSPOL, you might be able to delete it with idcams: DEL P.FSPOL.* This will delete any catalog entry with three nodes and the first two nodes are P and FSPOL (use with care!) If you have other three node catalog entries that start with P.FSPOL, you probably need to use something like mainstar or trex to get rid of the entry. 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: Invalid dataset name in catalog, how to remove
Have you tried using the UNCATLG operation of IEHPROGM? I think that the control statement would be UNCATLG DSNAME=P.FSPOL.SBHF38AA(0) (at least one blank before the UNCATLG). Bill Ken Leidner wrote: For the few people that have not understood. This is NOT a GDG entry or its base, rather just an invalid dataset name for an NONVSAM cataloged tape dataset. Here is a print from IDCAMS of the catalog entry (I know this will look like a mess) IDCAMS SYSTEM SERVICES LISTING OF DATA SET -PROD.USERCAT KEY OF RECORD - D74BC6E2D7D6D34BE2C2C8C6F3F8C1C14DF05D404040404040404040404040404040404040 4040404040404000 00 00600034 C101 2DD74BC6 E2D7D6D3 4BE2C2C8 C6F3F8C1 C14DF05D 40404040 *.-..AP.FSPOL.SBHF38AA(0)* 20 40404040 40404040 40404040 40404040 40404040 4014 01FF * ...* 40 FF088811 8F0F 0016 0400C3F2 F1F8F2F4 78008080 0800 0001 *..C21824* -- 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: Invalid dataset name in catalog, how to remove
Ken, One of the first posts in this thread stated that running an IEFBR14 with DISP=(OLD,...) failed with error Dataset not found. Question: Is the high-level qualifier P connected to catalog PROD.USERCAT? If not, can you do that without causing other grief? And after that, can you rerun the IEFBR14 with DISP=(OLD,DELETE,DELETE)? Regards, Ulrich Krueger -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Big Iron Sent: Friday, August 08, 2008 09:59 To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Invalid dataset name in catalog, how to remove Have you tried using the UNCATLG operation of IEHPROGM? I think that the control statement would be UNCATLG DSNAME=P.FSPOL.SBHF38AA(0) (at least one blank before the UNCATLG). Bill Ken Leidner wrote: For the few people that have not understood. This is NOT a GDG entry or its base, rather just an invalid dataset name for an NONVSAM cataloged tape dataset. Here is a print from IDCAMS of the catalog entry (I know this will look like a mess) IDCAMS SYSTEM SERVICES LISTING OF DATA SET -PROD.USERCAT KEY OF RECORD - D74BC6E2D7D6D34BE2C2C8C6F3F8C1C14DF05D404040404040404040404040404040404040 4040404040404000 00 00600034 C101 2DD74BC6 E2D7D6D3 4BE2C2C8 C6F3F8C1 C14DF05D 40404040 *.-..AP.FSPOL.SBHF38AA(0)* 20 40404040 40404040 40404040 40404040 40404040 4014 01FF * ...* 40 FF088811 8F0F 0016 0400C3F2 F1F8F2F4 78008080 0800 0001 *..C21824* -- 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: Invalid dataset name in catalog, how to remove
have you tried putting the dataset name in quotes on your IEFBR14 using the DISP=(OLD,DELETE) parameter like this DSN='P.FSPOL.SBHF38AA(0)' Data set names on the tape HDR1 record (assuming standard labels were used) is only the last 17 characters on the tape, but not on the catalog entry. HTH From: IBM Mainframe Discussion List on behalf of Ulrich Krueger Sent: Fri 8/8/2008 10:20 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Invalid dataset name in catalog, how to remove Ken, One of the first posts in this thread stated that running an IEFBR14 with DISP=(OLD,...) failed with error Dataset not found. Question: Is the high-level qualifier P connected to catalog PROD.USERCAT? If not, can you do that without causing other grief? And after that, can you rerun the IEFBR14 with DISP=(OLD,DELETE,DELETE)? Regards, Ulrich Krueger -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Big Iron Sent: Friday, August 08, 2008 09:59 To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Invalid dataset name in catalog, how to remove Have you tried using the UNCATLG operation of IEHPROGM? I think that the control statement would be UNCATLG DSNAME=P.FSPOL.SBHF38AA(0) (at least one blank before the UNCATLG). Bill Ken Leidner wrote: For the few people that have not understood. This is NOT a GDG entry or its base, rather just an invalid dataset name for an NONVSAM cataloged tape dataset. Here is a print from IDCAMS of the catalog entry (I know this will look like a mess) IDCAMS SYSTEM SERVICES LISTING OF DATA SET -PROD.USERCAT KEY OF RECORD - D74BC6E2D7D6D34BE2C2C8C6F3F8C1C14DF05D404040404040404040404040404040404040 4040404040404000 00 00600034 C101 2DD74BC6 E2D7D6D3 4BE2C2C8 C6F3F8C1 C14DF05D 40404040 *.-..AP.FSPOL.SBHF38AA(0)* 20 40404040 40404040 40404040 40404040 40404040 4014 01FF * ...* 40 FF088811 8F0F 0016 0400C3F2 F1F8F2F4 78008080 0800 0001 *..C21824* -- 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 -- 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: Invalid dataset name in catalog, how to remove
Ken Leidner wrote: I have a tape dataset cataloged over 10 years ago with a very strange - invalid name. I am not sure how it was created, but I would like to remove it from the catalog. The tape has scratched years ago and I found this odd dataset name and would like to remove it from the catalog without having to zap the catalog to change its name first. Any suggestions? I have tried; In TSO a DELETE 'P.FSPOL.SBHF38AA(0)' noscratch IKJ56709I INVALID DATA SET NAME, 'P.FSPOL.SBHF38AA(0)' ISMF doesn't even find the dataset, even when looking for a prefix of the dataset name (like 'P.FSPOL.SB*.**’) Running IEFBR14 in batch gives //STEP0EXEC PGM=IEFBR14 //DD1 DD DSN='P.FSPOL.SBHF38AA(0)',DISP=(OLD,UNCATLG) IEF212I CJ4130BT STEP0 DD1 - DATA SET NOT FOUND How did you find the catalog entry in the first place? Is it in the Master Catalog or some User Catalog? I think when you use a quoted DSN in JCL, that tells the system it shouldn't parse the internals of the name at all, so there's probably no way it could associate a catalog alias to find the entry if it's not in the Master Catalog. If the entry is in some User Catalog, back in the old days before STEPCAT was disallowed, a STEPCAT DD could have been used to point to the correct catalog. But, with STEPCAT unavailable, try a batch IDCAMS step to uncatalog the dataset with DELETE P.FSPOL.SBHF38AA(0) NOSCRATCH CAT(usercatname) (that assumes that IDCAMS doesn't get in the way and attempt to resolve this dsn as a relative GDG reference). TSO fails because it always attempts to interpret DSN parentheses as a PDS member reference and the member name is invalid. The ISMF failure to find anything suggests that either P or P.FSPOL is either not set up as a catalog alias (and the dsn is not in the master catalog), or it is set up as an alias that points to a different USERCAT than the one with the bogus entry, or perhaps ISMF does find the entry and just can't deal with the non-standard name. The IEFBR14 failure suggests that the entry is not in the Master Catalog. -- Joel C. Ewing, Fort Smith, AR[EMAIL PROTECTED] -- 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
