Thanks! According to the reply from you and Scott, I could locate the *VSAM* entry (or multiple entries as the VVDS may under >1 UCAT and/or MCAT) under DSLIST via 'S*.VVDS.Vxxxxxx'
.....but I still found one of the VVDS (I'm not sure if it is a normal case or not, anyway the datasets under that volume seems normal to me): 1. under DSLIST, input 'S*.VVDS.Vxxxxxx' or '*.VVDS.Vxxxxxx' shows nothing 2. under DSLIST, input 'SYS1.VVDS.Vxxxxxx' shows the Data Component of that VVDS but not showing the Cluster (*VSAM*) of that VVDS. By using "Display Catalog Name", it shows the VVDS is under MCAT. 3. I do a LISTC CAT(MCAT) ALL and DITTO VB/DB against that MCAT, but I can't locate the entry of that VVDS (not found even search with the volser). So under Point 2, the DSLIST tells me the VVDS is under MCAT but I could prove it elsewhere..... (and now this is the only VVDS that I can't locate its cluster component).... it is quite confusing indeed Paul On Mon, 12 Oct 2009 14:51:11 -0500, Rick Fochtman <[email protected]> wrote: >-------------------------------------<snip>------------------------------- ----- >Yeah, I also expect a VVDS should have been cataloged under either MCAT >or UCAT. However, there is a VVDS, it cannot be shown when I input >'SYS1.VVDS' under DSLIST, but it can be found if I input >'SYS1.VVDS.Vxxxxxx' (full name) under DSLIST. Even the VVDS can be seen >under DSLIST with full name search, I didn't see a "*VSAM*" Cluster >entry (only a Data Component entry there). In addition, when I issue a >'LISTC ENT(/) ALL' command against the Data Component of that VVDS, it >can't tell me where the VVDS is cataloged. So that's why I suspect the >VVDS is not cataloged anywhere..... >-----------------------------------<unsnip>------------------------------ ----- >Paul, the VVDS is ALWAYS cataloged in either a MCAT or UCAT. But it >doesn't follow the "rules" regarding ALIAS processing. When you search >for SYS1.VVDS, the system will look in the MCAT first. Since there's no >ALIAS named SYS1, that's where the system search ends. > >Lets assume we're playing with 1 volume here, volser is 123456. If I >define a VSAM cluster named U1.VSAM, the VVDS on volume 123456 will be >cataloged in UCAT.ABC, 'cuz that's where the alias in MCAT points for >U1. No U2.VSAM is created on the same volume, but in a different >catalog, named UCAT.XYZ. Again the VVDS is cataloged in the same UCAT as >the cluster. > >Try this: > > LISTCAT LVL(SYS1) CAT(UCAT.ABC) > >To see the VVDS entry in one of those catalogs. > >You can see the same things in all the other UCATs that might have VVDS >entries. > >It can be confusing, because the VSAM boys didn't quite follow the rules >they imposed on us, but that's the way it is. > >Rick > >---------------------------------------------------------------------- >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
