No real concerns either way in a single system shop. However, if you do Sysplex Shared filesystem "SYSPLEX(YES)" in BPXPRMxx then there is a requirement for them to be in a usercat connected to all systems that are sharing or you will have problems.
We happen to have ours in their own usercat, and everything is OMVSU.**. A side note to a comment I saw Skip make in his response about the physical file system dataset name and the fact that in his shop individual users filesystems start with a dataset name of their userid's. There is something in the OMVS config guide that talks about the fact that a "user" shouldn’t have access to the physical dataset container, as that is considered a security issue(not sure how). _________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Engineering [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of David G. Schlecht Sent: Thursday, August 20, 2015 11:21 AM To: [email protected] Subject: Catalog for OMVS datasets Hello all, 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? David G. Schlecht | Information Technology Professional State of Nevada | Department of Administration | Enterprise IT Services T:(775)684-4328 | F: (775) 684‐4324 | E:[email protected] ________________________________ This communication, including any attachments, may contain confidential information and is intended only for the individual or entity to which it is addressed. Any review, dissemination or copying of this communication by anyone other than the intended recipient is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and delete all copies of the original message. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
