That is only true for non-SMS-managed data sets, as it turns out.
True, Walt. I should have mentioned that the catalog checks are not done for SMS-managed datasets. I guess the presumption is that since SMS ds must be cataloged in the standard search order, the sites's sysprogs, by assignment of aliases, controls which catalogs datasets will go into, which gives implicit permission to update that catalog. So the user just needs authority to create the dataset.
The best description of the authorities you need will be in the DFSMS books, not in RACF books. As DFSMS is the one that performs all the checks, only they really know what the authorities are for the various cases.
If only it were true. I haven't done an exhaustive search of the DFSMS bookshelf, but the few references I looked at, especially the obvious "Managing Catalogs", don't seem to contain a definitive set of RACF rules for cataloging datasets.
The IDCAMS manual has a good table, but it relates to the IDCAMS commands such as DEFINE. The rules do apply to other environents, such as cataloing a dataset created through JCL, but why would you look in the IDCAMS manual for that?
-- Bruce A. Black Senior Software Developer for FDR Innovation Data Processing 973-890-7300 personal: [EMAIL PROTECTED] sales info: [EMAIL PROTECTED] tech support: [EMAIL PROTECTED] web: www.innovationdp.fdr.com ---------------------------------------------------------------------- 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
