I tried to report that as a bug back in ADSM V3; I was told "working as designed". From their point of view, when you change a schedule, it becomes a new schedule and the old one doesn't exist any more. As far as I know, that hasn't changed in TSM. -----Original Message----- From: Christo Heu�r To: [EMAIL PROTECTED] Sent: 7/23/01 8:49 AM Subject: Event records vanish after changing a schedule Hi everyone, Has anybody noticed that when you update a schedule for a client it throws away all the event records for every client connected to this schedule and starts collecting stats from scratch. (This might be a simple change like updating the length of the start-up window). Any idea of why this happens - might have a valid reason or it might be a bug ? We use the event records to generate reports on how many successfull vs. unsuccessfull/bad backups we've had in a monthly period. Server version is 4.1.3.0 on OS/390 2.10. Cheers Christo
