W dniu 18.05.2020 o 20:36, Richards, Robert B. pisze:
It has been a few decades since I have created a new SMS environment.
Current environment is parallel sysplex replete with CFs and lots of lpars.
I am trying to create a simple SMS environment that will be part of a monoplex
consisting on one lpar.
I did the following:
1. Defined the new SYSNAME into the base configuration in ISMF and
activated same. D SMS verified it was defined and not active
2. A REPRO of the SCDS into a new SCDS dataset (Alter/newname to correct
usercat)
3. Issued a SETSMS SAVEACDS(also using a SSA connector that I subsequently
ALTER NEWNAME the new ACDS into a new usercat that is connected to a new
mastercat)
4. Defined an empty COMMDS that I also performed an alter/newname to get
the desired COMMDS dataset name.
My boss says the ACDS is aware of the original sysplex environment and my
gyrations of trying to make the above work in a monoplex will not succeed.
Who is right? Will it work or not?
Quick and dirty method:
1. Add new system name to existing SCDS and ACDS. Don't worry, it is
nothing wrong to have non-present system names there.
2. Copy all *CDS to disk belonging to new system.
3. IPL the system.
Of course this is method for some migration. ACS routines, class
definitions and library definitions will be moved. Is that what you want?
Otherwise there is another method, to start from scratch. ACS routines
can be easily imported, class definitions - the only way I know is to
re-define them manually.
BTW: some dummy SMS environment is delivered with ServerPac. I always
start from that point. Then IPL with CPAC system name, then add my name
to ACDS then reIPL with my system name. Then *CDS datasets can be
imported (copied). Piece of cake.
--
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
