|
Eric DeLong
Sally Beauty Company
MIS-Sr. Programmer/Analyst
940-898-7863 or ext.
1863
-----Original Message-----
From: Weatherly, Howard [mailto:hweatherly@dlis.dla.mil]
Sent: Tuesday, August 14, 2001 7:13 AM
To: 'midrange-l@midrange.com'
Subject: RE: DRDA programsDRDA is sensitive about user id and password combinations, on your CONNECT you are most likely using exec SQL CONNECT user "USERID" password "PASSOWRD" end-exec. This userid and password pair must have access on each machine you are connecting to, so in the case of NT you would (no NT expert here) most likely need to have a userid and password defined in the "manage users" folder. This UID/PW must also have access to the database. I do not know if SQL Server uses NT security or has it's own, but that would b a place to start looking.
FYI check out this pub http://publib.boulder.ibm.com/pubs/html/as400/v4r4/ic2924/info/db2/rbal1mst55.htm
geee, I hope I typed that correctly....-----Original Message-----
From: santoshp@lot.tatasteel.com [mailto:santoshp@lot.tatasteel.com]
Sent: Tuesday, August 14, 2001 00:03
To: midrange-l@midrange.com
Subject: DRDA programs
We have recently upgraded to v4r5 e -servers but our applications are old
mostly in cobol and C. We need to send data from one machine to the other.
We have been doing it thru socket programs written in C. But now i have
embedded CONNECT command in cobol source codes so that a remote data base
can be handled. It has worked very successfully between our as400s.
I want to use the same connect command and update tables in the SQLserver
of another windows NT machine and i want it thru cobol only. I have made
entries for remote DB by using ADDRDBDIRE.But the thing doesnt work. It says " connection refused by remote host" .
Plz suggest what can be done at the windows NT end coz i have no clue
regarding its OS operations.Santosh.
Signature......................
e- mail at : santoshp@lot.tatasteel.com
ITS, Tata Steel.
Jamshedpur, India.
Tel : 842134 (O) , 200279 (R)._______________________________________________
This is Midrange Systems Technical Discussion (MIDRANGE-L)
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.