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
begin:vcard n:Saint-Jacques;Pierre tel;cell:514-233-8679 tel;fax:514-737-1268 tel;work:514-737-4515 x-mozilla-html:FALSE org:SES Consultants Inc. adr:;;233 Simcoe Cr.;Mount-Royal;QC;H3P 1X1;Canada version:2.1 email;internet:[EMAIL PROTECTED] title:President fn:Pierre Saint-Jacques end:vcard
