Classification: UNCLASSIFIED Caveats: NONE Hi Juergen,
I just allocated an LDS on a clean non-SMS volume (under 1.13) and a VVDS was created, as expected. Is it possible that your security system is sticking its nose in? Is it possible that the volume was initialized as STGR even though the volume is not defined in a SG? I remember reading somewhere that VVDSs are no longer automatically catalogued but I agree with your belief (i.e. that an LDS requires a VVR). Viele Gruessen! Alan (ehmalige SSS Berater) -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Juergen Kehr Sent: Wednesday, September 17, 2014 10:47 AM To: [email protected] Subject: zFS and VVDS Dear friends, a situation which at least for me seems to be quite strange today happened: We put some zFS datasets on a newly initialized volume. We do NOT explicitly put a VVDS on that volume. We thought that this be done, when the first VSAM dataset is allocated on this volume and AFAIK zFS files are VSAM LDS files. But no VVDS was allocated, but everything seems to be normal. Is that correct and where does the system store the VSAM informations about this zFS? BTW: The volume is not SMS managed. Can anybody clarify this surprising situation? Because I've learned that a VVDS is created, when the first VSAM on that volume is created. Thanks in advance. Kind regards. Juergen Kehr ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN Classification: UNCLASSIFIED Caveats: NONE ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
