General rules for HCD activation
It is easier to add than to remove (or alter) devices.
For remove, you have to vary/configure device/chp offline. Where? Everywhere on the CPC, that means each LPAR. It is nothing weird in having multiple non-sysplexed LPARs on CPC and dynamict activation. For dynamic activation when multiple z/OS LPARs are active there is following method: - do the checks, vary offline altered devices on every LPAR, repeat ACTIVATE TEST
- on every system except last perform ACTIVATE SOFT
- on last system perform ACTIVATE without the SOFT. That will also update HSA and since then every system will have definitions in sync.
- upload IOCDS on Support Element. DON'T FORGET IT.

Personally I used to start with "the last system" - that means HSA update, and then ACTIVATE SOFT on rest, however the "more recommended" way is the above.

Remarks:
Every system need access to IODF file. It can be shared file (convenient) or just copy of the file. How to get a copy of VSAM file is out of scope ;-) however take care - this file HAS TO BE SINGLE EXTENT. Check it before you start.

Assuming no changes in CF (and channels to CF), it doesn't matter whether given z/OS image is sysplexed or not.

Sysplex members on different machines always have different configuration, even when it comes from single IODF file. It's obvious: every machine has its own set of channel, etc. And sysplex member may have some non-shared devices.

For shared devices within sysplex there is no black magic, of course there are devices crucial for sysplex like CDS volumes, however you will find it out when trying to offline them.


--
Radoslaw Skorupka
Lodz, Poland







W dniu 21.05.2020 o 20:27, Mark Jacobs pisze:
I have a followup question on this topic. In addition to the 8 z/OS systems in 
the sysplex, we have several standalone monoplex z/OS systems on the same CEC. 
If I perform the HCD work in the sysplex, then transfer the IODF file to one of 
the standalone systems, perform a software and hardware activation there, will 
the IODF tokens match between the hardware and software in the members in the 
sysplex once they're all IPLed with the new IODF?

My goal is to keep everything in sync without needing a POR of the processor.

Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email.

GPG Public Key - 
https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



======================================================================

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

Reply via email to