RE: DDM and SQL

Ausverzeichnet! Uh, I mean, Outstanding! Like the farmer in his field.

Did you look at second-level text for the message you received? It has all
the answers you want. Even instructions on what to do if you actually do
want to delete the *LOCAL entry. In short, that entry is where CHGDDMTCPA
info is kept.

F1 is my best friend, next to F4 and F9 (and sometimes F14).   (I actually
do have a little bit of a life!)

Regards

Vern

At 04:51 PM 10/16/02 -0600, you wrote:

Tom/Vern,

        It was the DDM TCP server was not started. Configuration setting was
not set to auto start..  I ran STRTCPSVR SERVER(*DDM) and tried the
connection again.  Tom, are you stating that one can only connect to a
remote system entry that has *LOCAL on the target's RDBE  "..._as well as_
on the target system for *LOCAL."?

Example:
        RDBE Source - WFICYBIL 10.21.10.5             <--will work
        RDBE Target - WFICYBIL *LOCAL

        RDBE Source - PRODSYS 10.21.10.5              <-- will not work
        RDBE Target - PRODSYS 10.21.10.5

My _assumption_ from previous posts on this subject was that since I could
access DDM files from the source I could also connect via SQL.  However, I
did not take into account the fact of that for TCP, separate servers are
required to host TCP functions, even though I have been exposed to this
situation for Netserver and ftp.

Now, I want to change the name on the RDBE to something different (it
actually has been there for several years and refers to a system that we
upgrade from a long time ago).   I get the message stating "Removing the
*LOCAL directory entry may cause loss of configuration data." when I try to
delete that entry in order to add an entry with a more meaningful name
(since I can only have one entry per remote location).  Anyway, what (if
any) other areas are affect besides DDM or RDB?  Will it be as simple as
stop server, delete current *LOCAL entry, add new *LOCAL entry and start
server?

Thank you,
Matt Tyler