Thanks for your response.  The problem was resolved by running the
SQL-Backtrack supplied setup script and answering the questions.  Prior to
that, the DBA's had just modified the sample file to use our values.  I
believe the sample file uses management class where the script creates a
backup class.

On Sun, 27 Dec 1998, Hilton Tina wrote:

> Where are you specifying the management class?  In an ADMS include/exclude
> file or in SQL-Backtrack?  We use SQL-Backtrack for Oracle databases and
> specify the management class in the SQL-Backtrack options and it works fine.
> Do you get any error messages when you run the backup?
>
> Tina
>
> > -----Original Message-----
> > From: Joel Fuhrman [SMTP:joelf AT CAC.WASHINGTON DOT EDU]
> > Sent: Wednesday, December 23, 1998 8:51 PM
> > To:   ADSM-L AT VM.MARIST DOT EDU
> > Subject:      SQLBackTrack isn't using desired management class
> >
> > The dba's backed up some Sybase databases using SQLBackTrack to the
> > STANDARD
> > management class.  Later I created a copy and management class named
> > BACKTRACK.  Since then, we have been trying, without success, to get
> > SQLBackTrack to use the new management class.  We have tried entering the
> > management class name in all lower case and then in all upper case.  But,
> > according to the output from a " show versions lj /BACKTRACK:* " the MC:
> > is
> > still DEFAULT.  Any suggestions?
> >
> > env: AIX 4.2.1-03   ADSM Server 3.1.2.1   ADSM API Client 3.1.0.5
>