W dniu 2013-07-18 12:38, Scott Chapman pisze:
TDMF has worked fairly well for us for migrating between control units without
taking an outage. Just did so within the last month matter of fact. I thought
it was fun (and useful) that D IPLINFO shows both the original address you
IPL'ed from as well as the current. I don't remember noticing that last time we
did a TDMF migration (~4.5 years ago), but I may simply not have looked.
IEE254I 06.33.28 IPLINFO DISPLAY 326
SYSTEM IPLED AT 11.20.21 ON 05/19/2013
RELEASE z/OS 01.12.00 LICENSE = z/OS
USED LOAD0J IN SYS1.IPLPARM ON 04678
ARCHLVL = 2 MTLSHARE = N
IEASYM LIST = (MJ,L)
IEASYS LIST = (MJ) (OP)
IODF DEVICE: ORIGINAL(0624A) CURRENT(04678)
IPL DEVICE: ORIGINAL(06252) CURRENT(04304) VOLUME(RES600)
Non-disruptive application releases take a little more work. I believe it's not
necessarily impossible though, depending on how the application is architected
and how much effort you want to put into it.
Scott,
I'm aware of TDMF and realize that application release could be
non-disruptive - this is code (software) and data - as in microcode
upgrades or z/OS migrations. However it wasn't my point. My point was
that even if someone claims no planned outages, that usually means "no
planned regular "tech windows", but does not include software releases
or (sometimes) does not include hardware change. BTW: There is a *big*
difference between preparatin of new software release and preparation
new software release *and* non-disruptive rollout. That's at least
opinion claimed by authors of i390 (CPC microcodes). Note they don't
have multi-TB databases with possible data model changes.
Last, but not least: sometimes "binary approach" is not applicable, for
example you can shut majority of software modules/functionality, but
keep some 24x7 part alive during the process. Partial outage.
Regards
--
Radoslaw Skorupka
Lodz, Poland
P.S. What about people having maint windows and still using obsolete things?
--
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 authorised 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.
BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax
+48 (22) 829 00 33, www.brebank.pl, e-mail: [email protected]
Są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.2013 r. kapitał zakładowy BRE Banku SA (w całości wpłacony) wynosi 168.555.904 złotych.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
