Hi, We just went through the same thing. There is a job that renames the libraries and then creates an alias or path for each one. Once that is run, the catalogs you created for the new system should have the original dataset names (SYS1.NUCLUES, SYS1.LPALIB etc.) and you should be able to IPL from that. The aliases remain on the driving system, so you can access the datasets from there if you want to make changes if the IPL fails for some reason.
Gadi ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Tom Longfellow <[email protected]> Sent: Wednesday, September 6, 2023 19:21 To: [email protected] Subject: z/OSMF and the Old Timer I have had a few minor battles with z/OSMF over the years, so my view may be a bit biased. My new z/OS 2.5 install and upgrade is in progress. I have been going through all of the apps and workflows. All of my local usermods from V2R4 and before are applied. I am a ServerPac veteran and am now pretty pleased with myself on my progress so far. I *thought* I was approaching the point of some initial IPLs and then BAM, all I see is a brick wall. Back in the old days, there were ServerPac jobs to remove the HLQ used during the creation of my new sysres. I have been through the 'Software Management' and 'Software Upgrade' and all the Workflows (that I am now REQUIRED to use) without any success in finding the task/job that would Change HLQ.SYS1.LINKLIB to the good old fashioned SYS1.LINKLIB. Anybody have the secret Point-Click-Edit-Drag-Drop-Whatever sequence that can close out my Deployment to a testable state? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
