Re: DDM file between v7r3 and v5r4

Your thinking is that SQL somehow avoids using the DDM file that is actually created when doing a CREATE ALIAS statement?  SQL creates it then ignores it?  Seems unlikely - how else would it know where to get the data that it successfully returned with the SELECT statement?  The data does not otherwise exist on the v7r3 machine.

It seems like SQL and RPG are using different methods to open the DDM file.  And note that the DDM file created by SQL's CREATE ALIAS statement is somehow different than the DDM file created with the CRTDDMF command.  I know this because SQL will not use a DDM file created with the CRTDDMF command.  It's looking like the converse is true -- RPG cannot use a DDM flie created by SQL.


On 12/23/2019 2:48 PM, Patrik Schindler wrote:

Hello Peter,

Am 23.12.2019 um 23:09 schrieb Peter Dow <petercdow@xxxxxxxxx>:

On v7r3, a "SELECT * FROM mylib/myFile" returns the records from myMbr on the remote v5r4 machine.

You're talking about strsql? I'm not sure if this one is utilizing DDM in the background, so your verification might mislead.

[CPF9162] Cannot establish DDM connection with remote system.
Cause . . . . . : An error occurred during distributed data management (DDM)
initialization while attempting to establish a connection at the remote
location OCAL 0000.

That's really strange. I'm not sure if this helps in any way but I failed to provide proper authentication for DDM sessions over TCP/IP. It worked perfectly well with APPC. That was with V4R5, though. I never managed to get that resolved.

I'd recommend to build a test case to try the other way around, if that's a possible culprit. I'm successfully connecting with V4R5 to V7R2 to copy over some records via a trivial read-write loop.

:wq! PoC

PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc