> The dialogs do not allow SYS1. to be uncatalogued. Are you saying that on the Catalogs page in the configuration wizard, the SYS1 prefix row contains "Yes (required)" for the "Catalog the data sets" column and would not allow you to select action "Do Not Catalog data sets"? If that is the case, then it means there is one or more data sets with that prefix that must be cataloged because of the data set type or its usage. For example, zFS, VSAM, SMS-managed, multi-volume, a data set containing a workflow definition file; these are all reasons why a data set must be cataloged.
> ... I leave SYS1. as cataloged and get all kinds of errors saying that the > files are already cataloged….duh. It sounds like you want the data sets to be cataloged, but you want them indirectly cataloged. That is, you want the catalog entries to specify a variable for the volume that contains your SYS1 data sets, like "******" or "&SYSR1" or similar, so that you can use the same catalog to IPL the driving system as well as the new target system. Does that sound about right? If so, then you must tell z/OSMF that you want indirect cataloging for the data sets on that volume. You do this on the Volumes page in the Configuration wizard. Select the SYSRES volume and click Modify, then select "Indirect" for the Catalog method field. Then specify the variable you want to use for that volser. 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
