If I understand your note, I all set and only need to add a batch file like so:
sqldsmc /adsmautodelete:*  /ifolder:30
then schedule that file as a command for execution
and associate the node(s) with that schedule, e.g.:
Policy Domain Name: MS-SQLNT
     Schedule Name: SQL-DAILY
  Associated Nodes: LCMSSQL MSSQLAFS MSSQLREM MSSQLSMS


adsm> q copy ms-sqlnt active ms-sqlclass f=d

            Policy Domain Name: MS-SQLNT
               Policy Set Name: ACTIVE
               Mgmt Class Name: MS-SQLCLASS
               Copy Group Name: STANDARD
               Copy Group Type: Backup
          Versions Data Exists: 2
         Versions Data Deleted: 0
         Retain Extra Versions: 30
           Retain Only Version: 0
                     Copy Mode: Modified
            Copy Serialization: Shared Static
                Copy Frequency: 0
              Copy Destination: NTDISKBACK
Last Update by (administrator): ADMIN
         Last Update Date/Time: 11/23/99   14:12:16
              Managing profile:



>>> wzehnder AT JCPENNEY DOT COM 03/22/00 11:41AM >>>
Yes.  Set up a command file on the client server with the following -

sqldsmc /adsmautodelete:* /adsmoptf:xxx.opt /ifolder:21

If you use the default opt file you can leave that parm off and change the 
ifolder parm to any number you feel
is appropriate.  In this case I'm deleting everything older than 21 days.  But, 
they don't actually get
deleted, as I've learned, they just become inactive.  So you will want to 
create a new mgmt class with versions
deleted set to 0.  Then put the following in the xxx.opt file -

Include * newmgmtclass

Then bounce the sql scheduler service.

Oh, you'll also need to create a command schedule to execute the command file 
on the client.

Lawrence Clark wrote:

> Hi:
> I didn't see the beginning of this thread. Is there a way to automate the 
> deletion of older MS-SQL backups?
>
> >>> wzehnder AT JCPENNEY DOT COM 03/22/00 09:11AM >>>
> Thanks, thats what I did wrong.  Question, I created the new mgmt class and
> last nights incremental is bound to that class, but the other inactive backups
> are still bound to the old mgmt class.  Is there a way to rebind them to the
> new mgmt class, or do they have to age off according to the retain only
> parameter of the old mgmt class?
>
> Chris Zaremba wrote:
>
> > Bill,
> >
> > >So I ran the autodelete
> > >command, successfully, and 2072 of 2373 objects were deleted.  When I
> > >check the node with the query occupancy command, it still shows all the
> > >versions exist.  Will I need to wait for the tapes that the deleted
> > >backups reside on get reclaimed, or is something else going on?  I ran
> > >the autodelete last Thursday and expiration and reclamation have run
> > >several times since then.
> >
> > No, the query occupancy numbers will be adjusted after the expiration
> > process is run...if the backups are actually deleted.  Does the management
> > class to which the SQL backups are bound have the versions deleted copy
> > group parameter set to 0 as recommended in the TDP client User's Guide?
> > If not, then the objects will be retained in the server storage pool until
> > the retention period (retain only parameter) expires.
> >
> > Chris Zaremba
> > TDP Client Development
> > internet  zaremba AT us.ibm DOT com 
>
> --
> Cordially,
>
> Bill Zehnder
> 972-431-8733  Fax 972-531-8733

--
Cordially,
Cordially,

Bill Zehnder
972-431-8733  Fax 972-531-8733