> What about datasets that are not in the CSI, e.g., CPAC.*? When you use a model to initialize the deployment configuration, data sets not managed by SMP/E, like the CPAC.* data sets, won't be initialized to your existing data set naming conventions. The same is true for new data sets that don't have a match in the model. They get initialized with the data set name used by the ServerPac production process. On the Data Sets page in the deployment configuration wizard data sets that did not have a match in the model are identified by a message in the row, so its easy to determine which data sets need some attention. However, those data sets should be few in comparison to all of those that will get matched with the model.
> > > I do echo Terri's sentiments that there should be a way to mostly > > > seed a new z/OSMF instance whether there is a utility that reads the > > > last saved custompac config or somehow scans your sysres. > > > > That is exactly what z/OSMF offers! You can "model" your installation > > configuration on your existing installed software. For example when > > installing z/OS 2.5, simply define your existing z/OS 2.4 (or 2.3) as a > > Software Instance. (Use the Software Instance -> Add action, specify the > > global zone CSI, select the target zones from that global, and that's it!) > > During the deployment you can select this Software Instance as your model > > and z/OSMF will analyze your DDDEF entries in your existing CSI to > > determine your desired data set names and match them up with the new > > software as much as possible. > > > > Honestly, we did try to help you avoid a bunch of changes in the > > configuration. Perhaps we need to advertise it more, but the Model > > function is your friend. Kurt Quackenbush -- IBM, z/OS SMP/E and z/OSMF Software Management Chuck Norris never uses CHECK when he applies PTFs. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN