Herve,

   I understand what happen with the recovery log. Actually I had tape mount
contention and the DBBACKUP command didn't run before the log filled up.

   What I want to understand is why a command line logon failed but yet the
Web Admin logon worked with the same id. Until I resolved the mount
contention and got the DBBACKUP to run I wasn't able to login from a command
line.

Curt Magura
Lockheed Martin
Enterprise Information Systems
Gaithersburg Md.
301-240-6305


                -----Original Message-----
                From:   Herve Chibois [mailto:Herve.Chibois AT fr.abnamro DOT 
com]
                Sent:   Thursday, November 18, 1999 11:42 AM
                To:     curtis.magura
                Subject:        Re: Explain This......

                Hello


                To avoid this you should set the DB TRIGER STATUS to some
thing near 60%
                or 80%

                adsm > q status
                ...
                     Database Backup Trigger: 80%

                adsm >  DEFINE DBBACKUPTRIGGER ...

                Hope this helps
                Rv





                curtis.magura AT LMCO DOT COM on 18/11/99 14:42:00
                To:     ADSM-L AT VM.MARIST DOT EDU
                cc:      (bcc: Herve Chibois/FR/ABNAMRO/NL)
                Subject:        Explain This......

                Came in this morning went to logon to ADSM to do the normal
checking to
                verify the overnight activities ran as expected and found
that my password
                was failing. Tried it again - Still failed. Hmmm.... Logged
on with a
                different id.... Same thing password failure! This was tried
using an
                admin
                command line (TSM 3.7.1 /NT 4.0 SP4) under an Intel client
and also
                directly
                on the ADSM server (AIX 4.2.1 / 3.1.2.22) / ADSM Client
3.1.07

                Not sure why I tried this but just for kicks I went to the
Web Admin
                interface. Logged in using the same id and password that
failed from the
                command lines and guess what.... IT WORKED!

                Switched back to the command line and still couldn't logon
even though in
                another window I was logged on from the Web interface.

                After poking around a little I discovered that the recovery
log had filled
                up due to mount contention for a tape during the database
backup.

                Not sure I understand why I was able to logon from one but
not the
                other?. I
                guess the good news is that I was able to logon and correct
the underlying
                problem but why couldn't I use the command line interface?
As soon as I
                was
                able to get the database backup to run and recovery log
corrected all
                logon
                work normally from all interfaces.

                Curt Magura
                Lockheed Martin
                Enterprise Information Systems
                Gaithersburg Md.
                301-240-6305