One option for the high volume of SMF data is to use a 3rd party tool such as TMON, MAINVIEW, OMEGAMON, or DB2 PE to route the DB2 trace to an alternate destination. DB2 its self has this functionality but lacks the functionality for data set management. (Copy switching)
GTF is not a good choice. Like DB2 its self it lacks the required data set management support. I think only one copy of GTF can run at a time and GTF is needed for other things from time to time so 24x7 DB2 data collection is out of the question. The best solution is to improve your internal off load processes. Moving the data capture from SMF to a different product component is like rearranging the deck chairs on the titanic. If you do not handle the underlying problem the ship is going to sink. Two additional things to look at .... There are features in DB2 V8 and CICS that aggregate some types of trace and accounting records prior to them being externalized. There is some recent APAR history that addresses incorrect high volume SMF record generation. Avram Friedman 877-311-0480 ---------------------------------------------------------------------- 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
