What I usually do is to set up an mdisk on an ID on the first level system,
in my case JAB282 091, that overlaps a mdisk on the 2nd level system such
as MAINT 091. Then if I screw up, it's just my own mdisk that gets hit. I
set them both up as RR disks and just make sure or try to make sure that I
never have a write link to each at the same time.
Another approach, altho this usually comes into play a little further along
when you have RSCS and/or TCPIP working on the 2nd level system, is to use
an RSCS connection or FTP. Initially, however, some kind of system of an
overlapping mdisk using disk addresses that, if you have a brain check and
clobber something, all you're losing is whatever was on that
"transportation" mdisk.
Jim
At 09:06 AM 12/8/2005, you wrote:
Side question on this one. When you gen a 2nd level VM
system and need some CMS files from the 1st level
system, what is the easiest way to link to 1st level
CMS minidisks from the second level VM?
Thks,
Bill J.
Jim Bohnsack
Cornell Univ.
(607) 255-1760
