OK, I know I could look it up in the book, but what are the share options on the catalog that would cause the additional processing?
>>> [EMAIL PROTECTED] 10/12/2005 2:13:28 PM >>> > > >What about catalogs? Or DADSM activity? Don't those behave differently >if a volume is marked shared? > Good point on catalogs. If the catalog is on a shared disk, and has the right SHR options, then on every access CATALOG will read the catalog's VVR where updates to the catalog are recorded, so see if the key it needs has been updated. So, yes, there will be extra I/Os on catalog access, with some performance hit, but I don't know how much. DADSM just does the RESERVE on SYSVTOC, so overhead is minimal. Access to the VVDS is also protected by a RESERVE, no big deal. -- 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 ---------------------------------------------------------------------- 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
