Yet another answer to my own post.... I stripped out everything to do with the Software instances and deployments related to my Zos25 install.
I defined an instance for my new deployment This instance was modeled on my ZOS V2R4 install. The source for the instance is the downloaded ShopZ ZFS. The Dataset names had to be trimmed due to assumptions and defaults prefixed to the Target dataset names. The names were modified to match what they will have to be when I continue to use the indirect cataloging in my active system. Volumes and Storage Classes were assigned to local standard locations for DASD placement. Catalog Selection was NOT a chance to select a Catalog for these new to be created datasets. Job generations then fail with IZU9702E messages saying that the dataset in question is ALREADY in that Master Catalog that I am forcing you to use. I am assuming that this is because I am NOT creating a new master of any kind (temporary or other). This is because I actually read my choices for configuring the objectives of the install. and the 'no new catalog' option where you IPL using your old indirect catalog entries from your existing master catalog described exactly what I think I want to do. Do I want to change the objectives to create a new catalog where all the building would be done? If so, what the heck is the 'Existing' catalog objective for?? Time to step back and wait for a flash of brilliance to come to me. Mandatory cooling off period starts........... NOW ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
