W dniu 2018-07-09 o 13:12, Vernooij, Kees (ITOPT1) - KLM pisze:
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of R.S.
Sent: 09 July, 2018 12:47
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Sysplex between two hardware
W dniu 2018-07-06 o 18:22, Jesse 1 Robinson pisze:
We all have lots of questions about your goals here, but the short
answer to your question is Yes, sysplex is the answer. I assume that
your two boxes are already connected in some way as to share access to
data. Turning such a configuration into a sysplex may require some
additional hardware, but not a lot.
-- If you want a full-function parallel sysplex, you would need to
create an internal coupling facility LPAR (ICF) in each CEC.
-- You would need CF links to connect each ICF to the opposite CEC.
-- I think you would also need server timing protocol (STP) to keep
clocks in synch; I have not tried running without STP.
STP (or earlier sysplex timer) is mandatory for sysplex, even for basic
sysplex.
For production parallel sysplex it is good idea to have standalone CF.
--
Radoslaw Skorupka
Lodz, Poland
In this case: yes, but to be precise: not if you run a sysplex on 1 box. The
required 'common time source' can then be the time of that machine.
I thought the recommendation of a standalone CF was not current anymore.
Well, I was suggested by the topic - "two different hardware".
Regarding CF and availability - for availability reasons one should
avoid having CF and z/OS LPAR on the same hardware, which means:
a) at least 3 CPCs (of course CF-only box is much cheaper)
b) use CF structures replication which gives some performance penalty,
especially for non-local distances.
Regards
--
Radoslaw Skorupka
Lodz, Poland
======================================================================
--
Treść tej wiadomości może zawierać informacje prawnie chronione Banku
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość
włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.
This e-mail may contain legally privileged information of the Bank and is
intended solely for business use of the addressee. This e-mail may only be
received by the addressee and may not be disclosed to any third parties. If you
are not the intended addressee of this e-mail or the employee authorized to
forward it to the addressee, be advised that any dissemination, copying,
distribution or any other similar activity is legally prohibited and may be
punishable. If you received this e-mail by mistake please advise the sender
immediately by using the reply facility in your e-mail software and delete
permanently this e-mail including any copies of it either printed or saved to
hard drive.
mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,
www.mBank.pl, e-mail: kont...@mbank.plsąd Rejonowy dla m. st. Warszawy XII
Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców
KRS 0000025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2018 r. kapitał
zakładowy mBanku S.A. (w całości wpłacony) wynosi 169.248.488 złotych.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
