> > The Managing Catalogs manual describes this sequence with a DELETE and a > DEFINE between the export and import, so the import is into an empty > catalog. In this case, jobs referencing the catalog would probably get > upset. > > Why do you wnat to do this if you are not going to empty the catalog > first? > > Jim McAlpine <[EMAIL PROTECTED]> wrote: > Is it ok to do the following - > > LOCK CATALOG > EXPORT CATALOG > IMPORT CATALOG > UNLOCK CATALOG > > while there are jobs referencing datasets in the said catalog, or should I > wait until the work is quiesced. > > Jim McAlpine >
<war story> Many years ago, a customer was following this procedure. Soon after the UNLOCK CATALOG, jobs started have catalog problems. It was deemed that the Ucat was corrupt, and a backup copy was restored (using LOCK/UNLOCK). The problems persisted. OPC (Job scheduling tool) was defined as Privileged in the ICHRIN03, so the Catalog locking wasn't observed. It took a while to clean up. </war story> John ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
