We have both parallel sysplexes and monoplexes. SMS runs on every image. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com
-----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Richards, Robert B. Sent: Tuesday, May 19, 2020 8:58 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Creating new SMS environment in a monoplex CAUTION EXTERNAL EMAIL Thanks, Radoslaw. My point, and I think you have also confirmed it, is that an SMS environment has no specific dependence on a parallel sysplex, CFs, couple datasets, etc. All that is left for me is to finish building the system and IPL it. Bob -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of R.S. Sent: Tuesday, May 19, 2020 11:21 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Creating new SMS environment in a monoplex 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
