The first form, is clearly NOT quoted, and never appears to be. In order for it to be quoted, the quotes would have to be the data area passed to SVC 99, ie. DSNAME DC CL44'''MY.DATA.SET'''
In the second, this is also unquoted because the TSO parse utility removes the quotes from dataset name prior to passing it to the CALLDAIR interface. The third also, is clearly non-quoted, so in fact, all of these forms will not hav ethe bit set. Wayne -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Paul Gilmartin Sent: Thursday, December 29, 2005 2:18 PM To: [email protected] Subject: Re: Invalid DSN in Catalog In a recent note, Dan said: > Date: Thu, 29 Dec 2005 14:45:41 -0500 > > The SIOT contains a "Quoted Data Set Indicator", SIOTDSQU... > change id JBB2223 93/05/13. > It's been around a while. > And how does this get set/unset in the case of dynamic allocation? For example in assembler language, one might code: DSNAME DC CL44'MY.DATA.SET' ... which would appear always to be quoted. Likewise in TSO, is the fully qualified form: ALLOCATE DSN('PREFIX.DATA.SET') ... considered to be quoted while PROFILE NOPREFIX ALLOCATE DSN(PREFIX.DATA.SET) ... is considered to be unquoted? Etc. -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
