On Friday, 01/23/2009 at 03:56 EST, "O'Brien, Dennis L"
wrote:
> I've seen a number of posts, either here or on IBMVM, that suggest
> changing system ID's for DR. We don't do that. We have 18 VM systems.
> They're all somewhat different, or we wouldn't have that many. There is
> far too much no
riginal Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
O'Brien, Dennis L
Sent: Friday, January 23, 2009 3:55 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Z/Linux CKD DASD migration from one DASD Subsystem to
another
Alan Altmark wrote:
>Convenience a
Alan Altmark wrote:
>Convenience and Security are rarely bedfellows. Hopefully you use a
>different system ID when you're in DR. Use it to qualify the
>OFFLINE/ONLINE_AT_IPL so that you get the correct address range
depending
>whether you are at home or abroad.
I've seen a number of posts, eithe
And if I remember correctly, when Mark joined Novell, we had this little 2 GB
memory problem in VM. That would force many large zLinux shops to have
production running in LPARs. They could still leave test and smaller zLinux
images under z/VM.
But the 2 GB line is no longer much of a proble
On Friday, 01/23/2009 at 03:23 EST, Marcy Cortes
wrote:
> Alan wrote:
> >Iffen I had my druthers, I'druther SYSTEM CONFIG allowed volumes to be
> specified by device address instead of, or in addition to, volser.
>
> Ewww. That'd suck for disaster recovery and PPRC Hyperswap.
Convenience and Sec
>> Iffen I had my druthers, I'druther SYSTEM CONFIG allowed volumes to
be specified by device address instead of, or >> >> inaddition to,
volser.
Alan,
I see your point, but many would have an issue with that approach - many
DR scenarios would be at risk.
Pat
-
Alan wrote:
>Iffen I had my druthers, I'druther SYSTEM CONFIG allowed volumes to be
specified by device address instead of, or in addition to, volser.
Ewww. That'd suck for disaster recovery and PPRC Hyperswap.
:)
Marcy
--
F
On Friday, 01/23/2009 at 07:58 EST, Clovis Pereira
wrote:
> To avoid this risk doesn't put all these disks on SYSTEM CONFIG.
> If you need repeated volsers, is secure to use fullpack dasd defined as
> MDISK ... DEVNO. VM mounts them only when necessary and volser doesn't
> matter
> I know a VM sy
0@VM.MARIST.EDU
390 Port cc
Subject
Re: Z/Linux CKD DASD migration from
one DASD Subsystem to another
cc
Subject
Re: Z/Linux CKD DASD migration from
one DASD Subsystem to another
21/01/2009
On 1/21/09 5:09 PM, "Mark Post" wrote:
On 1/21/2009 at 2:31 PM, David Boyes wrote:
> -snip-
>> If I haven't said it before, I don't think there's much reason to ever
>> consider LPAR deployment of Linux, but others do disagree with that view.
>> I'm sure there are workloads where it would
David
On Wed, Jan 21, 2009 at 7:42 PM, David Boyes wrote:
> 3) From an appropriately privileged ID (MAINT, etc):
>
> LINK guest 150 150 RR (you don't need/want write access to this
> volume)
> LINK guest F150 F150 MR(you're going to overwrite this one, so write)
>
My advise to make abs
On Wednesday, 01/21/2009 at 05:10 EST, Mark Post wrote:
> When I first joined Novell, I was surprised to learn that the world's
largest
> implementation was done all in LPARs. From what I was told, that wasn't
> because of the dollar cost of z/VM, but the overhead.
Their estimate of "overhead"
>>> On 1/21/2009 at 2:31 PM, David Boyes wrote:
-snip-
> If I haven't said it before, I don't think there's much reason to ever
> consider LPAR deployment of Linux, but others do disagree with that view.
> I'm sure there are workloads where it would matter, but I still think the
> manageability
On Wednesday, 01/21/2009 at 02:39 EST, David Boyes
wrote:
> I also really prefer to let VM manage the actual cyl 0. That may be just
> that I'm ancient and weird, but that way, there's absolutely zero chance
> that something weird in Linux will cause something unpleasant to happen
to a
> disk that
On 1/21/09 2:20 PM, "Tom Duerbusch" wrote:
> You said that if you used dedicated disks, you will now pay for it.
> I'm interested in "why you would pay for it"?
Mostly because it's usually a sign of a we-like-LPAR-LPAR-good mindset, and
you then fall into the problem of "it's a new disk, so it's
complained.
Paul Feller
AIT Mainframe Technical Support
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
tony...@bellsouth.net
Sent: Wednesday, January 21, 2009 11:02 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Z/Linux CKD DASD migration from one DASD
Hi David
You said that if you used dedicated disks, you will now pay for it.
I'm interested in "why you would pay for it"?
Your procedure works the same with dedicated dasd, except instead of linking
the disk, you attach the disks.
Now, if you were thinking LPAR, when then, yes, I agree it is m
I would add one step to David's excellent procedure below. Step 2.1, make
sure the guest account is logged off. Otherwise, when you renumber the
virtual addresses in the following steps, these changes will not take
place for the currently logged on guest.
Aria.
On Wed, 21 Jan 2009 13:42:07 -050
On 1/21/09 12:02 PM, "tony...@bellsouth.net" wrote:
> Hi all,
> I would like to know what ways you have used to migrate z/Linux CKD DASD
> volumes from one DASD subsystem to another? Thanks.
If you used minidisks (the right way, IMHO) then you:
1) Allocate new minidisks on the new array using
One thing to consider if you are on SUSE 10, the fstab defaults changed. And
that stops you from copying/moving from one disk to another, even on the same
DASD subsystem.
Go into:
yast
System
Partitioner
edit each disk
FSTAB options
change Device ID to Device Path
ok
ok
apply
Go into /etc/zip
It all depends -- maybe you can give some more detail about what you're
migrating from/to - whether it will be done under z/VM - whether the same
DASD types will be used.
In general - the answer is DDR .. use it to copy volumes of the same device
type/size..
Scott Rohling
On Wed, Jan 21, 2009 a
Oops... Thunderbird on Linux just showed a blue background with sort of a
snowflake
watermark on it. Ok, my apologies.
Mark Post wrote:
On 1/21/2009 at 12:35 PM, Rich Smrcina wrote:
tony...@bellsouth.net wrote:
Nice background, but is there a question?
My copy of his email had this:
Hi a
>>> On 1/21/2009 at 12:35 PM, Rich Smrcina wrote:
> tony...@bellsouth.net wrote:
>
> Nice background, but is there a question?
My copy of his email had this:
> Hi all,
> I would like to know what ways you have used to migrate z/Linux CKD DASD
> volumes from one DASD subsystem to another? Than
tony...@bellsouth.net wrote:
Nice background, but is there a question?
--
Rich Smrcina
VM Assist, Inc.
Phone: 414-491-6001
Ans Service: 360-715-2467
http://www.linkedin.com/in/richsmrcina
Catch the WAVV! http://www.wavv.org
WAVV 2009 - Orlando, FL - May 15-19, 2009
--
<>
26 matches
Mail list logo
