Dan,
I'm not sure I agree with all you said... Specifically, "When you
create a DDM file, you specify a relational database directory entry"..
This is not correct... When you create a DDM connection, you reference
the host. In SNA, this was the APPN system name, or Control Point name.
In TCP/IP, this is either a DNS host name, System host table entry, or
IP address.
Back in the early days, we did DDM extensively, without ever even
knowing about the ADDRDBDIRE. We did not have the SQL development
tools, so DRDA RDB Directory was never defined.
I think Vern got it with his DRDA documentation reference, stating that
DDM is a prerequisite of DRDA...
Just picking nits...
Eric
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan Kimmel
Sent: Wednesday, December 10, 2008 4:31 PM
To: Midrange Systems Technical Discussion
Subject: RE: YAIQ - Yet another ignorant question: multiple LPARs.
Okay. I was trying to make a generic comment.
DRDA is an architecture. All DB2 instances support DRDA.
The Relaional Database Directory is the i object that is used to
describe the connection to other database machines and instances that
support DRDA. You can put other databases in there too, but you have to
install a driver. The driver for DRDA databases is supplied with the
system.
When you create a DDM file, you specify a relational database directory
entry.
When you CONNECT with SQL you specify a relational database directory
entry.
A relational database directory is often referenced as a remote
relational database directory.
Not the same thing. I should have said DDM *usually* *uses* DRDA. When
you use DDM to connect to a remote database, you *usually* use the i
DRDA driver. When you use SQL to connect to a remote database, you
*usually* use the i DRDA driver.
Dan Kimmel
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, December 10, 2008 2:06 PM
To: Midrange Systems Technical Discussion
Subject: RE: YAIQ - Yet another ignorant question: multiple LPARs.
I am not so sure they are the same. DDM can't be used by SQL. DRDA had
better be.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From:
"Dan Kimmel" <dkimmel@xxxxxxxxxxxxxxx>
To:
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date:
12/10/2008 01:35 PM
Subject:
RE: YAIQ - Yet another ignorant question: multiple LPARs.
Sent by:
midrange-l-bounces@xxxxxxxxxxxx
I'm sorry I led you astray on that. No, you cannot access program
objects using DRDA.
By the way, others called it DDM. Same thing as DRDA.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of McKown, John
Sent: Wednesday, December 10, 2008 11:05 AM
To: Midrange Systems Technical Discussion
Subject: RE: YAIQ - Yet another ignorant question: multiple LPARs.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan Kimmel
Sent: Wednesday, December 10, 2008 10:47 AM
To: Midrange Systems Technical Discussion
Subject: RE: YAIQ - Yet another ignorant question: multiple LPARs.
Use remote database directory to use the database on another LPAR.
This is DRDA under the covers. You can also connect to DB2 on your
mainframe from your i. When using LPARs, the "ethernet" (or SDLC if
you
prefer) is
through the system backplane, so it is very fast.
Ah. Thanks. I think that I have a "conceptual problem". So, everything
on the i is contained in a DB2 database, correct? Therefore it can be
shared via "remote database directory" aka DRDA. I'm not used to
thinking of programs as being stored in a database. Another conceptual
hurdle to get over.
The "backplane ethernet" sounds very similar to the z series
"hipersocket".
--
John McKown
Systems Engineer IV
IT
Administrative Services Group
HealthMarkets(r)
Administrative Services Group
9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * (817)-961-6183 cell john.mckown@xxxxxxxxxxxxxxxxx
* www.HealthMarkets.com
Confidentiality Notice: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential or proprietary information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
