Lizette,
You can pursue hardware manipulation if you have the control and the
persistence, but to me the proper solution is software: IODF. Others have
said as much, but what you appear to need is the ability to IPL with
certain devices online to some LPARs and offline to others. The native
mechanism for this case is the 'OS Configuration', which allows you to
specify online or offline for every individual device that is still
physically and logically connected.
You can create as many OS Configs as you wish in your IODF. If you create
only one, then that config gets used by every LPAR IPLing with that IODF.
Depending on how you manage your enterprise, this may result in duplicate
volsers or volumes coming online to systems they don't belong to. The
solution is to create a separate OS Config for each sysplex or group of
systems that you want to see a singe set of volumes online at IPL during
NIP. Once a system is running, you can use VARY commands to put individual
volumes online or offline, but this is well after NIP.
We manage two glass house data centers with a single IODF that gets
migrated throughout the enterprise. Because we share DASD (mostly) within
each sysplex, we create several OS Configurations to segregate devices
online or offline according each set we want online or offline to each
plex. With an 8-character name, it's not hard to devise an appropriate
convention that makes sense. You don't have to push the distinction down to
the individual device address if you can identify ranges for each system,
but there is no limit to specificity.
The caveat is that if you have *more than one* OS Config in your IODF, then
*every system* must explicitly name the OS Config in LOADxx. That is, with
more than one, there is no default. Otherwise you get a wait state.
Specifying the OS Config looks like this. You will most likely want to
include other parameters not shown here.
*---+----1----+----2----+----3----+----4----+----5----+----6----+----7--
IODF os-confg
********
.
.
JO.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
[EMAIL PROTECTED]
Lizette Koehler
<[EMAIL PROTECTED]
ING.COM> To
Sent by: IBM [email protected]
Mainframe cc
Discussion List
<[EMAIL PROTECTED] Subject
.EDU> Devices online at IPL should be
offline
11/12/2008 10:25
AM
Please respond to
IBM Mainframe
Discussion List
<[EMAIL PROTECTED]
.EDU>
I have been racking my brain trying to remember how to do this (again).
I have a series of replicated devices that should be offline at IPL. If
they are not, then I get IEA213A DUPLICATE VOLUME which really annoys
operations.
In the IODEF they are defined as online. In my COMMNDxx they are defined
as offline.
I know that the message IEA213A is probably during NIP processing. So how
to I ensure that NIP does not try to bring these devices online? My memory
on this one is just swiss cheese.
Lizette
----------------------------------------------------------------------
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
