Just to continue the process of showing that VM provides many tools to perform the same work...
When installing a second-level z/VM 5.1.0 system (which we called VMCMS510 for our purposes), we wanted to copy many files from minidisks on the old still-production 1st level system to the new system (actually running second level on a totally different machine).
I got tired playing the usual games, and wrote a "510MDISKS EXEC" which uses the CP command "DEFINE MDISK" to define a r/w mdisk mapping the VM:Secure source minidisk (1B0) on the VMCMS510 system, access it as a R/O extension (to keep from "accidentally" writing to it), read the directory entry for the specified used, DETACH the 1B0 disk, use CP DEFINE to define an MDISK mapping the cylinders of the VMCMS510 userid's target disk (r/w), and by default access it as a R/O extension of itself (again, moderate protection from self-immolation).
The command could be changed to go the "other way", but I feel better copying from a production system to a target new system. The syntax follows:
CP DEFINE MDISK and ACCESS mdisks as defined on "VMCMS510" test system's
VM:Secure 1B0 mdisk.
XEDIT this EXEC to add new mdisks.
+-=----+ +-I--+
>>-510MDISK-+-userid-+--+-mdisk-+--+-vdev-+--+-fm-+--+---------+-------><
+-*----+ +-fm-+ +-R/W-----+
+-RW------+
+-FORCERW-+
E.g.
510MDISK MAINT 299 {Defined R/W, ACCESSed as R/O ext.}
510MDISK MAINT 299 * M {Defined R/W, ACCESSed as R/O M/M ext.}
510MDISK MAINT 191 2191 {Defined R/W as 2191, ACCESSed as R/O ext.}
510MDISK MAINT 191 2191 P {Defined R/W as 2191, ACCESSed as R/O P/P.}
510MDISK OPERATOR 191 * O RW {Defined R/W, ACCESSed as R/W O-disk}
I'd be happy to share if anyone wants it (with the usual provisos: no warranty expressed or implied, you mileage may vary, do not operate this command when taking alcohol or sleep-inducing drugs, etc.)
Mike Walter
Hewitt Associates
The opinions expressed herein are mine alone, not my employer's.
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.
The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
