Lucas Rosalen wrote: >+1 for REPRO MERGECAT. >I've done this for Netview's datasets - with all Netview's STCs down because >I'm a chicken :)
Let me cheep-cheep in, just as soon as I hatched from my (rotten?) egg, I did the same (Move, REPRO, Rename HLQ, all the works including using a new PU - LU settings in a new VTAM on another LPAR) for Netview Access Services VSAM datasets while that Netview Access Services STC was down and out ... ;-) Uhm, no beautiful chicks were available then ... Oh, BTW, when they complained they could not logon using the old LOGON APPLID(<old NVAS name>), I discovered I'm really very low in the pecking order... Ok, back to the topic: Peter, could you be kind to describe WHAT is your STC and WHAT dsn(s) you want to move via recatalog? Others gave you good solutions, but you can also rename them to something else, fix your aliases and rename them back. Yes, I know it is a PITA especially if they're really 'busy'. But, since you mentioned DB2, if they're DB2 database datasets, then, during non-peak hours, stop all the subsystems, do your thing and restart them. That is if you can't copy/move the contents to a brand new set of datasets. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
