yes, forgive me, I criss-crossed my terms.. I was using the Command Center, and the script runs fine. and yes, we do the "connect to dbname user ididid using pwpwpwp"... actually, we can not seem to get just that simple term to work to connect to remote NT databases, via script center, but that statement works fine in command center....
So basically, if I run my script in command center, everything works great.. but if I put the same script into Script Center, we get login ID failure for the NT systems. Regardless, my script contains the login parameters for each database(host and NT). Heck, I even tried just doing a "connect to dbname user idid using pwpw" script in the script center and cant get that to work. Works fine for host connections(db2 connect), but not for remote nt db2 servers.
Possible answer might be that I installed db2 connect after db2 workgroup edition was already installed, could that be my hangup? I did reinstall the fixpack, and everything appears to be running, but could be a snafu...
Or could it be that I am running db2 connect from a personal edition cd? (i.e.- installing db2 workgroup edition from workgroup edition cd, and installing db2 connect from my db2 personal edition cd)
any help much appreciated, I am new to db2, and trying to get everything hashed out....
thanks again
-----Original Message-----
From: Pierre Saint-Jacques [SMTP:[EMAIL PROTECTED]]
Sent: Monday, August 13, 2001 1:23 PM
To: [EMAIL PROTECTED]
Subject: Re: DB2EUG: question with db2 for NT
I think that if you're running your connect command from a script on a
remote system, you must do an explicit connect as in:
db2 connect to dbname user ididid using pwpwpwp
From the Control Center, your function carries the id under which you're
logged on but not so in a script.
HTH, Pierre.
Lee Smith wrote:
>
>
> I have numerous data servers that I will be rolling out to multiple
> sattelite offices across the state. Weekly we have to export certain
> tables from our host system, and import them into these sattelite
> office db2 servers, running on NT. We have created a script to do
> this, exports from our host via db2 connect, import to our db2 on NT.
> The weird part is that we can run this script fine in control center,
> but we get the login failures when we try to run in script center.
> From script center, we are able to export from the host, but not able
> to import to the db2 for NT (error says Login Failure) Has anyone seen
> anything like this?
>
> We are using db2 for nt.. and we are on version 5.2 FixPak WR09094.
>
> Any help much appreciated,
>
> +Lee Smith << File: Card for Pierre Saint-Jacques >>
