Great information Kurt, thanks, but need a clarification on one thing. I was able to get the migration workflow now, that's the steps I was missing.
>>That's great! You would choose any of these software instances as your model >>when installing z/OS next. You can also experiment with other Software >>>>Management actions on those defined software instances. For example, on >>the Software Instances page try the View -> Data Sets action. >>Or any of the Maintenance Report actions. So does this means I will always have to change every dataset again? To add my SYS1SSA, CPACSSA and SMPSSA? Because the instances all point to the real names. If so you lost me again, because that was pain staking to change 1200 datasets, even with filtering. At least the SERVERPAC just prefixed everything with you SSA HLQ's. I would have thought the Portable would work as the model.. otherwise YUCK!! Ms Terri E Shaffer Senior Systems Engineer, z/OS Support: ACIWorldwide - Telecommuter H(412-766-2697) C(412-519-2592) terri.shaf...@aciworldwide.com -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Kurt J. Quackenbush Sent: Thursday, October 28, 2021 11:16 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Serverpac installs January 2022 and beyond - Issues External Email > So just a few clarifications. > > I am guessing when I install z/OS 2.6, not sure what my model is, an > instance or the portable 2.5 order? A model is a software instance representing your actual installed software, no matter how it was installed, not a portable software instance. > Because the portable copy still has all the install names like > SYS1SSA, SMPESSA, CPACSSA for dataset names and it doesn't seem like I > can change them. > > But then if that my model for z/OS 2.6, then it should work with > everything I setup already, Again probably just a learning curve. > > So, I was trying to use my z/OSMF (Serverpac install for 2.5) as a > base for my software instance. > > That's wrong, because it wants to duplicate everything that came with > that process. > > Once I just pointed to the SMPE datasets, you are correct it went > after the DDDEF's and found everything correctly. > > I have now built a 2.3, 2.4 and 2.5 instance that matches my shop. That's great! You would choose any of these software instances as your model when installing z/OS next. You can also experiment with other Software Management actions on those defined software instances. For example, on the Software Instances page try the View -> Data Sets action. Or any of the Maintenance Report actions. > z/OSMF still has a few quirks, depending on how you access things, > Like my first comments about modifying datasets names. But I > eventually got it to work. > > z/OS will be my first real install using z/osmf, so I am hoping all > the nuances will be worked out, by then. > > Lastly, I want to thank Barbara for the link to the migration guides. > I still don't understand were they are in z/OSMF or how to access, but > for another day. Briefly, the z/OS Upgrade Workflow files will reside in /usr/lpp/bcp/upgrade/. There are several files depending on your upgrade path. Open the z/OSMF Workflows application, click Actions -> Create Workflow, specify the appropriate file name in the Workflow definition file field, for example, /usr/lpp/bcp/upgrade/zOS_V2.5_from_V2.4_Upgrade_Workflow_V2.0.xml, and click Next, then click Finish. This will create and open an instance of the upgrade workflow. You can then perform the steps of the workflow ... much like reading the upgrade actions in the older style Migration Guide. 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 ________________________________ [https://go.aciworldwide.com/rs/030-ROK-804/images/aci-footer.jpg] <http://www.aciworldwide.com> This email message and any attachments may contain confidential, proprietary or non-public information. The information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this email, please notify the sender immediately and destroy this email. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this email are those of the author personally. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
