|
You do not mention the version of DB2 on the 390, it needs to be at least 5 to be able to do this with TCP, otherwise you must use SNA LU 6.2
-----Original Message-----
From: Tsopelas Anastasios [mailto:ATsopelas@eurobank.gr]
Sent: Friday, June 30, 2000 11:50 AM
To: MIDRANGE-L@midrange.com
Subject: RE: AS/400 DB2/400 & S/390 DB2 CONNECTION
Your User ID must have CREATE IN authority in collection QSQL400 on the
S/390 system.
Be current on PTFs because the project is a nightmare :-( , but we have full
DRDA (APPC) active for more than one year.
HTH
T.T.
-----Original Message-----
From: Gokhan Yildirim (Garanti Teknoloji)
[mailto:GokhanY@garanti.com.tr]
Sent: Friday, June 30, 2000 3:32 PM
To: 'MIDRANGE-L@midrange.com'
Subject: RE: AS/400 DB2/400 & S/390 DB2 CONNECTION
In my opinion i did my best to create connection. I have
created RDB Directory Entry with this command ADDRDBDIRE RDB(HOST)
RMTLOCNAME(xx.xxx.x.xx *IP)
STRSQL >>
CONNECT TO HOST USER AAA USING ' '
I have accessed to the S/390 via my Host user name and
password authorization passed. But after that there is a message SQL Package
Creation failed.
Is there a checklist for doing this? Manuals, Redbooks etc.
Thanks in advance,
-----Original Message-----
From: Tsopelas Anastasios [mailto:ATsopelas@eurobank.gr]
Sent: Thursday, June 29, 2000 7:23 PM
To: MIDRANGE-L@midrange.com
Subject: RE: AS/400 DB2/400 & S/390 DB2 CONNECTION
Yes but DRDA over SNA ??
-----Original Message-----
From: Gokhan Yildirim (Garanti Teknoloji)
[mailto:GokhanY@garanti.com.tr]
Sent: Thursday, June 29, 2000 6:34 PM
To: 'MIDRANGE-L@midrange.com'
Subject: AS/400 DB2/400 & S/390 DB2 CONNECTION
Is there anyone working with S/390 and AS/400, to help me???
AS/400 DB2/400 & S/390 DB2 CONNECTION OVER IP via DRDA.
İyi Çalışmalar Dilerim,
Gökhan YILDIRIM
GARANTİ BİLİŞİM TEKNOLOJİSİ ve TİCARET T.A.Ş.
Evren Mah. Kocman Cad. No:22
34550 - Güneşli / Bağcilar
İSTANBUL / TÜRKİYE
*Tel : 90 + (212) 657 04 04 / 1336 Dahili
*Faks: 90 + (212) 657 04 73
* mailto:GokhanY@Garanti.Com.TR
<mailto:GokhanY@Garanti.Com.TR>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to
MIDRANGE-L@midrange.com.
| To subscribe to this list send email to
MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to
MIDRANGE-L@midrange.com.
| To subscribe to this list send email to
MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to
MIDRANGE-L@midrange.com.
| To subscribe to this list send email to
MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@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.
midrange.com
