Thank you for your reply, Kurt. Things have moved on somewhat. Having cancelled the deployment dialogue and started again (possibly with a different 2.4 software instance - I am not sure which one I selected the first time) I found that most of the datasets were correctly matched against the 2.4 configuration and correctly renamed to match those 2.4 datasets. This clears up any confusion I may have had about what dataset names should be used - the eventual target dataset name (which it should in fact be), or the server pack source name or some other name involving an SSA. Maybe the first few datasets that I viewed on my first attempt were ones which could not be matched (eg not target or club zone datasets, or new datasets). Never mind - that is fixed now.
Incidentally I find it really irritating that I cannot log off or somehow save my configuration changes before they are complete. I have had to start again several times because my dodgy home internet connection has temporarily failed. With regard to new volumes : I will initialise a new target and dlib volume before doing the configuration again (I had to start again because I left the session open for a few hours and the connection dropped). I did select ‘use existing master catalog’. Most of the operational datasets (eg SYS1.RACF) will not be required but they still appear on the deployment configuration deployment panel. We do use a few of those (eg CPAC.PROCLIB and CPAC.Linklib, which we always rename as SYS1.CPAC.PROCLIB and indirectly catalog on the sysres) but I am considering leave no most of them with the source name CB.ST25nnnn.* - if these are indeed created by the dialogue I will be able to recognise them easily. I also decided that the reason that there is no detailed documentation is that , after some initial confusion, the dialogue is intuitive . In general I am impressed - it is, or will be, better than the system it replaces. Keith Gooding > On 12 Oct 2021, at 16:39, Kurt J. Quackenbush <ku...@us.ibm.com> wrote: > > - I have attempted to model the configuration on a 2.4 software instance > which > I created, but although the zone names are primed with the 2.4 values none > of > the dataset names have been primed with the 2.4 names. Should I set the > names > to their eventual values (eg SYS1.Linklib) or leave them as the source > values > with the expectation that a later step will rename them ? > > No later step will rename the data sets. Not sure why the model > processing did not find matches for most of your data sets, but update the > target data set names on the Data Sets page to your desired data set > names. > > - An attempt to change the target volser is rejected because the volume > does > not yet exist. In the ISPF version there was a job to initialise new > volumes. I > am aware that z/OSMF does not yet include all of the old method functions > but > have I missed something here ? > > No, you have not missed anything. z/OSMF does not provide a capability to > define a new volume. You do have an option to initialize an existing > volume so it will be empty before any new data sets get created, but no > option to define a volume that does not already exist. > > - I want to use the equivalent of a Serverpac upgrade ie the existing > master > catalog is used with indirect cataloging. On the ISPF version there was a > step > to validate the entries in the master catalog and create new entries as > required. On the Catalogs page, should I catalog the datasets or not ? > > Yes, indicate the data sets will be cataloged. An indirectly cataloged > data set is cataloged, not uncataloged. Then, on the Volumes page, use > the Modify action to indicate data sets on that volume will be indirectly > cataloged and specify the symbol to use for the volume in the catalog > entries. Curious, did you select the "Existing master catalog" option in > step 3 of the Deployment Checklist? > > Kurt Quackenbush > IBM | z/OS SMP/E and z/OSMF Software Management | ku...@us.ibm.com > > 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
