I'd be curious to know how to "use" this. I just tried on my sandbox system, and didn't get the expected results.
With or without the catalog command I can create non-standard Dataset names using quotes, but then SMS complains, and it doesn't get cataloged. Allocate it on non-sms DASD, and I still cannot open it. The following 1) IKJ56231I FILE ISP09537 NOT ALLOCATED, SYSTEM OR INSTALLATION ERROR+ 2) IKJ56231I TEXT UNIT X'0002' CONTAINS INVALID PARAMETER _________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Services [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Tuesday, December 27, 2011 9:19 AM To: [email protected] Subject: Re: Eight-character TSO Userid Support On Tue, 27 Dec 2011 07:49:31 -0500, Peter Relson wrote: >>What PARMLIB member is it that allows >8 characters between periods? >> >http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2c190/8.6 .5.1 > >As Paul Gilmartin posted, this is a reference to: >MODIFY CATALOG,DISABLE(DSNCHECK) > There's precious little further documentation I can find. Is all syntax checking removed? Is even the HLQ allowed to exceed 8 characters? Some people suspect that this was an unintended consequence of removing all syntax checking when CVOLs were supplanted. After the product was in the field, some customers complained that programmers were cataloging DSNs that couldn't readily be manipulated with customary utilities. IBM discovered or at least suspected that other customers were actively exploiting the feature and had little choice but to provide an option. >I'll admit that I didn't even know that this option existed. I know of >many places that validate data set names that have no knowledge of the >state of this option. > You could likely start the list with the JCL R/C/I. What if JCL were DSNCHECK-savvy but the submitting and executing systems had different states of this option? You know me; I'd insist that lacking such knowledge, JES should presume the least restrictive setting. On Tue, 27 Dec 2011 00:54:58 -0500, Robert A. Rosenberg wrote: > >>Likewise, in days of yore, but no longer, one DSN was not allowed >>to be a prefix of another, such as: >> >> GUBBINS.WOMBAT versus >> GUBBINS.WOMBAT.FUBAR > >This was due to CVOL Support. Each level was a set of chained records >and WOMBAT as a File name conflicted with it being a record >containing a pointer to another level. > Much analogous to the UNIX behavior where a name may not refer to both a directory and a basefile. This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
