I prefix dsn's with SYS1.OMVS. Where the name is required to be unique, I append a LLQ.
DFDSS logical copy with RENUNC works great to keep multiple copies if required. You might want to look up "Chapter 5. Managing the z/OS UNIX File System" in "z/OS UNIX System Services Planning" (GA32-0884 for z/OS 2.1) HTH, <snip> How do you catalog your OMVS datasets? My predecessor created a catalog in which he put a few OMVS dataset definitions. However, it never really got used. We only have a few dozen OMVS file systems so it doesn't seem to make sense to have a catalog just for them. What is common practice? What do you do? Do you have a separate catalog for your OMVS datasets? If so, what's your reasoning? </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
