W dniu 10.07.2020 o 20:19, Michael Babcock pisze:
We are in the process of bringing DR back in-house and have a new
z15-T02 in our new facility (our current "home" machine is a
z14-ZR1). I want to be able to manage both processors from a single
IODF. I'd like to have the same CHPIDs, CUs, and Device addresses
both at home and in our DR machine. I have the new processor defined
in our current IODF and have used the CHPID mapping tool to map the
PCHIDs to CHPIDs. I have tested adding devices with the same address
to both processors and that seems to work (as long as I define the CUs
to both processors first. I tested adding a range of 16 tape drives).
My questions are this:
1. Is this something we even want to do (same IODF, same device
addresses)?
2. What's the best way to move the IODF at home to the DR machine?
3. Are there any gotchas we need to watch out for?
4. We have IBM DS8886s and are using Metro Global Mirror Multi-Target
w/Practice. Any concerns here?
5. Am I crazy for even entertaining this idea?
6. Any alternatives I need to consider?
General opinion: always use single IODF, even for machines in different
locations. Even for machines with no relationship like sysplex of shared
DASD. Just keep all your realm in single IODF. Exceptions could apply,
but IMHO it would mean specific scenario.
Why? It's easier to maintain, it provide consistency, it eliminate some
potential errors, etc.
It is especially convenient for machines within parallel sysplex.
Sysplex links definition by default assume single IODF (however it is
possible to use different IODFs).
Answers:
1. Yes. It is good idea to have single "numbering convention" on each
machine.
2. There are many ways. Note: another machine also need IOCDS. For the
first time (new machine) you do as usual - use txt input. For IODF you
can use shared disk volume, remote copy (PPRC, SRDF), or some
backup-restore method, including transfer to/from PC. For regular use
clone (point in time copy) of your IODF disk seems to be the most
convenient.
Note: any method is much more convenient than keeping two separate IODF
files.
3. Check you addressing conventions. Especially disk and tape. For
"embedded" devices like OSA ICC terminals and OSA network it is nothing
wrong to use same devices and CU for many machines. It is some planning
excercise, but worth it.
4. Another argument pro.
5. No, this is good idea.
6. Obviously you can still have separate IODFs, but this is worse than
single IODF.
--
Radoslaw Skorupka
Lodz, Poland
======================================================================
Jeśli nie jesteś adresatem tej wiadomości:
- powiadom nas o tym w mailu zwrotnym (dziękujemy!),
- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś
na dysku).
Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać
tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza)
tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać
karze.
mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st.
Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 0000025237,
NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na
01.01.2020 r. wynosi 169.401.468 złotych.
If you are not the addressee of this message:
- let us know by replying to this e-mail (thank you!),
- delete this message permanently (including all the copies which you have
printed out or saved).
This message may contain legally protected information, which may be used
exclusively by the addressee.Please be reminded that anyone who disseminates
(copies, distributes) this message or takes any similar action, violates the
law and may be penalised.
mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950
Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital
City of Warsaw, 12th Commercial Division of the National Court Register, KRS
0000025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN
169.401.468 as at 1 January 2020.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
