Robert A. Rosenberg wrote: >I do not think that just reading the catalog would be a problem but >adding/deleting datasets as well as doing the updates involved with >opening/closing existing datasets may have an effect due to locking of the >catalog during these operations.
Agreed. Think 'catalog(s) overhead' and 'CA/CI splits'. Move your catalogs so they are on different volsers. Move your backups to OTHER volsers while ensuring your backups are done regurlarly and restorable. To Alan Storr: >If you could rebuild your z/OS environment from scratch, however you wanted, >how would you organize user catalogs to optimize performance, availability and >recovery? Others gave very useful answers, but it seemed to me the eventual answer is 'it depends'. For myself, I would consider security of the catalogs and their backups themselves and check the accesses to manage catalogs and their entries. UACC for MCATs = READ UACC for User Cats = UPDATE STGADMIN.** profiles = check with storage team. Access to CATALOG address space commands should be restricted. ... add your other security concerns here ... Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
