Randy DeMaat wrote:
Bob, Ok. Thanks all. Wondering, though, why the DEFINE doesn't catalog
the SYS1 in the master cat. A define of vsam with my id catalogs fine.
And why the screwy results from 3.4? The full name works? But
SYS1.VVDS.VHAW15* doesn't?
Don, I do have 2 lpars but I did this all in the span of a few minutes.
The test lpar did not come in to play.
Tom, a listc of SYS1.VVDS.VHAW157 with no catalog parm fails.
With a catalog parm of the cat that DSN120T is in, it works. Although
I'm guessing this would not have worked either before the datasets
existed on the volume. I'll play a little more with your other
suggestions but I think all is working well. Just need to think out side
the box apparently.
Oh, and this is an SMS managed volume. Maybe an acs routine is doing
something too. Havent looked into that.
-----------------------------<snip>----------------------------------------
No, Randy. Whn you define the first VSAM dataset on the volume, the VVDS
is created and cataloged in the same catalog as that first dataset.
That's just the way it works. The VVDS has to be cataloged, but there's
no requirement that it follow normal CATALOG/ALIAS relationships, since
the usual access to it is via the VTOC, not the catalog.
----------------------------------------------------------------------
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
