What I sometimes did in the past for such massive updates that make the log fill faster than log backup can clean: - place the updater in CP SLEEP - issue CP SEND VMSERVx BACKUP to empty the logs - "unSLEEP" the updater.
2008/7/11 Alan Altmark <[EMAIL PROTECTED]>: > On Friday, 07/11/2008 at 01:51 EDT, "Imler, Steven J" > <[EMAIL PROTECTED]> wrote: > >> That being said, what's the correlation between the error I got and the >> LOG filling up? (At least I assume the LOG filled up?) > > What was returned in the WUERROR field, if anything? Some error codes > (i.e. implicit rollback) are part of the wuerror information. > > As to why a log that isn't actually full would cause a rollback, I don't > know. Is there anything you can commit along the way? > > Alan Altmark > z/VM Development > IBM Endicott > -- Kris Buelens, IBM Belgium, VM customer support
