I'm trying to understand IDCAMS NODISCONNECT to correct a UCAT entry in a new master catalog. After I created a new master, another sysprog successfully moved a UCAT to a different and larger volume. My goal is to correct my new master catalog without affecting the heavily used production UCAT and defined ALIAS. BTW the new master catalog is defined as a UCAT to the existing master catalog for z/OS HLQ ALIAS.
Both DFSMS Technical Update and A Practical Guide to ICF Catalogs have the same example: DELETE UCAT.RLSTST USERCATALOG RECOVERY NODISCONNECT and DEFINE USERCATALOG - (NAME(UCAT.RLSTST ) ICFCATALOG - VOLUME(MHL1A0) TRK(5 1) - STORCLAS(SCRLS) - DATACLAS(WELCHRLS) - LOG(NONE) RECONNECT - FREESPACE(0 0) - NOIMBED NOREPLICATE) - DATA (CISZ(4096)) /* Anyone have experience with this process? Are all the DEFINE UCAT parameters required, besides VOLUME and RECONNECT? Another solution come to mind: rebuild the new master catalog with the proper UCAT volume entry. As part of that, I'm using RCNVTCAT. Thanks. David ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
