Filemode C has been "special" since very long, that is even before VMSES was available. At that time, moste service execs neede to be started from disk C. Maybe that's the reason why VMSES leaves filemode C untouched.
So, I'd say: leave the 191 as A, then all $MSGLOG files remain there, you have access to your PROFILE XEDIT, LASTING GLOBALV etc. And, if you need a 500, access it as C But, nobody forbids you to enlarge the 191 and you'll never need the 500 anymore... 2007/6/14, James Vincent <[EMAIL PROTECTED]>:
VMSES/E has specific file modes that are "free" to access disks/directories at. Guessing what file modes to access disks at is probably not a grand idea because it could be that some component will use that file mode later and then strange things will happen. HELP VMSES VMFSETUP explains in the "RETAIN" parm that "File modes A thru D, S, and Y are automatically retained." A _should_ be 191; B is the 5E5, D is 51D. S and Y are specifically for CMS. That leaves file mode C as a Very Good Choice. Your MAINT 191 disk is good to keep at A - it will get all the MSG (logs) files from VMSES/E processes etc. If you access 500 as A, it will work but then you have logs in different places. You can get fancy and do a $PPF override and add a :RETAIN. tag to your components if you want to use a specific file mode to have VMSES/E "ignore". File mode C works well though. Jim Vincent On 6/14/07, Dave Jones <[EMAIL PROTECTED]> wrote: > > A simple ACC 500 L (o K) works ..... > > Good luck. > > Jim Bohnsack wrote: > > Ann--I took the cowards way out and made the 500 disk my 191 disk. If > I > > remember correctly, I copy some or most of what I thought I'd need > from > > 191 to the much larger 500 disk and then changed mdisk addresses. > > Jim > > >
-- Kris Buelens, IBM Belgium, VM customer support
