Hi
David,
For
most things a "virtual cylinder 0" is just fine, but if you want full access to
the pack you need real cylinder 0. For example, if I'm testing my Disaster
Recovery software for an 3339 cylinder 3390-3, I need all 3339 cylinders.
Michael Coffin, President
MC Consulting Company, Inc.
PMB 123
289 Park Street
Stoughton, Massachusetts 02072
Voice: (781) 344-9837 FAX: (781)
344-7683
We employ aggressive SPAM filters. If you cannot reply or send email to mccci.com go to www.mccci.com/spamblockremove.php
-----Original Message-----
From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes
Sent: Friday, November 04, 2005 3:08 PM
To: [email protected]
Subject: Re: 2nd level install - duplicate volsersDavid's method (using cylinder 1-END) is arguably easier at the cost of a cylinder, and loss of access to real cylinder 0 by the second level guest (should that be needed).OK, now I'm curious. I've never encountered a VM function that absolutely, positively had to operate on *real* cylinder 0 to work properly -- AFAIK, the "virtual" cyl 0 has always been good enough for 2nd level guests. What functions would care about this (assuming that DDR properly offsets as needed if you're restoring from a minidisk back to a real volume)? I can't think of any.-- db
