Beware when you give CP RR access to CF1: CP can have to read files from there while it is running. The most obvious are the logon LOGO files. If you change them on the fly while CP has RR access, CP can get the problem we know as CMS users: 'error 3 reading file....'.
*CPLISTFILE * * A STAT* will show you which files are read how many times To avoid that problem, you can tell CP to chache certain files (explained in CP Installation and Planning Guide, "Understanding the CP File System". You can issue *CPCACHE fnsel ftsel fm* to have some files chached, or create a CPCACHE FILES on the CFx disks to have them cached automatically each time that CFx disk is CPACCESSed. Once that's done, you can change the SYSTEM CONFIG to access CFn in RR mode. That's how I set up my famous -and former- customer's VM systems. 2011/7/6 Ronald van der Laan <nl50...@gmail.com> > Gao, > > Your SYSTEM CONFIG (on the MAINT 0CF1) probably contains: > CP_Access MAINT CF1 A > > Normally you want to issue "CPREL A" before you update the parm disk, > followed by a "CPACC MAINT 0CF1 A" to reaccess it again. > But you can also change the SYSTEM CONFIG line into: > CP_Access MAINT CF1 A RR > > That will make CP link its parm disk with RR instead of the default SR and > will allow you to update the disk while CP still has it accessed. > The normal single writer, multiple reader rules for CMS disks apply, so it > is your foot and your gun. > And don't forget to let CP know that you updated the disk by issueing a > "CPACC MAINT CF1 A RR". > > Ronald van der Laan > -- Kris Buelens, IBM Belgium, VM customer support
