Onbar, ADSM, and logical logs

We use OnBar and ADSM. When OnBar backs up logical logs ADSM uses the "uniqid" value as the low-level file name. The ADSM Policy Domain has been configured to keep three generations of a file so the standard OnBar backups of root and dbspaces cycle through and expire automatically. But because the logical log "file" is unique as far as ADSM is concerned it is never expired because a replacement (newer version) has never been saved. I have thousands of these un-expired files sitting on ADSM library tapes that can't be automatically recycled by ADSM. Has anyone else using OnBar and ADSM conceived of a solution to expire log files? Thanks.

In article <8i8din$eau1@netnews.state.az.us>, Fred Prose <fprose@supreme .sp.state.az.us> writes >We use OnBar and ADSM. When OnBar backs up logical logs ADSM uses the >"uniqid" value as the low-level file name. The ADSM Policy Domain has been >configured to keep three generations of a file so the standard OnBar backups >of root and dbspaces cycle through and expire automatically. But because >the logical log "file" is unique as far as ADSM is concerned it is never >expired because a replacement (newer version) has never been saved. I have >thousands of these un-expired files sitting on ADSM library tapes that can't >be automatically recycled by ADSM. > >Has anyone else using OnBar and ADSM conceived of a solution to expire log >files? > With IDS 7.31.UC6 there is a tool called onsync (or omsync?) which should help. >Thanks. > > > -- David Williams