|
Matt, You need to create a Relational Database Directory Entry for each system you want to use DRDA to connect to (IBM menu CMDRDB contains the RDB commands). In SQL you then use the CONNECT keyword to access the remote database. Everything else is straight SQL. Of course you want to remember to disconnect when you finish. If you are having difficulties connection to the remote system look at how your communications is set up. -----Original Message----- From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com]On Behalf Of Tyler, Matt Sent: Thursday, October 10, 2002 7:37 AM To: 'midrange-l@midrange.com' Subject: RE: DDM and SQL Vernon, There has to be more to than that. I have added entries as you have indicated and I can ping all our 400's. I get refused connections because of authorizations and other messages. Thank you, Matt Tyler Mattt@wincofoods.com -----Original Message----- From: Vernon Hamberg [mailto:vhamberg@attbi.com] Sent: Thursday, October 10, 2002 00:19 To: midrange-l@midrange.com Subject: RE: DDM and SQL An *IP type RDB entry needs to have an IP address that is pingable from the 400. Try pinging whatever you've specified for the IP address. You might need to use a numeric address, not a name, unless the 400 is set up to check a DNS or has the name in its hosts table. To add the entry ADDRDBDIRE RDB(ASDF) RMTLOCNAME('192.168.1.52' *IP) should work. Then use CONNECT TO ASDF in iSQL. You might also need SET CONNECTION ASDF. Then you just need to be sure the library and file exist on the other system. All depends on whether your 400 can resolve the IP address. Luck Vern At 05:06 PM 10/9/02 -0600, you wrote: >Mark, > I do have RDBE's but I am not able to get connected to another >system. Can you post the specifics of a RDBE using IP? And is there >anything else that might need to be set up (beside TCPIP)? > > >Thank you, >Matt Tyler >Mattt@wincofoods.com _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 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 Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 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 Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.