> As I said I know there are multiple ways to do what I wanted.
Right. With z/VM and most other OS'es there are many ways to skin a cat -
if you're into that sort of thing. Chuckie may be into that, but lets not
go there.
Nonetheless, having the discussion on the list serves to enlighten z/VM
newbies with several additional ways to "prepare the meal". Learning from
those who have trod the road of real experience often results in better
understanding than obtuse written doc. Of course, IBM's pubs are rarely
obtuse - but instead serves as example which most other vendor's should
emulate, including a certain two-letter ISV which shall remain nameless.
For those who have not discovered it yet, there is excellent WEB BROWSER
ACCESS to the IBMVM discussion list. It provides outstanding HISTORICAL
SEARCH CAPABILITY - so that when you have a question, you can search the
full history of the list (even before its name change to IBMVM) for
previous similar discussions of related (or ANY!) question. See:
http://listserv.uark.edu/archives/ibmvm.html
Mike Walter
Hewitt Associates
The opinions expressed herein are mine alone, not my employer's.
"Bob Bates" <[email protected]>
Sent by: "The IBM z/VM Operating System" <[email protected]>
12/18/2009 01:39 PM
Please respond to
"The IBM z/VM Operating System" <[email protected]>
To
[email protected]
cc
Subject
Re: Old question
As I said I know there are multiple ways to do what I wanted. I actually
use several different ways of doing it depending on the situation.
I have a small 5.4 running 2nd level that I test apply maintenance on
before any 1st level install. It has a virtual CTC to 1st level RSCS and I
send files back and forth that way.
When I roll out new upgraded releases with a new res, I use the shared
minidisk (R/W on 1st level, R/O on 2nd) to move files up and swap if I
need to go the other way.
In this case I was going to have 6 different systems IPL'd under the same
id (obviously not at the same time). Felt the PUNCH was easiest.
Bob Bates
Enterprise Hosting Services
w. (469)892-6660
c. (214) 907-5071
"This message may contain confidential and/or privileged information. If
you are not the addressee or authorized to receive this for the addressee,
you must not use, copy, disclose, or take any action based on this message
or any information herein. If you have received this message in error,
please advise the sender immediately by reply e-mail and delete this
message. Thank you for your cooperation."
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[email protected]] On
Behalf Of Fran Hensler
Sent: Friday, December 18, 2009 12:13 PM
To: [email protected]
Subject: Re: Old question
I've been using this method ever since I migrated from VM/SP 3 to 4.
Works great! Only once did I screw up because I had both minidisks in R/W
mode and it was easy to recover by reformatting the minidisk.
/Fran Hensler at Slippery Rock University of Pennsylvania USA for 46 years
mailto:[email protected] http://zvm.sru.edu/~fjh +1.724.738.2153
"Yes, Virginia, there is a Slippery Rock"
--------------------------------------------------------------------------
On Fri, 18 Dec 2009 09:34:57 -0600 Mike Walter said:
> {snip} I'll offer another
>simple method disk-to-disk copy technique (usable by those not
>permitted to download tools): Define a minidisk on both systems, on the
>same DASD at the same extents for both systems.
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. All messages
sent to and from this e-mail address may be monitored as permitted by
applicable law and regulations to ensure compliance with our internal policies
and to protect our business. E-mails are not secure and cannot be guaranteed to
be error free as they can be intercepted, amended, lost or destroyed, or
contain viruses. You are deemed to have accepted these risks if you communicate
with us by e-mail.
