Nice. It's been (I would guess) several releases since I worked with CA 1. Maybe 5.2 era? Either I was unaware of the UNCATA option, or it wasn't available at the time. Having two-way communication between TMC and OS-CAT makes sense, and cuts the work in half.
On Sat, Feb 20, 2016 at 8:09 AM, Russell Witt <[email protected]> wrote: > Based on the UNCATA option setting, chances are that CA 1 will do the > un-catalog from the MVS/Catalog once the volume is scratched. For CA 1, > there is also a batch job (TMSUNCAT) that takes the output from TMSCLEAN > (the scratch list) and will un-catalog all entries. This is useful for > sites with unique un-shared MVS/Catalogs but use a single shared TMC. Or > for clients that want to improve the performance of TMSCLEAN (doing > thousands of un-catalog's takes a lot of time, so this off-loads that > process). > > Russell Witt > CA 1 > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Steve Horein > Sent: Saturday, February 20, 2016 5:50 AM > To: [email protected] > Subject: Re: Question on CA-1 > > Isn't the job only half done if the now obsolete entries are still in the > system user catalogs? > Wouldn't removing the obsolete GDGs from the user catalogs also clean up > TMC "catalog controlled" entries during the next scratch run? > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
