Re: DDM file between v7r3 and v5r4

[Peter Dow <petercdow@xxxxxxxxx>]

Hi Tom,

Yes, you are correct. We have the remote DB entry, along with ADDSVRAUTE 
(Add Server Authentication Entry). For RPG programs, the CRTDDMF works 
great; we have a small application in production that is using that, 
along with remote data areas.

However, SQL does not like files created with CRTDDMF.  SQL *does* like 
files created with CREATE ALIAS which point to a remote table, which are 
actually DDM files; but RPG doesn't like those.

Kind of like the IBM development teams (SQL and RPG) didn't agree on 
something.

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /

On 12/24/2019 9:46 AM, Tom Daly via MIDRANGE-L wrote:
>   I seem to recall there was change in how DDM authenticates, now you must add a remote DB entry
> On source system add an RDB entry to point to the target systemADDRDBDIRE RDB(rdb_name) RMTLOCNAME('x.x.x.x' *IP)
> CRTDDMF FILE(LOCLIB/LOCNAME) RMTFILE(RMTLIB/RMTNAME) RMTLOCNAME(rdb_name)
> Then run your SQL on LOCLIB/LOCNAME