No, the SAVESCDS or SAVEACDS appears to be an ALL or Nothing type process. It does not allow for selective extractions.
But, depending on how much to do one way or the other. If you used the original SCDS and then once it was active just go into the ISMF Panels and DELETE what you did not want, it might be an easier process than manually entering everything you want on that lpar. However, if the SCDS has 2000 entries but you only needed 5 - then manually entering them would be more efficient. Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Raju Reddy Sent: Wednesday, October 09, 2013 6:36 AM To: [email protected] Subject: Re: New LPAR build - Storage activities - SMS/ACS Functionality Kee, Nope. They are manual ISPF entries so they won't be in SCDS :-( Lizette Koehler, You understood my problem very well. I have not come across any suggestions/options to copy ISMF entries from one LPAR to another LPAR's ISMF. So I am planning to define them manually. But I still hope to see some ideas here...!!! Cheers, Raj On Wed, Oct 9, 2013 at 2:23 PM, Lizette Koehler <[email protected]>wrote: > Thanks Allan, > > I have never had to use the SAVESCDS command. We use a backup > procedure that has been in place for a long time > > But from the manual > > SAVEACDS(dsname) > Specifies the ACDS that SMS is to use to save to DASD the active > configurat1ion from the SMS address space. SAVEACDS is one way to > create a backup ACDS. Do not specify SAVEACDS in the same command as > ACDS, SCDS, or SAVESCDS. > > SAVESCDS(dsname) > Specifies the SCDS that SMS is to use to save to DASD the active > configuration from the SMS address space. SAVESCDS is one way to > create a backup SCDS. Do not specify SAVESCDS in the same command as > ACDS, SCDS, or SAVEACDS. > > So unless the OP is familiar with this process, this new system is > probably a good way to work on a recovery procedure until it goes Live. > > > This has been very educational, I will be looking at "improving" our > DR procedures. > > > Lizette > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Staller, Allan > Sent: Wednesday, October 09, 2013 6:12 AM > To: [email protected] > Subject: Re: New LPAR build - Storage activities - SMS/ACS > Functionality > > Yes. > > On the "original" LPAR SETSMS SAVESCDS(some name) On the "new" LPAR > SETSMS SCDS(some name) > > Obviously "some name" must be available (via export/import, shared > dasd,...) > to both the source and target LPARS. > BTW, it would be a good practice for "some name" to be unique for both > source and target. > Saves many "oh no" seconds.* > > *oh no second. The second between hitting the enter key and realizing > your error. > > HTH, > > <snip> > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Lizette Koehler > Sent: Wednesday, October 09, 2013 7:58 AM ... > Okay, I am going to retract what I have said so far. I think I am > seeing the OP question. > > The functions in ISMF were manually entered via the panels for Storage > Class, Data Class, and Management class. > > The Source PDS is strictly for the ACS routines that assign those > definitions as needed. > > Currently - I do not know of a way to "EXPORT" the Classes that were > manually defined with the Panels and put them in a "PDS/FILE" to be > able to "IMPORT" them to another system SCDS dataset. > > The only process I am familiar with is to DUMP/RESTORE the SCDS you > like and then activate it on the new LPAR. > > I am not sure if you could use IDCAMs to EXPORT the current SCDS and > then IMPORT that file into a new SCDS dataset. > </snip> > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
