Mike:
Thanks, and that has no affect on the previously defined volume
contents? Sounds like it just adds the alias addresses to the LCU
definition, but no physical disk data needs to be changed, right?
Mike
On 10/18/2011 03:35 PM, Mike Schwab wrote:
If you have unused / usassigned addresses on each LCU, you can add
PAVs to the end and dynamicly update your I/O gen to use them.
On Tue, Oct 18, 2011 at 1:56 PM, Mike Myers<[email protected]> wrote:
Radoslaw:
Thanks. My greater concern is loss of data. This system is very new and not
into production yet, so an IPL would be minimally "disruptive" for a while
(until after the operating system was installed and configured.
Since we are installing the operating system later this week, if it was
reformatting the volumes, that would be truly disruptive.
Mike
On 10/18/2011 02:28 PM, R.S. wrote:
W dniu 2011-10-18 20:00, Mike Myers pisze:
Does anyone know if adding PAV (alias) addresses to a configured DS6800
is disruptive of any real devices already configured and initialized on
the affected LCU?
IMHO yes. Usually you have 256 devices per CU. Base and aliases. So,
adding aliases means
CU reconfiguration, means some device must go to another CU. Since such
devices must go offline, it is disruptive.
There is further question: is the reformat required to do such
reconfiguration? "Disruptive" means simply offline-online, maybe it causes
IPL. Reformat means you LOSE your volumes and have to restore them from
backup.
My €0.02
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
