The server is AIX 5.2.3 - clients are typically XP, many running 5.1.6. In
all cases they are running the client scheduler service.
I'll have to do some testing with an expired password to see what the dsmc q
sess returns. I can set it to 1 day and wait until tomorrow, I assume - or
is there a way
> Is the client set for PASSWORDACCESS GENERATE?
Yes, this is in our standard optionset for all clients..
Doug
>
> On Tue, 28 Sep 2004 08:28:07 -0400, Doug Baker wrote:
>
> >Hi all. I am wondering what the effects of password expiration are when a
> >client scheduler
ow of automatic
synchronization? Or will it just reset itself the next time it turns on?
We're seeing the former - and thereby an administrator has to reset the
node's password before they can resume backups. Any ideas on if this is
normal, or if something is amiss? Thanks very much,
Doug Baker
Hi everyone,
Currently we're running TSM 4.2.3.0 on AIX, attached to an IBM 3583
library. I'm curious about the prospects of migrating the TSM system
from AIX to Solaris.
1. Is it feasible to do this with the same library? (does the existing
data on the 3583 tapes need to be converted, or can a T
al services
required? Thanks for any info!
Doug Baker
[EMAIL PROTECTED]
I have successfully connected to a TSM 3.7 server via JDBC.
Unfortunately its a bit kludgy. JDBC does not seem to be
compatible with the TSM ODBC driver. (and I've tried everything
from the old ADSM ODBC drivers up to the newest TSM).
But MS Access gets to the TSM db without any trouble, so I mad
o a TSM server
> using a JDBC-ODBC bridge, which it sounds like you are
> attempting to
> do. I'd be very interested in any progress you make
> on getting this to work.
>
> Good luck!
>
> ..Paul
>
> At 04:18 PM 12/6/2000 -0500, Doug Baker wrote:
> >Hello al
es based on Java, servlets, jdbc,
> Informix, et al. I have
> been wondering if there is a way to include JDBC
> access to a TSM server
> using a JDBC-ODBC bridge, which it sounds like you are
> attempting to
> do. I'd be very interested in any progress you make
> on gettin
s under Borland JBuilder Foundation 4.0. But note
that when I try to use the JDBC explorer under Borland JBuilder
3.0 Pro, I get the same problem.
I've also tested this on NT 4.0 - so I suspect it's something to
do with JDBC, snce the same ODBC datasource is fine with Access.
Any advice would be great..
Doug Baker
