W dniu 2018-07-11 o 09:41, Timothy Sipples pisze:
J.O.Skip Robinson wrote:
It's easy to diss a solution as 'budget' when it saves
someone *else* money.
I quite agree.
As it happens, I'm quite fond of the single machine z/OS Parallel Sysplex
configuration that David also describes. I wish more installations without
Parallel Sysplex would adopt it in order to reduce or eliminate most
planned and unplanned outages (for the part of their business services
relying on IBM Z resources). The single machine z/OS Parallel Sysplex is a
terrific value and quite easy to implement. For some odd reason there's a
misconception that if you want to upgrade from PLEXCFG=XCFLOCAL or
PLEXCFG=MONOPLEX that you must add another machine. No, that's not correct.
Moreover, you can run terrifically useful z/OS features such as VSAM RLS
and Transactional VSAM even in a PLEXCFG=MONOPLEX mode with one z/OS LPAR
(or one z/OS guest in z/VM). That's another popular misconception.
Within z/OS Parallel Sysplex configurations you get to decide which
subsystems and applications to protect, and how. As one example, you might
decide to implement MQ shared queues but otherwise not do much else.
Messages can then still be received and queued for processing, even when
the only instance of a particular application (or whole LPAR) is offline
for maintenance or some other purpose. If "Yes, I've got your message, and
I'll get to it soon" is good enough to meet the business requirements
between 3:00 a.m. and 4:00 a.m. every third Sunday of the month, or
whatever, FINE!
There are all kinds of really interesting configuration choices available
to cater to particular business service objectives, and it's wonderful to
have the flexibility. It's important to have some basic familiarity with
these various options if you have a role in advising on configurations.
Timothy,
It's 90% off-topic, but 99% right. The missing 1% is about XCFLOCAL and
MONOPLEX mess. What misconception do you mean?
Monoplex does not require (does not use) CF at all. It is not the same
thing as single-image parallel sysplex, which require CF. Failure
isolation is another issue. RLS require Parallel Sysplex, but not
everyone need it.
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
