> I think I messed up the original deployment then. The newnames all have CB > and the order number prefix on them.
> ALTER - > NEWMCAT.CB.OS313256.TCPIP.SEZAEXEC - > NEWNAME(CB.OS313256.TCPIP.SEZAEXEC) - > CATALOG(CATALOG.MCAT) > Is the only way to recover to restart the deployment? Ouch. If you already ran any of the generated jobs, then the safest option is to manually cleanup/delete the results of running those jobs. Then go back to the "Configure this deployment" step in the deployment checklist and modify the deployment configuration to your liking. By the way, it appears you chose the option to create a new master catalog, and you kept the default temporary catalog alias (NEWMCAT) and catalog name (CATALOG.MCAT). Is that what you want? If not, then on the Catalogs page in the deployment configuration wizard, select one HLQ and click the Modify action to modify the properties for the new master catalog. After you modify the configuration and regenerate the jobs, click the link to "View the deployment summary" and review very carefully. The Summary shows you exactly what will happen when you run the jobs. Go back and modify the configuration as many times as you need to get the Summary, and the generated jobs, correct before submitting any of the jobs. Reach out to me if you have more specific questions or confusion. Kurt Quackenbush IBM | z/OS SMP/E and z/OSMF Software Management | [email protected] Chuck Norris never uses CHECK when he applies PTFs. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
