>Ah. Well, I was thinking of a script that Kevin Mullen of >US West (later Qwest) had for his organization. [snip]
That was sure a very useful script back when automount did not yet support the allocation of file system data set. Apart from adding an OMVS segment, automount can do the rest for you today. >I would give the userid for OMVS and your ZFS STCs all authority >to all zFS data sets. I would do the same for HFS files for OMVS. There is no need for this if you define the OMVS and zFS address spaces as TRUSTED, which is the recommended way to do it. The advantage over PERMITting those userids to each and every file system data set is that the access is bound to the STC name, not to the userid. PERMITting OMVSKERN (which is the standard userid assigned to the kernel STC) to the file system data sets allows the same access to any other programm running under OMVSKERN. You may not have such but I know of installations that are using OMVSKERN for more that only the OMVS STC. >I thought automount would work with HSF files only, and not with >zFS. Automount can manage HFS, zFS and NFS file systems (basically every type of file system that can be handled with mount/unmount). It does only allocate data sets for HFS and ZFS file systems, however. -- Peter Hunkeler Credit Suisse ---------------------------------------------------------------------- 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
